Step 5. Add Inventory Groups

At the Inventory Groups step of the wizard, select inventory 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 an inventory group to be displayed in the Available Groups list, it must be added to the list of inventory items available for the scope, as described in section Managing Inventory Items. By default, the list shows those inventory groups that relate to datastores protected by storage replication and datastores backed by storage systems added to Orchestrator — to display groups that contain empty datastores as well, select the Show all datastore groups check box.


  1. 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.
  2. If a VM that you want to fail over stores its disk files on multiple datastores, make sure to include in the plan all inventory 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.

  1. 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 inventory groups related to this cluster.
  2. Failover to the same VMware vSphere datacenter where the source VMs reside is not supported.
  3. Failover of VMs that store disks on volumes protected using SnapVault is not supported.
  4. Failover of VMs with RDM disks is not supported.
  5. For datastores connected through the NFSv4.1 protocol, Orchestrator supports failover to a recovery location only in the case that 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.

  1. If the LUN ID of a datastore where the selected inventory 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.
  2. For Orchestrator to be able to recover a VM correctly, the VM must have VMware Tools installed. The presence of VMware Tools is checked automatically on the vCenter Server side — for both Windows-based and Linux-based VMs. To know how to install and upgrade VMware Tools in vSphere, see this VMware KB article.


Creating Storage Plan