#Vcenter 6.5 cluster different update#

This would actually save you an extra step. You could just add the ESXi hosts to the new vCenter Server and once you have confirmed you wish to move the ESXi host, it will automatically be disconnected once added. Note: Technically, you do not even have to disconnect the ESXi hosts from the old vCenter Server. Pre-vSAN 6.6 -В Disconnect one of the ESXi hosts from your existing VSAN ClusterВ and then add that to the VSAN Cluster in your new vCenter Server. Step 1 - Deploy a new vCenter Server and create a vSphere Cluster with VSAN Enabled. Re-enable stretched cluster (follow Step 4 below).Enable vSAN on new cluster (follow Step 2 below).I asked if he could share the modified instructions in case others were interested. I did not see any technical reasons preventing this and one of our GSS Engineers had recently validated this with a customer and successfully moved a vSAN Stretched Cluster. UPDATE2 (11/02/17) - There was a question a couple of weeks back on whether the procedure outlined below could also apply to a vSAN Stretched Cluster.

The Migration Tool does all the heavy lifting. No longer requiring scripts and many long nights of moving hosts one cluster at a time. The new Migration Tool included in the vCenter Server Appliance (VCSA) 6.5 is a game changer. To demonstrate the process, I have a 3 Node VSAN Cluster with a running Virtual Machine on vCenter Server (vcenter55-1) and I have built a new vCenter Server (vcenter55-3) which I would like to move the existing VSAN Cluster over to. vCenter Server migrations have typically taken massive planning, a lot of effort, and time. This means if you need to move your VSAN Cluster from a development vCenter Server to a production vCenter Server or if you accidentally destroyed your original vCenter Server, the VSAN Cluster can easily be re-created on a new vCenter Server. It is true that vCenter Server is required for the configuration and management of the VSAN Cluster and VM Storage Policies, but once those configurations have been applied, then the vCenter Server is no longer in picture from operational point of view. The main reason this is not a challenge is that VSAN has been architected to not have a reliance on vCenter Server for its normal operations. I have personally performed this operation on several occasions without any problems and the process is actually quite straight forward and thought I walk you through it because it is literally a couple of steps. The great news is that this can be done without any impact to your ESXi hosts and more importantly, there is no impact to your workloads. I once moved i updated the vSAN health check DB and donвЂ™t see any new warnings or alerts.I recently caught an interesting VMTN thread where a user wanted to move an exiting VSAN Cluster from one vCenter Server to another vCenter Server with minimal impact to the ESXi hosts and running Virtual Machines. Reconfigure and re enroll any external products you used with the old vCenter.Д¬opy over user permissions you find in the old vCenter. Warning: If you do not use the same cluster name some backup programs wont know where to find the VMвЂ™s so make sure you test backups post migration depending on how it was configured.Д¬opy over you licensing for vCenter and vSAN.Д®nable Dedupe and compression on the cluster if you used it previously.Д®xport then import any template customization you had

Then import the VDS configs to the new vCenterД¬reate a vSAN enabled cluster and move the hosts in. If you use Standard switches they will move over with host so you could skip this step. Next would be to export your Virtual Distributed Switch(s) vDS config and import into the new vCenter. I followed steps from VMware KB 2109891 and .ДЇirst steps is to deploy just the Platform Service Controller and then vCenter with the external PSC option.

#Vcenter 6.5 cluster different update#

After moving vDS and vSAN to new vCenter i will also need to update products that leverage vCenter such as Veeam and Open Manage. I deployed the PSC and vCenter 6.5 as separate VMвЂ™s. This particular vCenter had been upgraded several times and I opted for a fresh start instead of trying to split out the current vCenter. I had a need to split out the PSC from vCenter to use enhanced link mode for a DR site.