Step 5. Include VM Groups
At the VM Groups step of the wizard, select VM groups that you want to recover, and click Add to include them in the plan. Note that you must add VMs that are running on source storage volumes — not destination volumes.
For a VM group to be displayed in the Available Groups list, it must be included into the list of plan components available for the scope, as described in section Including VM Groups. By default, the list shows only those VM groups that relate to datastores protected by storage replication — to display all existing groups, select the Show all datastore groups check box.
- Since Orchestrator orchestrates storage failover at the volume level, all VMs that belong to a specific datastore must be processed as part of the same storage plan.
- If a VM that you want to fail over stores its disk files on multiple datastores, make sure to include in the plan all VM groups related to these datastores.
Also, make sure to include the group with the .VMX file into the plan first, before the groups with .VMDK files.
- If the VMs that you want to fail over belong to a datastore in a VMware Storage DRS cluster, make sure to include in the plan all VM groups related to this cluster.
- Failover to the VMware vSphere datacenter where the source VMs reside is not supported.
- For datastores connected through the NFSv4.1 protocol, Orchestrator supports failover to a recovery location only in case target hosts included in the location have the NFSv3 export policy enabled (since the recovered datastores will be mounted to the hosts through NFSv3).
For datastores connected through other protocols, no limitations apply.
- If the LUN ID of a datastore where the selected VM groups belong is higher than 256, Orchestrator may not be able to orchestrate storage failover properly. If the LUN ID is higher than 256, make sure that your equipment supports this ID.