The data located on shared pRDMs will be copied over network to VMDKs located on vSAN storage in the target SDDC as a part of the cold storage vMotion. Any cluster node can be used as the first migrated node. This operation is an offline operation and require the downtime.

NOTE: The VM “SQL-DB1Node01” is used to illustrate the migration of the first node of the cluster

Step 1. Shutdown the cluster

Step 2. Schutdown VMs

Step 3. Execute vMotion

Step 4. Configure independent-persistent mode.


Step 1. Shutdown the windows cluster using the Failover Cluster Manager mmc. Ensure that all nodes are shown in the Offline state.

Step 2. Shutdown all VMs (within Guest OS) hosting nodes of your cluster.

Step 3. Select the VM “SQL-DB1Node01” in the vSphere Client. Start the vMotion wizard. Check the section Migration of Standalone SQL Server Workload: Step-By-Step Guide early in this document for more details.Follow the additional instructions below:

  1. Assign vSAN policies, use per disk assignment if required.


   2. Use the extended destination port-groups (L2 VPN based), avoid re-IP of nodes/cluster network.

3. Wait for the cold vMotion/Relocation to finish. Depending on the network connectivity, available bandwidth, and pRDMs capacity the process might take a long time.

4. After copletion of the vMotion, check VM virtual disk and SCSI controller configuration sections and ensure that all pRDMs are converted to VMDKs and retained the same configuration as on-premises. Ensure that the SCSI bus sharing for a controller(s) used to connect shared pRDMs is set to physical.

Step 4. Set independent-persistent mode for all converted VMDKs .


check-circle-line exclamation-circle-line close-line
Scroll to top icon