About VM Selection
This is additional information about selecting VMs for protection. It applies to both Recovery Groups and Independent Protected VMs.
- Some VMs displayed in the list may appear grayed out. This means the VMs are already protected or cannot be protected because they contain disks that cannot be replicated.
- VM disks must meet the certain requirements to be used for PD Asynchronous Replication: [See: https://cloud.google.com/compute/docs/disks/async-pd/configure#disk_requirements].
Note: PDAR can replicate only two types of disks: pd-balanced and pd-ssd.
- Additional considerations for VM protection:
- A disk's snapshot schedule will not be preserved after VM recovery.
- If a primary VM has a specific reservation configured, it will be restored using the existing reservation in the secondary region.
- If a primary VM's machine type is not supported on the secondary region, a warning will be displayed when starting VM protection. You will have the option to update the VM's properties and set a valid machine type before performing failover.
- If a primary VM instance's data encryption is configured with regional CMEK which is not available on the secondary region, the VM’s properties must be updated and a valid CMEK key set before performing failover.
- If a primary VM has sole-tenancy configured, its VM properties must be updated and a corresponding node-group set before performing failover.
- All disks of an Independent Protected VM will be assigned into a Consistency Group, and all disks of VMs under the same Recovery Group will be grouped together in a Consistency Group.
- Limitations for assigning disks to Consistency Groups are described in this article: [https://cloud.google.com/compute/docs/disks/async-pd/manage-consistency-groups#limitations]
Note: Despite adhering to the above guidelines, protection requests may still be rejected for various reasons. E.g., If protection is started for VM under a Recovery Group and AROVA detects the associated CG exceeds the maximum number of disks (which is 128), or if a VM’s disks do not match the corresponding RG’s disk zones or scope.
Also see: