How to rename veeam backup server host?

[Vitaliy S.]

After joining to another domain, you will need to verify/change all the credentials used in the Veeam backup server (assuming that there are no trusts between new and old domains).

[hyvokar]

Thanks! I'll double check that.

[rogerdu]

I have a Repository server that (in the GUI) is referenced by the IP address... I was in a hurry to get/test the backups... now the name is stuck there. Is there a way to change the name in the GUI to reflect the DNS name instead of the IP address?

Thanks in advance.

Roger

[veremin]

You're talking about underlying server that hosts repository role, right? If so, you can try this workaround. Thanks.

[rogerdu]

Correct... VeeamBKP is the management host, VeeamREPis the repository which has 3 iSCSI LUNS for repositories setup as one regular and one SOBR. In the GUI, they show up as VeeamBKP and 192.168.1.8. I would like them to show up as VeeamBKP and VeeamREP.

I've downloaded the latest .iso, and in the Backups folder there is only Shell.x64.msi and Server.x64.msi. Are either of these the Powershell extensions? or do I have to go to the v8 .iso?

[foggy]

It's now embedded into the Veeam B&R Console installation package, so you need the first one.

[rogerdu]

so in my case, I should be able to issue 4 commands to rename the Repository server...

Code: Select all

Add-PSSnaping VeeamPSSnapin
Connect-VBRServer -Server <server-name> -Port 9392 -User <MyUserID> -Password <MyPassword>
$Server = Get-VBRServer | ?{$_.name -eq "192.168.1.8"}
$Server.SetName("VeeamREP")

All I want to do is aesthetics... its the value that shows up in the GUI that I want to change... the server IS represented as the IP address not the Hostname

[foggy]

You have an unnecessary "g" in the first cmdlet.

[rogerdu]

what... no snapping!!!

[veremin]

VeeamREP is not a DNS name, is it? I'm wondering because the managed server should be reachable via this name/IP. I want to clarify that you're not confusing Repository name and DNS name/IP address of managed server that hosts repository role/

Thanks.

[rogerdu]

The actual server name is veeamrep-<site1> and veeamrep-<site2> (for the two sites). Our highly imaginative naming convention went out the window for these... veeamwan-<site1>... you get the picture. In the GUI, instead of having the FQDN or the nodename, one of the repository servers was noted as its IP address... its all aesthetics...

Thanks for the help!

[veremin]

Ok, I was trying to say that if you go to backup infrastructure node and select a backup repository, you will see two "names": name of repository itself (Name), name of a host it's created on (Host).

The provided script changes the latter, and the later should be valid IP address or DNS name.

Thanks.

[pkelly_sts]

Should this script also work if wanting to strip *just* the DNS name from the B&R server itself? (i.e. "rename" from FQDN to short-name).

We're nearing the end of a domain migration & I've found that removing & re-adding proxies as short-names gets over the current naming issue, plus protects against the same issue in future (this company has changed domain 3 times in 3 years - drives me mad!)

I ran the commands no problem (against B&R) but it hasn't changed within the "Managed Servers" section of the gui so I'm not sure if it'll actually help me...

[foggy]

Have you tried to rescan/restart everything?

[pkelly_sts]

Re-scanned a couple of times with no change, just rebooted it & still showing FQDN?

[foggy]

Support could look into the database to see if it has really changed.

[pkelly_sts]

Okedoke, I'll give 'em a shout tomorrow... Thanks for the help anyway.

[veremin]

Just checked it, the suggested script works for every managed server, except backup server itself. Thanks.

[pkelly_sts]

Argh! Just my luck!

Is there a safe way to "just" remove the domain portion of the backup server name?

[veremin]

The information must be stored somewhere in product database. So, you can try this approach.

However, I'd suggest you to open a ticket prior to doing that and correct db under engineer supervision.

Thanks.

[david.matthewson]

And yes, I know this is an old issue but I've just had it on 9.5 B&R and the regedit fix works fine. [A few of the keys have changed names slightly but are obvious]

The symptoms are that several of the Veeam services fail to start and can not be manually started. Make the reg changes - no need to reboot - manually start the services and everything works as expected.

[guitarfish]

Just wanted to chime in and say this still works in VB&R 11. There were a few more keys which I found which contained the host name, below. I did not change these initially and all my jobs still worked.

HKLM\SOFTWARE
\Veeam\Veeam Backup and Replication\SqlLockInfo
WOW6432Node\Veeam\Veeam NFS\ItemsCache\265779749415739\itemName
WOW6432Node\Veeam\Veeam NFS\Shared Folders\{a07ea884-461a-495f-8b40-e81da0a28dc0}\nfsFolderName

[guitarfish]

I'm using Veeam 12, and most of the keys mentioned in this thread are no longer in the registry. There is a new key which seems to cover most of them:

HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\DatabaseConfigurations\MsSql\SqlServerName