In a VMware Live Site Recovery environment, if multiple protection groups are configured within a single recovery plan, this article explains whether it is possible to set priorities on a per-protection group basis and perform failover.
VMware Live Site Recovery 9.x
In a configuration where multiple Protection Groups reside within a single Recovery Plan, it is not possible to control the failover (virtual machine power-on) sequence at the Protection Group level.
During the actual recovery process, Protection Group boundaries are ignored. The power-on sequence is executed based strictly on the Priority Groups and Dependencies configured for the individual virtual machines contained within that Recovery Plan.
If strict startup order control is required for specific service groups or protection groups, implement one of the following workarounds:
・Configure Priority and Dependencies at the Virtual Machine Level
The following is how to meet the requirements using a single recovery plan and per-virtual machine power-on configuration:
1: Assign VMs belonging to the Protection Group that must start first to a higher Priority Group (e.g., Priority 1 or Priority 2).
2: Assign VMs belonging to the Protection Group that should start later to a lower Priority Group (e.g., Priority 3 or lower).
3: If application requirements dictate waiting for a specific database or service to fully initialize, configure Dependencies between the relevant virtual machines.
・ Separate Recovery Plans by Protection Group
Create individual Recovery Plans for each Protection Group. Execute the failover by running the Recovery Plans manually in the required order of priority.