Prepare your migration environment by deploying the essential components identified in Table C-1. Ensure that each component meets the stated requirements.
Table C-1 Components Needed for WSFC Migration to VMware VMs with RDM Disks
|
Required Component |
Description |
|---|---|
|
Windows Server Failover Cluster |
A supported Windows Server Failover Cluster with two nodes (active/passive). Ensure that PlateSpin Migrate supports the source Windows cluster for migration to VMware. See |
|
VMware vCenter Cluster 6.x |
A supported VMware 6.x cluster with at least two member hosts that are running the same software version of VMware ESXi. The VM nodes for the target WSFC will reside on different hosts in the same VMware cluster. Both hosts must be in the same broadcast domain. Each host must have a NIC available to use as the uplink of the host’s virtual switch for the heartbeat network. The uplink abstracts the actual NIC information so that the host NIC used for the heartbeat traffic can be different on each host. Ensure that PlateSpin Migrate supports the VMware version as a target platform. See Table 2-10, Supported Target VMware Platforms for the Migrate Web Interface and Migrate Client. Ensure that the target VMware environment is compatible for the source Windows cluster, and in the cluster-across-boxes configuration. See Microsoft Windows Server Failover Clustering on VMware vSphere 6.x: Guidelines for Supported Configurations (2147661) in the VMware Knowledgebase. |
|
vSphere Web Client |
VMware tool used to prepare your target VMware environment. Ensure that you have administrator-level access to the VMware vCenter Cluster and its member hosts to prepare the VMware environment, heartbeat network, VMs, and RDM disks. NOTE:You can alternatively use the vSphere Client. You must adapt the instructions as needed to perform the tasks and apply the required configuration settings. |
|
SAN storage |
Fibre Channel (FC) SAN storage to use for the RDM disks. The SAN must be accessible to the VMware environment. NOTE:VMware requires that you use the same SAN type for all shared RDM disks that you create for the Windows cluster. We tested this migration scenario using RDM disks created with LUNs on a FC SAN. |
|
PlateSpin Migrate server |
Migrate server deployed in the source network. |
|
PlateSpin Migrate Client |
Migrate Client deployed on the Migrate server, or on a dedicated computer in your source network. |
|
PlateSpin ISO image file |
Download the PlateSpin ISO image from the PlateSpin Migrate software download page. See Section H.1, Downloading the PlateSpin ISO Images. |
|
NTP Server |
An NTP server external to the VM hosts. After the migration, VMware recommends that you synchronize time for the cluster VM nodes with the NTP server used by your domain controller. Disable host-based time synchronization for the two VMs. |
Before you begin the migration, you must prepare and configure the heartbeat network, VMs, and RDM disks in the target VMware environment. Table C-2 identifies the configuration requirements for these target VMware components. For instructions, see Section C.3, Preparing the Target VMware Environment.
Table C-2 Configuration Requirements for Target VMware Components
|
Required VMware Components |
Remarks |
|---|---|
|
LUNs in the FC SAN |
A LUN (logical disk) in your FC SAN to use for each shared RDM disk. Each LUN should be sized to fit the source shared quorum or data disk that you plan to store on the RDM disk. |
|
Virtual heartbeat network |
A dedicated virtual network for the private heartbeat communications between the VM nodes of the Windows cluster across the hosts. Ensure that you create the virtual network before you create the target VMs and RDM disks. |
|
Target VM nodes |
Target VMs to use as members of the WSFC. Each VM must have two NICs: one for the data network and one for the private heartbeat network. |
|
SCSI Controller |
A dedicated SCSI Controller (virtual SCSI adapter) on each cluster VM node for the shared RDM disks. All of the cluster VM nodes must use the same target ID (on the dedicated SCSI Controller) for the same shared disk. For example, if you attach the first shared RDM disk to SCSI1:0 and the second one to SCSI1:1 on VM1, you must attach the same disks to the same IDs on VM2. |
|
RDM disks |
Shared disks for the shared quorum and data disks that are accessible to each cluster VM node. VMware requires a separate RDM disk for each shared quorum disk and shared data disk. Configure RDM disks in Physical Compatibility Mode. Set the SCSI bus sharing mode to physical. |