How to rename Vmware Backup Proxy

[rimvydukas]

Hi,

When I create new backup proxy it is created with a name "Vmware Backup Proxy" which is too general. So my question would be - is it possible to change this name to more descriptive one? Thanks.

[veremin]

"Vmware Backup Proxy"

This is the name of default VB&R proxy; other proxy servers are named in accordance with their DNS names or IP addresses, depending on the way they have been added to backup console.

For now the only possible way to provide more detailed information about proxy server is to fill the corresponding “description” field.

Thanks.

[rimvydukas]

Then there goes another feature request - ability to change backup proxy name

[doomi]

it still seems not possible to rename the first proxy server

it's disturbing to have multiple proxies, each with it's real server name, but the first one is just called "VMware Backup Proxy".

[veremin]

In this case, you might want ask support team whether they are aware of ways to change the said name inside the product database. Thanks.

[plochner]

What is the status on this 2.5 year old feature request? I have 5 proxies in my organization, all of them named properly, except for my very first created proxy, which is stupidly named "VMWare Backup Proxy" and I can't change it. When I'm creating backup jobs in other sites I can easily determine what belongs where, since my proxy name is texas-proxy.mysite.net, I need to match that with texas-repo.mysite.net.

However "VMware Backup Proxy" doesn't provide me with this. I can't even add "california-proxy.mysite.net" because it knows that it's already been assigned to "VMWare Backup Proxy".

[Gostev]

What is the status on this 2.5 year old feature request?

Not enough demand in the past 2.5 years to justify implementation.

[thomas.biesmans]

Not enough demand in the past 2.5 years to justify implementation.

TL;DR: possible pre-v9 and in v9.

Anton... Shouldn't be a feature request, this is just an oversight. Not being able to rename a Backup Proxy, in such a dynamic product, is just foolish.
How can you look at the following list and not be irked by it? When selecting proxies in a backup job the description is not even shown...
- VMware Backup Proxy
- BE_VSRV_WIN_VEEAM02
- BE_VSRV_WIN_VEEAM03
- NL_VSRV_WIN_VEEAM01
- NL_VSRV_WIN_VEEAM02

I wouldn't open a feature request for something like this, I just get frustrated and upset and in the end give up... It's one of those little gripe things.

At least v8 allowed you to work around this using standard operations:
- add the first backup server as a new managed Windows server, using FQDN,
- delete the default 'VMware Backup Proxy' (I'm thinking after changing the config backup to a new repository with a non-default name ),
- re-create a Proxy using the new managed server and name.

In v9 the first server is already listed using its FQDN, yet when deleting and re-creating the default Proxy Veeam still uses 'VMware Backup Proxy' for the name... -.- Unlike every other Proxy where the FQDN is used. Luckily you can still do it using SQL:
- Stop Veeam services, except for SQL.
- Use SQL Management Studio, edit table 'dbo.BackupProxies' and change the name to an FQDN.
- Start Veeam services.

Encountered it in a new installation, running backups off this newly named Proxy works, still need to test further.

[Matthieu]

In v9 the first server is already listed using its FQDN, yet when deleting and re-creating the default Proxy Veeam still uses 'VMware Backup Proxy' for the name... -.- Unlike every other Proxy where the FQDN is used. Luckily you can still do it using SQL:
- Stop Veeam services, except for SQL.
- Use SQL Management Studio, edit table 'dbo.BackupProxies' and change the name to an FQDN.
- Start Veeam services.

Encountered it in a new installation, running backups off this newly named Proxy works, still need to test further.

Could you tell us if your solution worked like a charm.. or not?

thx by advance

[sanktis]

Hi i have the same issue. I like to rename the Default VMWare Backup Proxy to the FQDN of the Server.
Does the SQL Manipulation works?

[veremin]

The said approach has not been tested by us. So, it seems you're on your own here.

I'd recommend backing up server configuration prior to editing product database in order to be the safe side.

Thanks.

[dropped91]

Hi,

I have a feature request:
I want to rename my existing proxies.
This is actually impossible.

[Shestakov]

Hi,
Could you specify your request?
Do you want to rename to default proxy or all of them?
Thanks!

[dropped91]

If it possible I want to rename all my backup proxies.
For the first time it would be enough to rename the default backup proxy.

[Shestakov]

There is no way to rename the default proxy via UI, however you may contact the support team and check whether they can change the said name inside the product database.
For other proxies you can re-add them with new names and edit the jobs if needed.
Thanks!

[matsholm]

Hi all
I have a customer that wil lchange their domain name, not a new domain but they'll change the name.
They have Veeam 9.5 installed with one Veeam server, two proxies, two reps (StoreOnce) and one Veeam O365 server with local rep all is shown in Veeam with FQDN
What is the best way to handle this from a Veeam perspective?
I was thinking about setting up a new Veeam server and restore configuration but what about the other reources?

[DGrinev]

Hi Mats,

There is no way to rename Veeam infrastructure components via UI.
Please review this topic for more information.

Thanks!

[matsholm]

Thanks for fast answer and if I uderstand you I need to setup a new server with the new name of the domain and then do a restore? And for the proxies (physical servers) I'm not able to handle this at all?
The server will have a new name after two restarts it's veeam-2.domain.local today and will be renamed to veea-2.newds.local but it's still the same doamin.
How am I suppose to handel the Veeam proxies if I can't rename a server?

[DGrinev]

I need to setup a new server with the new name of the domain and then do a restore?

That's correct.

You can re-add proxies that's the only way to rename them.
Please, look at the first page of this thread as it's already been discussed. Thanks!

[foggy]

Hi Mats, you can try this approach, might help.

[l.vinokur]

The powershell approach did not help unfortunately. the "Get-VBRViProxy" command returns a Veeam.Backup.Core.CViProxy object, which does not have a SetName method.
In any case, quick search in the DB shows that the BackupProxies table has a "name" field. I changed it using the SQL mgmt. studio and after console restart it shows the new proxy name.
The same line has an "id" and a "host_id" fields with GUIDs, so I believe it should be safe from breaking anything. From my experience with Veeam support editing the DB, there is always some kind of GUID linked, so the name is probably harmless.

And yet, keep a good DB backup

[foggy]

The same line has an "id" and a "host_id" fields with GUIDs, so I believe it should be safe from breaking anything. From my experience with Veeam support editing the DB, there is always some kind of GUID linked, so the name is probably harmless.

That said, we do not encourage interfering with the database directly.

[l.vinokur]

Agree 100%, foggy. It should be done with the support.
As a followup, I have no issues since that change (about a month).

[l.vinokur]

Still works, Veeam9.5u4a.
No issues.

[Shestakov]

Good to know, but it's still not recommended to change database values manually

[spfs62]

Hello all!
I am running V10 and my Proxies are the same server as my Repositories. I am in the process of renaming our Proxie/Repository Windows 2016 servers.

Do I have to remove them from Veeam first, or can I rename them and add them in as new.

I know I will need to go into Backups\Disk and remove the configuration of the backup jobs associated then point to the new servers, but is there anything else I need to do.
I don't think I can remove them while there are jobs attached, Correct?

any help is appreciated
thanks

[veremin]

Just to be sure - by renaming you mean setting new DNS name to the server that runs both Proxy and Repository roles, correct? Thanks!

[spfs62]

yes, that is correct

[veremin]

Got it, in this case you seem to have grasped the concepts correctly: you will need to re-add proxy and repository servers under new names and make jobs use them (change proxy and repository settings in the job configuration).

Also, you can try the referenced PowerShell workaround, but I'm not sure whether it still works on v10 or v11 installation.

Thanks!

[spfs62]

thanks Vladimir. I appreciate your reply and quick response