I'm going off a whim here based from experience.
I'm going to have to do the basic steps:
1) Follow this KBhttps://docs.vmware.com/en/VMware-vSphe ... 2A854.html to change the vCenter Address.
2) Ensure my DNS records show to be updated on Veeam via a ping test and DNS cache flushing.
3) Rescan the object in Veeam.
That should be it, yes?
And if I were to change the hostname of the vCenter server https://blogs.vmware.com/vsphere/2019/0 ... -fqdn.html
After doing so, in this case I'd also change the account used to connect to the vCenter in Veeam as well. All I'd have to do is:
1) Change the hostname of the vCenter.
2) Update Object in Veeam https://www.veeam.com/kb1905
3) Run object edit wizard to pick updated credentials (which would be added to Veeam managed crednetials)
4) Rescan the object in Veeam.
That would be it yes? AFAIK no issues would occur to VM-IDs and all CBT data would also fully remain in-tact, correct?
-
- Veteran
- Posts: 382
- Liked: 86 times
- Joined: Mar 17, 2015 9:50 pm
- Full Name: Aemilianus Kehler
- Contact:
-
- Product Manager
- Posts: 15166
- Liked: 3248 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Change vCenter name and IP
Hello,
I never did the VMware part, but from a Veeam side that looks good.
KB1905 came up a few days ago and we update it a little bit to reflect that it works for all Veeam components.
Best regards,
Hannes
I never did the VMware part, but from a Veeam side that looks good.
KB1905 came up a few days ago and we update it a little bit to reflect that it works for all Veeam components.
Best regards,
Hannes
-
- Veeam Software
- Posts: 727
- Liked: 161 times
- Joined: Jan 22, 2015 2:39 pm
- Full Name: Stefan Renner
- Location: Germany
- Contact:
Re: Change vCenter name and IP
Hi,
as for the VMware part there were usually the following things that kicked in at such a change when I did it in the past:
1. DNS issues as you may have name resolutions you forgot to change (esp. host files etc. if used).
2. External tools that are connected via IP instead of DNS (monitoring tools, remote access...etc) and all of a sudden stopped working
So make sure to check everything upfront
Outside of that the change should be fine and of course what I write here is not Veeam related but more infrastructure overall.
For Veeam @HannesK already answered.
Regards
as for the VMware part there were usually the following things that kicked in at such a change when I did it in the past:
1. DNS issues as you may have name resolutions you forgot to change (esp. host files etc. if used).
2. External tools that are connected via IP instead of DNS (monitoring tools, remote access...etc) and all of a sudden stopped working
So make sure to check everything upfront
Outside of that the change should be fine and of course what I write here is not Veeam related but more infrastructure overall.
For Veeam @HannesK already answered.
Regards
Stefan Renner
Veeam PMA
Veeam PMA
-
- Veteran
- Posts: 382
- Liked: 86 times
- Joined: Mar 17, 2015 9:50 pm
- Full Name: Aemilianus Kehler
- Contact:
Re: Change vCenter name and IP
Yup Thanks Stefan, I have dealt with both those things in the past as well haha.
-
- Veteran
- Posts: 382
- Liked: 86 times
- Joined: Mar 17, 2015 9:50 pm
- Full Name: Aemilianus Kehler
- Contact:
Re: Change vCenter name and IP
If anyone interested. I did the needful, went through it all and blogged about my experience.
https://zewwy.ca/index.php/2021/10/23/c ... -hostname/
Was pretty much like the steps I stated, but with a lot more fun.
https://zewwy.ca/index.php/2021/10/23/c ... -hostname/
Was pretty much like the steps I stated, but with a lot more fun.
Who is online
Users browsing this forum: No registered users and 57 guests