Comprehensive data protection for all workloads
Post Reply
matteu
Veeam Legend
Posts: 1055
Liked: 172 times
Joined: May 11, 2018 8:42 am
Contact:

Rename VBR server

Post by matteu »

Hello,

After an outage, new VBR server was built and restore configuration applied.
Unfortunately the default name was kept (WIN-XXXXXXX) and I would like to rename it.

What is the correct way to do it ?

Backup configuration -> Rename server -> Restaure configuration ?

Or is it possible only with registry key ?

Or I can just use this : https://www.veeam.com/kb2350

I use Veeam latest version and I have encrypted backup jobs. I use PostgreSQL.

Thanks for your help.
mjr.epicfail
Veeam Legend
Posts: 636
Liked: 182 times
Joined: Apr 22, 2022 12:14 pm
Full Name: Danny de Heer
Contact:

Re: Rename VBR server

Post by mjr.epicfail » 1 person likes this post

just don't. (don't open this can of worms)

Better to create a new server, export import(migrate) config DB.
VMCE / Veeam Legend 2*
matteu
Veeam Legend
Posts: 1055
Liked: 172 times
Joined: May 11, 2018 8:42 am
Contact:

Re: Rename VBR server

Post by matteu »

Thanks for your help but I finally open a veeam case :)

The answer :

Very often, you just have to rename the server name and it should work because Veeam backup service will just use the new name and this new name will be updated on all veeam components (repositories, proxies, ...).
Just need to be sure when local database is used "localhost" is present on sqlhostname on this registry key (if PostGreSQL is used) :
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\DatabaseConfigurations\PostgreSql\SqlHostName

If no localhost is specified here, it's needed to move database to the new hostname after updating it with dbconfig utility.

After the changes, if Veeam backup service start, it should be ok !

Case 07795046
rschols
Influencer
Posts: 10
Liked: 4 times
Joined: Sep 09, 2016 1:12 pm
Contact:

Re: Rename VBR server

Post by rschols »

I tried this on a new server where opening the can or worms wasn't a big deal.
Worked without issues. Existing vmWare and HyperV jobs continued etc.

The change was not picked up in the online admin panel of Veeam Data Cloud Vault (cloud.veeam.com).
So inside VBR, I edited the properties of the Vault repository, clicked "Authorize" and authorized it again.
That made the Vault admin panel pick up the new name. Pre-existing association between the vault and the VBR server remained intact.
Post Reply

Who is online

Users browsing this forum: Amazon [Bot] and 7 guests