Change VC Name/FQDN/IP in Veeam

Veeam Backup & Replication
7.x, 8.x, 9.x
Last Modified:
KB Languages:


The Name/FQDN/IP of the vCenter Server has changed, and needs to be updated within Veeam Backup & Replication.


This solution applies ONLY if the vCenter Server database has not changed.
If the Name/FQDN/IP of the vCenter changed due to a reinstall or upgrade and a new vCenter database was used, the Ref-IDs will have changed. Due to the changed Ref-IDs you will need to follow the documented process in to resolve the "Object "VM_Name" not found" errors if the original jobs are kept.
Before starting you will have to find out the Name\FQDN\IP Veeam is using to communicate with the VC presently. To do this, edit the entry for the VC under Backup Infrastructure and note the “DNS name or IP address”.

User-added image

Next perform the following steps, checking that same location again afterward to confirm the change. 

1.  Launch PowerShell from inside the Veeam Backup & Replication console. You can find the "PowerShell" button under the File-menu's "Console" section.

User-added image

PowerShell will load with the Veeam PowerShell Snapin attached. Run the following command: $Servers = Get-VBRServer -name "Current-VCName/IP"
User-added image

3.  Run the following command next: $Servers.SetName("New-VCName/IP")
User-added image

Close and reopen the Veeam Backup & Replication console to update the entry within the GUI
5.  Restart Veeam Backup Service


More Information

There's no guarantee on whether this method will be public on future releases. 

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
3.9 out of 5 based on 59 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: