A recovery plan is the automated plan (runbook) for full or partial failover from Region A to Region B.

Virtual machine priority determines virtual machine startup order.

All priority 1 virtual machines are started before priority 2 virtual machines.

All priority 2 virtual machines are started before priority 3 virtual machines.

All priority 3 virtual machines are started before priority 4 virtual machines.

All priority 4 virtual machines are started before priority 5 virtual machines.

You can additionally set startup order of virtual machines within each priority group.

You can configure the following timeout parameters:

Response time, which defines the time to wait after the first virtual machine powers on before proceeding to the next virtual machine in the plan.

Maximum time to wait if the virtual machine fails to power on before proceeding to the next virtual machine.

You can adjust response time values as necessary during execution of the recovery plan test to determine the appropriate response time values. 

When you create a recovery plan, you must configure test network options. The following options are available.

Isolated Network (Automatically Created)

An isolated private network is created automatically on each ESXi host in the cluster for a virtual machine that is being recovered. Site Recovery Manager creates a standard switch and a port group on it. A limitation of this automatic configuration is that a virtual machine connected to the isolated port group on one ESXi host cannot communicate with a virtual machine on another ESXi host. This option limits testing scenarios and provides an isolated test network only for basic virtual machine testing.

Port Group

Selecting an existing port group provides a more granular configuration to meet your testing requirements. If you want virtual machines across ESXi hosts to communicate, use either a standard or distributed switch with uplinks to the production network, and create a port group on the switch that is tagged with a non-routable VLAN. In this way, the network is isolated and cannot communicate with other production networks.

Because the isolated application networks are fronted by a load balancer, the recovery plan test network is equal to the recovery plan production network and provides realistic verification of a recovered management application.

Recovery Plan Test Network Design Decision

Decision ID

Design Decision

Design Justification

Design Implication


Use the target recovery production network for testing.

The design of the application virtual networks supports their use as recovery plan test networks.

During recovery testing, a management application will not be reachable using its production FQDN. Either access the application using its VIP address or assign a temporary FQDN for testing. Note that this approach will result in certificate warnings due to name and certificate mismatches.