{"id":1253,"date":"2021-09-26T15:18:02","date_gmt":"2021-09-26T20:18:02","guid":{"rendered":"http:\/\/zewwy.ca\/?p=1253"},"modified":"2022-05-17T14:18:38","modified_gmt":"2022-05-17T19:18:38","slug":"change-vcenter-fqdn-or-ip-on-veeam","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2021\/09\/26\/change-vcenter-fqdn-or-ip-on-veeam\/","title":{"rendered":"Change vCenter FQDN or IP on Veeam"},"content":{"rendered":"

<\/span>Story<\/span><\/h1>\n

I recently did a infrastructure upgrade on my home lab, which included moving all my esxi hosts into a dedicate subnet, and making them all more dependent on DNS. This has it’s pros n cons, after all my ESXi host had their IP addresses changed<\/a>. I also moved my vCenter and changed it IP address<\/a>, which is now supported yay.<\/p>\n

Now I had to move Veeam along with it, originally it was in the same subnet as the esxi hosts, and vCenter which have all moved, instead of trying to manage cross subnet comms, I changed Veaam’s IP address and pointed it’s DNS settings to my AD DNS which has all the ESXi and vCenter host records. Was easy enough just changing the Windows NIC Ip address, and changing the VM’s VMPG.<\/p>\n

<\/span>\u00a0How to<\/span><\/h2>\n

Now when I went to scan the vCenter instance in Veeam, it complained about the certificate, since it was renewed from the vCEnter upgrade. I decided I’d change it to be based on DNS now that everything else is as well. When I went to edit the object in Veeam it was greyed out.\u00a0 Lucky for me Veeam had a KB ready to go<\/a>.<\/p>\n

Challenge<\/p>\n

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

Solution<\/p>\n

Solves Name Change Only
\nThis solution applies ONLY if the vCenter Server database has not changed.
\n(I did an upgrade so yes, which you’d want to preserve VM-IDs, and chains)<\/p>\n

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 www.veeam.com\/KB1299<\/p>\n

<\/span>Step 1<\/span><\/h3>\n

Prior to running the commands below you need to identify the Name\\FQDN\\IP Veeam is using to communicate with the VC currently. To do this, edit the entry for the vCenter under Backup Infrastructure and note the \u201cName:\u201d.<\/p>\n

\"\"<\/a><\/p>\n

Next perform the following steps to change that VMware Server’s name.<\/p>\n

<\/span>Step 2<\/span><\/h3>\n

Launch PowerShell from inside the Veeam Backup & Replication console. You can find the “PowerShell” button under the File-menu’s “Console” section.<\/p>\n

The Veeam Backup & Replication PowerShell Tookit will load.<\/p>\n

<\/span>Step 3<\/span><\/h3>\n

Run the following command:<\/p>\n

$Servers = Get-VBRServer -name \"old-name\"<\/pre>\n
Replace old-name with the “Name” current set for the vCenter in the Veeam Backup and Replication Console<\/p>\n
<\/span>Step 4<\/span><\/h3>\n
Run the following command next to change the name:<\/p>\n
$Servers.SetName(\"new-name\")<\/pre>\n
Replace new-name with the new name for the vCenter, this can be an IP, Hostname, or FQDN.
\nDo not remove the quotes on either side.
\nThis change will go in to effect as soon as the command in Step 4 completes.<\/p>\n
<\/span>How I did it – One Liner<\/span><\/h2>\n
<\/span>Verify:<\/span><\/h3>\n
Get-VBRServer -name \"Name from Step 1\"<\/pre>\n
<\/span>Change:<\/span><\/h3>\n
(Get-VBRServer -name \"Name From Step 1\").SetName(\"new.domain.com\")<\/pre>\n
<\/span>Results:<\/span><\/h3>\n
\"\"<\/a><\/p>\n
\"\"<\/a><\/p>\n
Now you can click next, Apply, should get right past checking certificate if the certificates are all good… and end up with the follow after rescan:<\/p>\n
\"\"<\/a><\/p>\n
That was easy enough, I don’t fully understand why the grey out the UI to make this change, but there you have it. Happy Backups!<\/p>\n","protected":false},"excerpt":{"rendered":"
Story I recently did a infrastructure upgrade on my home lab, which included moving all my esxi hosts into a dedicate subnet, and making them all more dependent on DNS. This has it’s pros n cons, after all my ESXi host had their IP addresses changed. I also moved my vCenter and changed it IP … <\/p>\n
Continue reading “Change vCenter FQDN or IP on Veeam”<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","footnotes":""},"categories":[5,8,236],"tags":[379,16,82],"class_list":["post-1253","post","type-post","status-publish","format-standard","hentry","category-hypervisors","category-server-administration","category-veeam","tag-change-ip","tag-vcenter","tag-veeam"],"_links":{"self":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1253","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/comments?post=1253"}],"version-history":[{"count":3,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1253\/revisions"}],"predecessor-version":[{"id":1371,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1253\/revisions\/1371"}],"wp:attachment":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/media?parent=1253"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/categories?post=1253"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/tags?post=1253"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}