Veritas™ Resiliency Platform 2.2 Solutions for VMware

The vCenter and ESX servers for the virtual machines must be added to Resiliency Platform at the production and recovery data center.

For more information on adding asset infrastructure, refer to the Deployment Guide.

VMware Tools must be installed on the virtual machines.

If you add new disks, ensure that they are visible from the guest operating system.

If a virtual machine has more than one ethernet adapter, then all of them should have either static IP configuration or DHCP IP configuration. A mix of static and DHCP IP configuration is not supported on the same virtual machine.

All the virtual disks must be connected to the virtual SCSI controllers. Other controller types are not supported. Also all the virtual disks must belong to a single datastore.

Using array-based replication

Using Resiliency Platform Data Mover

Using NetBackup

For recovery on Amazon Web Services

For recovery on vCloud

The replicated storage must be provisioned to the ESX servers at each data center.

See Protecting VMware virtual machines using array-based replication - an overview.

Ensure that any file or device is not mounted on the virtual CD drive of the virtual machine.

The Resiliency Platform Data Mover virtual appliances must be part of the same ESX clusters that host the protected virtual machines in the source and target data centers.

Each host system in source and target data center must run ESXi version 6.0 U2 or later versions.

Check the acceptance level on every host system in source and target data center. Ensure that the host system's acceptance level is not set to VMwareCertified. The allowed acceptance levels are VMwareAccepted, PartnerSupported, or CommunitySupported. By default, the ESX host is set to PartnerSupported.

Virtual machine disks should be in the same datastore.

Enough storage must be available on the recovery data center for provisioning the replicated virtual machines.

Both the source and recovery (target) gateway must have external storage equivalent to 12GB for each virtual machine protected by the gateway pair. For example, if a gateway pair supports 10 virtual machines, the source and recovery (target) gateway must each have 120GB of external storage.

A maximum of 58 volumes or disks can be attached to the Replication Gateway. The total number of disks from the virtual machines in the resiliency group and the number of disks that are already attached to the gateway should not exceed more than 58. This is a VMware limitation.

Configuring resiliency group for remote recovery using Data Mover fails if a virtual machine has snapshots. Hence remove all snapshots before proceeding with the operation. This is a VMware limitation.

Virtual machines must not have any physical RDM disks.

The VMware vCenter Server user account used to add the server to Resiliency Platform must have the appropriate privileges for Data Mover.

See VMware vCenter Server privileges required for implementing Resiliency Platform Data Mover.

Ensure that any file or device is not mounted on the virtual CD drive of the virtual machine.

Every asset selected to be in the resiliency group should have a NetBackup policy of type VMware.

NetBackup master server on production and recovery data center should be running.

The vCenters or ESX servers for the selected assets should be configured in NetBackup master server.

There should be at least 1 backup schedule meeting the RPO defined in the service objective.

Ensure that the datastore on the recovery data center has enough storage capacity.

The Paravirtual (PV) Drivers for Windows must be installed. These drivers are located at:

C:\ProgramData\Symantec\VRTSsfmh\spool\addons\store\
VRTSitrptap-2.1.0.0\AWSPVDriver_7.4.3

After completing the Prepare host for replication task, follow the documentation of AWS for more information on driver installation.

Enable the UUID for the virtual machines (disk.enableuuid=true).

Ensure that the Replication Gateways have sufficient storage to handle the replication for the planned number of protected virtual machines.

Both the on-premises gateway and the cloud gateway must have external storage equivalent to 12GB for each asset protected by the gateway pair. For example, if a gateway pair supports 10 virtual machines, the on-premises gateway and the cloud gateway must each have 120 GB of external storage.

A maximum of 40 volumes or disks can be attached to the cloud Replication Gateway.

On Windows hosts, initialize and reboot the disks that are attached to IDE controller.

On Linux virtual machines, ensure that the NIC name in the file ifcfg-Auto_ens192 or ifcfg-Auto_eth0 matches with the actual NIC name on the system.

A bucket must be created in S3 and must have a policy that assigns the following permissions:

One role named ImportSnapshotRole must be created and the above policy is associated with this role. The service vmie.amazonaws.com should be able to assume this Role.

For more information about the permissions required, refer to the AWS documentation.

See Sample policy statement for AWS.

See Sample trust relationship for AWS.

Enable the UUID for the virtual machines (disk.enableuuid=true).

Install one of the following:

A maximum of 45 volumes or disks can be attached to the Replication Gateway. The total number of disks from the virtual machines in the resiliency group and the number of disks that are already attached to the gateway should not exceed more than 45.