vSAN cluster migration

In my experience, some vCenter’s faults can’t be remediated how hard you try, and if it's possible you would probably have to start an upgrade scenario like what happened to me about two years ago.

For a couple of months, I was struggling with the vCenter database issues and with the “vPostgres archiver service”

 Finally, I had to upgrade the vCenter version from 6.7U3 to 7U3 and it worked.

Recently, as I was reviewing the vSAN fault scenarios, I found another similar issue where you need to migrate your workload to a brand new vCenter. As you certainly know it would be a breathtaking process.

But what if you have enabled vSAN Cluster?

As a result there are not just some ordinary VMs in a simple scenario, it is a vSAN-enabled cluster!

So as I was reading more about the matter to find a proper solution, I faced a unique yet new feature available from vSAN 7.0.1c where you can completely migrate your "CLUSTER" to a new vCenter server without any downtime!

Just like our Cross-vCenter process think about Clusters instead of VMs! Awesome!

So, I tried to briefly wrap up all the considerations and steps here to have a safe and non-interrupting cluster migration:

• Configure the new vCenter which should have a similar or higher version from the old one.
• Register all the required licenses on the new vCenter.
• Check the management network to ensure the connectivity between your hosts and the new vCenter.
• Check the status of the vSAN health cluster.
• To minimize any impact and maximize workload continuity it would be better to migrate the vSAN kernel adapters traffic from our vDSs to some temporary vSSs.
• Export and then import the vDS settings to the new vCenter.
• Create and enable a new vSAN cluster on the new vCenter.
• Do the same advanced settings on the configuration tab on the new Cluster to have the exact vSAN cluster features there.
• Set the same policies on the new one.
• Respectively disconnect the hosts from the old vCenter and then connect them to the new one.
• Do the vSAN kernel adapter migration from vSS to vDS.
• At last, reapply all policies to the new one.

Please let me know if you have any suggestions to make this migration more smoothly.