Consider the following when creating a protection groups:

Note: These considerations apply to both standard and high-frequency snapshots. For caveats specific to high-frequency snapshots, see here.

General Caveats

  • VMware Cloud DR does not support:
    • Shared disks
    • VMs that use Integrated Drive Electronics (IDE) disks for storage
    • Independent disks and Raw Device Mappings (RDM)
    • Encrypted VMs
  • The members of a single protection group must share the same vCenter. In other words, you cannot create a protection group that contains VMs from two different vCenters.
  • VMware Cloud DR does not support protecting VMs that belong to two different vCenters but share the same VM instanceUUID. An instanceUUID is a unique identifier that is used by vCenter Server to uniquely identify a Virtual Machine within a vCenter Server. If two VMs have the same instanceUUID, you cannot protect those VMs with VMware Cloud DR.
  • Only five snapshot replication tasks can be run concurrently across all protection groups (on all protected sites). If more than five snapshot replication tasks are started at the same time, the first five tasks are started, and the remaining snapshot tasks are queued until the first five finish, and continues until all tasks are completed.
  • VMware Cloud DR does not snapshot VM templates. If you include a VM template in a protection group, the snapshot does not capture the template.
  • Do not make any vSphere environmental or configuration changes when a snapshot is in progress, or you can experience accuracy issues with the snapshot.
  • Protection group snapshots ignore VMs that provide infrastructure services for your vSphere environment, even if the protection group definition indicates that the VM should be included. (For example, if the PG is defined with the "*" VM name pattern). Specifically, protection groups exclude the following types of VMs from snapshots:
    • VMware Cloud DR DRaaS Connector VMs.
    • VMware Cloud on AWS Management VMs.

VMware Cloud DR and VADP

If your environment is running backup software that uses VMware APIs for Data Protection (VADP), then that software’s processes might conflict with VMware Cloud DR replication as follows:
  • If a VM is being backed up another backup solution, and VMware Cloud DR starts a snapshot of the same VM after the other backup software started the backup, then the VMware Cloud DR snapshot might fail if the backup software finishes the backup before VMware Cloud DR finishes replication of the snapshot. In this case, even though the VMware Cloud DR VM snapshot failed, the next scheduled snapshot will resume from where it failed
  • If a VM snapshot is being replicated by VMware Cloud DR, and another backup solution (non-VMware Cloud DR) starts a backup of the same VM after VMware Cloud DR started replication, then the backup might fail if VMware Cloud DR finishes the replication of snapshot before the backup software finishes the backup.

For example: