Managing Recovery Locations
Recovery locations are groups of target resources (that is, infrastructure objects such as hosts, clusters and storage) used by Orchestrator to orchestrate recovery. Resource groups are managed by Veeam ONE Client, a component of the embedded Veeam ONE server installed on the Orchestrator server.
To allow Orchestrator to process resource groups properly, you must connect vCenter Servers — not standalone ESXi hosts — to Veeam Backup & Replication servers orchestrated by Orchestrator. To learn how to add VMware vSphere servers to the backup infrastructure, see the Veeam Backup & Replication User Guide, section Virtualization Servers and Hosts.
Before you run a restore plan or perform a failback operation, you can choose whether to recover VMs included in the plan to the original or to a new location:
- If you want to restore VMs to their original location, you do not need to configure any resources.
Orchestrator already includes an out-of-the-box ready-to-use location named Original VM Location — if you select this location, Orchestrator will automatically detect the original location of processed VMs and restore the VMs to that location.
You can only customize datastore capacity level and enable Instant VM Recovery for the location. For more information, see Configuring Original Recovery Location.
- If you want to restore VMs to a different location, you must first categorize vCenter Server resources into restore recovery locations.
Storage recovery locations are used to define target storage systems and compute resources to be used to recover VMs when running storage plans.
Storage recovery locations are populated based on information from connected vCenter Servers — resources for these locations are categorized into groups based on vCenter Server Tags that use metadata attached in the vSphere inventory. Resource membership in these groups cannot be edited in the Orchestrator UI — you must modify tags in the vCenter environment. To learn how to add metadata to infrastructure objects in the vSphere inventory, see VMware Docs.