Start a Conversation



1 Message


February 10th, 2024 01:05

Adding a new vxrail with VSAN, Then migrating old vxrail and vsan to new cluster - both embedded vcenter

Hi everyone,

I am looking for some info on migrating an existing vxrail (4.5.210-8392086) and vsan cluster (or it's vms and storage) to a new vxrail and vsan - both using their own embedded vcenter.  The information I have found doesn't document this but documents to an external vcenter.

The source vcenter is and target is 7.0.3

I am unsure if I can do the following or if it would cause an issue with VXRAIL.

  1. Copy all VDS settings to new cluster
  2. Enable vSAN on new cluster (follow Step 2 below)
  3. Disable stretched cluster
  4. Move each host
  5. Move witness
  6. Re-enable stretched cluster (follow Step 4 below)

Any comments or updates would be appreciated.

4 Operator


1.7K Posts

February 10th, 2024 02:22

I'm not completely sure what you are planning to do.

If you want to merge VxRail host into non-VxRail cluster, it's not supported from VxRail perspective.

But if you do not need a technical support for the VxRail any more, it's possible technically.

However, VxRail ESXi has some custome vib that personalize VxRail itself so it could make some trouble.

4 Posts

February 13th, 2024 18:29

Good morning,

Have you looked into vSphere Replication?
I would make sure that the version of vSphere Replication is compatible with both versions of your vCenters. You can look at the VMware matrix for this.

We had success with the following:
Old VxRail was on 6.5 (source) our other location was 7.0.x. (destination)

We made sure the version of vSphere Replication was compatible.

We made sure we had enough storage space on the destination.

The network that the servers will use are on the destination. This is important.

Setup the replication process for all the virtual machines that needed to be moved.

You can set the settings as RPO as little as 5 minutes or up to 24 hours. You can then allow replication to complete.

Then, once the virtual machine has been replicated, you can recover to the destination.

The process is straight forward, just make sure the virtual machine (source0 is powered off and still in inventory. It will offer to do a final sync and then you need to make sure the network adapter is connected, and the correct port is used. Then power on the virtual machine and trouble any issues.

I moved over about 163 virtual machines like this. It had little downtime.

You may need to update the VMware tools and hardware compatibility (do the VMware tools first, if it is a guest-controlled tools, you may need to contact support before upgrading the hardware compatibility).

This information is offered as a use at own risk, please do your due diligence and research.

Thank you.

No Events found!