The VMware HCX virtual machine protection operation is used to configure the disaster recovery settings for a virtual machine, with specific remote site resources and recovery point objectives.

Note:

For the number of concurrent virtual machine protections supported with HCX, see Configuration and Service Limits for VMware HCX.

Procedure

  1. In the vSphere Web Client, navigate to VMware HCX.
  2. Navigate to the Disaster Recovery tab and click Protect VMs.

    Protection Configuration screen appears.

    Note:

    For the number of concurrent VM protections supported with HCX, see Configuration and Service Limits for VMware HCX.

  3. Set these options as appropriate:
    • Replication Destination Site – When selected, the site loads the virtual machine Inventory for Site B. When deselected (default), Site B’s virtual machine inventory is loaded.

    • Remote Site – The 2 Sites that are paired and the current direction of Protection.

    • Source Inventory

    • Default Replication options – Global Setting Policy for all VMs within the DC or Cluster, Resource Pool, or Host.

    • Virtual Machine Replication Options:

      • Activate Compression – Helps during the seeding process of the VM. Helps if there is a low throughput LAN/WAN connectivity.

      • Activate Quiescence – Pauses the virtual machine to ensure that the most consistent copy of the virtual machine is protected on Site B.

      • Seed Virtual Machine – Used when a previous action created a copy of the VM, for example, a Bulk Migration of a virtual machine.

      • Specify Destination Container – Cluster or Resource Pool where the protected copy of the virtual machine is going to live.

      • Storage – Datastore on which the protected copy of the virtual machine resides. The Storage Policy drop-down menu lists all compatible datastores. Default Storage Policy and the corresponding datastore are used if there is no selection.

      • RPO – Recovery Point Objective for the VM. With VMware HCX, it can go from 5 minutes – 24 hours.

        Note:

        The 5 minute RPO requires the source host to be ESXi 6.0 or later for vSAN, and ESXi 6.5 for other supported datastores.

      • Snapshots Interval – Interval between Snapshots. In the event, a corrupted change was synchronized to the protect site, providing an option to recover from an earlier point in time. The event provides a Multiple Point in the Time Recovery plan for the protected VM.

      • No. of Snapshots – Total number of snapshots within the established snapshot interval.

      • Network Port group – Corresponding port group that the protected virtual machine uses. In the illustration used, the port group that the source virtual machine is using has been stretched to Site B, as a result it is automatically populated.

      Note:

      Always verify the Storage Policy and associated datastore selection, and evaluate the expected storage usage at the DR site. The settings cannot be changed once the protection is in place. Storage Policy selection is NOT available during Recovery or Test Recovery operations.

  4. Click Next. A validation of the configuration for protection is performed.
  5. Click Finish.

    The DR Dashboard is displayed. You can monitor the progress of virtual machine protection.

  6. The dashboard now shows the virtual machine being protected. Expand the dashboard.
    • Local VMs – Reflects the total # of VMs on Site B that are protected. In the preceding illustration, it shows that one local virtual machine is being protected.

    • Remote VMs – Reflects the total # of VMs on Site B that are being protected from other Sites.

    • Activity – To monitor any ongoing Disaster Recovery related operations.

    • Green Shield – DR protection is active.

    • Yellow triangle – Protection has not been tested.

    • In/Out – Direction of protection between a local site and a remote site.

  7. Log in to Site B.
  8. Go to Services > Disaster Recovery.

    The Protected virtual machine is displayed. This process shows how a virtual machine on Site A is protected on Site B using VMware HCX.