I believe all you should have to do is go to Managed Servers and go into your vCenter properties and go through the wizard changing the name to the new name.
As I share with anyone, I suggest creating a small test environment to test this.
You can change the name in Veeam
Rescan the vCenter in Veeam and you should be fine.
But you have to set the same user/password on the vCenter oder adjust them in Veeam.
Thank you for the quick reply @coolsport00 . However, I can’t find the wizard to change the name. I can change credentials for the existing vCenter but no way to change the hostname.
@JMeixner oh thanks. Yes, we definitely can re-scan and the the same creds are being used. We’ll give that a go, otherwise I guess we can always power down the new vCenter and power the old one back up and it should work? At least that’s the “back-out” plan from the VCSA installer.
Cheers!
Ah ok...so the Properties wizard won't allow the name to be changed. I couldn't verify as I'm away from my laptop atm.
I forgot about this post by Wolff. Good reshare Joe!
Just to add, unless you’re doing a specific custom upgrade path, the default path is to allocate a temporary IP address to the new VCSA to read data from the old one, then it powers down the old VCSA, and the new one restarts with the VCSA FQDN and IP address of the old one, no name changes necessary.
@MicoolPaul really? That’s a bit confusing. The installer screen did mention the temporary IP but it also asked for a new name for the VCSA that’s why I thought it would change the FQDN. I’m guessing that what’s really happening then is that the “label” shown in the VCSA would change to whatever I gave it (a very unimaginative VCSA80 to indicate the version) but ti would still have myVCSA.domain.local as it’s FQDN and therefore would not really affect the backup jobs since they do look for myVCSA.domain.local.
Cool! One learns something new everyday :-)
@MicoolPaulreally? That’s a bit confusing. The installer screen did mention the temporary IP but it also asked for a new name for the VCSA that’s why I thought it would change the FQDN. I’m guessing that what’s really happening then is that the “label” shown in the VCSA would change to whatever I gave it (a very unimaginative VCSA80 to indicate the version) but ti would still have myVCSA.domain.local as it’s FQDN and therefore would not really affect the backup jobs since they do look for myVCSA.domain.local.
Cool! One learns something new everyday :-)
That new name is a temporary name for the upgrade it will change it back to your current VCSA FQDN/IP once completed.
@afn24805 can you share a screenshot please? 
@MicoolPaul screenshot of the window where they ask for the name? I am already in Stage 2 so I don’t think it’ll be possible but I’ll see if I can find one online.
Found some in this article: https://masteringvmware.com/how-to-upgrade-vcenter-server-7-to-vcenter-server-8-step-by-step/
The screenshot under Step 9 of this article is what I was referring to. We use the hostname as the “VM Name” and caused the confusion/concern on my part. That is actually just the label that is shown under the list of VMs in vCenter and NOT the FQDN.
The screenshot under Step 19 once in Stage 2 confirms what @MicoolPaul and @Chris.Childerhose were saying.
Just to add, unless you’re doing a specific custom upgrade path, the default path is to allocate a temporary IP address to the new VCSA to read data from the old one, then it powers down the old VCSA, and the new one restarts with the VCSA FQDN and IP address of the old one, no name changes necessary.
This….I’ve never changed a vCenter name when doing an upgrade. The only time I would consider this is when the vcenter name (FQDN, not the VM container name) is no longer desired, such as if someone decided to call the vcenter “vcenter6” and you’re upgrading to v7 or v8 or whatever. But generally speaking, there’s not need to change the name.
