vCenter migration to another host

[BenciHu]

Hello All!

1)
I'm planning to patch my ESXi hosts in a vSphere environment. My vCenter Server (6.5 U3) VM runs on one of the 3 hosts on a separate VMFS datastore, while other VMs are on a vSAN datastore
I know that I have 2 options:
- Shut down the vCenter and upgrade the host from CLI
- vMotion vCenter to another host.

Which method is safer or what are the benefits and drawbacks of each method?

2)
Furthermore, I noticed the vCenter disks are thick provisioned (lazy zeroed), and the total amount of provisioned disk space is larger than the VMFS datastore capacity, of course, the used space is much smaller. In this case, If I migrate the vCenter to another host and datastore (vSAN), would it not be a problem if I want to migrate back?

3)
Finally, If I use the CLI method for upgrade and it fails, can I make the vCenter available again on the same host or another host, or I can only restore from backup after the ESXi reinstall? Or what is the best practice in such a case?

Thank you for your answers in advance!

[Milad Mehrabi]

Maybe better to post it in vSAN discussion also

[a_p_]

If vMotion is possible, use it. This will allow you to update/patch all hosts through Update Manager.

>>> I noticed the vCenter disks are thick provisioned (lazy zeroed), and the total amount of provisioned disk space is larger than the VMFS datastore capacity ...
Please clarify. You are saying that vCenter runs on the VMFS datastore, but the provisioned space is higher than the datasatore's capacity!? That's impossible.

André

[BenciHu]

Hello André!

Thank you for your answer.
You were right, I miscounted the disk provisioned size, and it is indeed lower than the VMFS. Thus, it is not an issue anymore.

Regarding the vMotion vs CLI. I assume vMotion advantage would be the vCenter will be safe on another host, but it takes time to get migrated (back and forth). However with CLI method if the upgrade failed the vCenter will be in risk, but I do not have to wait vMotion time.

Am I correct?

Is there any known issue with vMotion that I have to pay attention to? (Network settings are the same, the Storage policy will be changed to vSAN Default Policy)

Thank you in advance!

Thank you in advance!

[Rob Bishop]

I've been vMotioning the vCenter around between hosts every month for years to allow for host patching and have never had an issue. 

[Sachchidanand Upadhyay]

In you first option, it depends the requirement of vCenter duing the downtime. vMtion is always a good option. It's better to take backup of vCente while doing such activities. 

Regarding your third point, It's the last and in the worst case, you deploy the vCente and add the hosts to it or restore from the backup.

Regards,

Sachchidanand