VMware VMs

Before configuring DR services, check the virtualization environments of the production end and the DR end, and the storage end environment. If any environment does not meet requirements, modify its configuration.

Common Check Items

Check and configure the following items in the VMware VM environment on the production and DR ends.

Check the version of vCenter Server installed at the production end and the DR end.
For details about the VMware versions supported by eReplication, see the Application Support Matrix sheet in the OceanStor BCManager 8.5.0 eReplication Compatibility List. Check whether the vCenter Server version is applicable before configuring the DR. Install the same version of vCenter Server on both production and DR ends, because different versions of vCenter Server may cause incompatibility with the preinstalled VMware Tools or Open VM Tools, resulting in unexpected failures. The vSphere vCenter version must be the same as the ESX version. Otherwise, unexpected errors may occur.
1. Double-click the vSphere Client icon and enter vCenter Server IP address and its administrator account. Click Login.
  
  You will be prompted by an alarm about installing a certificate upon the login. Install a certificate as instructed or ignore the alarm.
  
  An administrator account of the vSphere vCenter Server is required for logging in to and later locating the vSphere vCenter Server. Obtain it in advance.
2. On the menu bar, choose Help > About VMware vSphere and view the vCenter Server version.
When an ESXi cluster is used, ensure that Distributed Resource Scheduler (DRS) is enabled and the automation level of Distributed Resource SchedulerDRS is not Manual.
1. Choose Inventory > Hosts and Clusters. In the navigation tree on the left, right-click the ESXi cluster and choose Edit and Configure from the shortcut menu.
2. Click Cluster function and select Open VMware DRS.
3. Click VMware DRS and do not select Manual in Automation level.
Confirm that virtual disks used by the protected VM are not in the independent mode (persistent or non-persistent).

Production End

Before performing DR protection for or recovering VMs, ensure that VMware Tools or Open VM Tools has been installed on the VMware VMs. The VMware Tools version or Open VM Tools needs to match the vSphere vCenter version. Unexpected failures may occur if an incompatible version is used. For details about how to obtain and install VMware Tools or Open VM Tools, see the related VMware documentation.

Check whether VMware Tools or Open VM Tools has been installed on the VMs that require DR protection at the production end and whether the VMware Tools or Open VM Tools version is correct.
Choose Inventory > Hosts and Clusters. In the navigation tree, click a VM that requires DR protection. In the function pane, click the Summary tab and view information about VMware Tools in the General area. If VMware Tools or Open VM Tools is not installed on the VM, install it. If the VMware Tools or Open VM Tools version is not correct, install a correct version.
- If VMware Tools or Open VM Tools is not installed, information shown in Figure 1 or Figure 2 is displayed.
Figure 1 VMware Tools not installed

Figure 2 Open VM Tools not installed
- If VMware Tools or Open VM Tools has been installed but its version is incorrect, information shown in Figure 3 is displayed.
Figure 3 Incorrect version of VMware Tools or Open VM Tools installed
- If VMware Tools has been installed and its version is correct, information shown in Figure 4 or Figure 5 is displayed.
Figure 4 Correct version of VMware Tools installed

Figure 5 Correct version of Open VM Tools installed

Storage End

Table 1 describes the storage requirements of DR solutions.

**Table 1** Requirements of DR solutions on storage
Technology	Restriction and Requirement
Synchronous or asynchronous replication (SAN)	Operating systems of VMs can only be installed on virtual disks. Disks, except those where operating systems of VMs reside, can be RDM disks. If VMs use disks of the virtual RDM type, you can create quiesced snapshots for VMs to ensure VM consistency and recover VMs using the snapshots. If VMs use disks of the physical RDM type, quiesced snapshots cannot be created for these disks. Check whether remote replication pairs or consistency groups of the arrays are correctly set up. If datastores used by a VM occupy multiple LUNs, ensure that the remote replication pairs of all LUNs reside in the same consistency group. Check whether information about initiators of production/DR ESXi hosts and test hosts is displayed on the array. Check whether multiple primary LUNs on the storage array reside in the same consistency group. If a VM uses a datastore consisting of multiple LUNs, the LUNs must reside in the same consistency group. If a VM uses multiple datastores, the LUNs used by the datastores must reside in the same consistency group. If a datastore used by multiple VMs is created using multiple LUNs, the LUNs must reside in the same consistency group. If one or more VMs use the same RDM disk, the LUNs used by the RDM disk, the datastores where the disks files reside, and VMs must be in the same consistency group. Check that the primary and secondary LUNs on the storage array are correctly mapped to the production/DR host (group). For a cluster consisting of ESXi hosts, ensure that the hosts included in the host group to which the primary and secondary LUNs are mapped are all the ESXi hosts only in the cluster. If the production/DR environment is a cluster consisting of multiple ESXi hosts, ensure that the host group to which LUNs on the production/DR storage array are mapped only includes all ESXi hosts in the cluster.
Asynchronous replication (NAS)	VMs cannot use RDM virtual disks. VMs' virtual disks cannot reside in different storage devices and datastores used by VMs must be created by Huawei NFS file systems. File systems can be shared by NFSv3 only. Check whether remote replication pairs or consistency groups of the arrays are correctly set up. Check whether the shared file systems on the arrays have the following permissions: Read and write no_all_squash root_squash
HyperVault	VMs cannot use RDM virtual disks. One VM's virtual disks cannot reside in different datastores used by VMs must be created by Huawei NFS file systems. File systems can be shared by NFSv3 only. Check whether the shared file systems on the arrays have the following permissions: Read and write no_all_squash root_squash Check whether Huawei storage devices meet the networking requirements for all-in-one backup. Check whether remote replication pairs or consistency groups of the arrays are correctly set up. If datastores used by a VM occupy multiple LUNs, ensure that the remote replication pairs of all LUNs reside in the same consistency group.