{"id":12625,"date":"2024-11-06T16:28:49","date_gmt":"2024-11-06T15:28:49","guid":{"rendered":"https:\/\/irg-net.com\/?p=12625"},"modified":"2024-11-06T16:35:46","modified_gmt":"2024-11-06T15:35:46","slug":"moving-a-vsan-cluster-from-one-vcenter-server-to-another","status":"publish","type":"post","link":"https:\/\/irg-net.com\/index.php\/moving-a-vsan-cluster-from-one-vcenter-server-to-another\/","title":{"rendered":"Moving a vSAN cluster from one vCenter Server to another"},"content":{"rendered":"
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

vSphere 7 to 8 updates are slowly in full swing, many customers are migrating to October ’25 -> EOL for vSphere 7. Some of my customers want a brand new vCenter right away, because some of theirs are still from version 5, the ex-colleague fiddled in the Postgre database before he quit and so on and so forth – the reasons seem to be endless.<\/p>\n\n\n\n

One of the most important workarounds is the migration of vSAN clusters from one vCenter to another. I would like to describe this process to you today.<\/p>\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

First things first, let’s see how our vSAN cluster is doing. The cluster MUST<\/strong> be in a healthy state, such as here:<\/p>\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

No warnings are allowed to be displayed, not to mention any errors:<\/p>\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

We look at the virtual network infrastructure, i.e. whether there are standard and\/or distributed switches and how they are set up:<\/p>\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n
<\/div>\n\n\n\n

The same applies to the vmk adapters, here it is important to know where the vMotion is running, how the vSAN is configured, etc.:<\/p>\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

And now let’s start with the first step, exporting the distributed switch and its configurations:<\/p>\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

The port groups must also be included for a smooth migration:<\/p>\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

Then import the Distributed Switch on the new vCenter:<\/p>\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

IMPORTANT<\/strong>: do not check the Box with:<\/p>\n\n\n\n

<\/div>\n\n\n\n
Preserve original distributed switch and port group identifiers<\/code><\/pre>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n
And that’s it for the distributed switch:<\/p>\n\n\n\n
<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n
Now build a new cluster on the new vCenter and activate only vSAN, no other service:<\/p>\n\n\n\n
<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n
Additional important details:<\/p>\n\n\n\n