This is an archive version of the document. To get the most up-to-date information, see the current version.Managing Recovery Locations
Recovery locations consist of resource groups (that is, infrastructure objects such as vSphere hosts) used as target locations when orchestrating recovery. Resource groups are managed by the embedded Veeam ONE server installed on the Orchestrator server.
Orchestrator provides 3 types of recovery locations — Restore Recovery Locations, Storage Recovery Locations and Cloud Recovery Locations.
Restore recovery locations are used to define compute and storage resources in a vSphere environment required when running restore plans and performing failback operations.
Before you run a restore plan or perform a failback operation, you can choose whether to recover machines 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. However, the original VM location does not apply to Veeam agent backups, only to vSphere VM backups.
Orchestrator already includes a built-in recovery 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 customize datastore capacity level, set backup copy preference, allow VM recovery across different locations and enable Instant VM Recovery for the location. For more information, see Configuring Original Recovery Location.
- If you want to restore machines to a different location, you must first categorize vCenter Server resources into restore recovery locations.
For more information on working with restore recovery locations, see sections Adding Recovery Locations, Configuring Recovery Locations and Allowing Access to Recovery Locations.
Storage recovery locations are used to define target storage systems and compute resources required when running storage plans.
Storage recovery locations are populated with connected storage systems, and with compute resources from connected vCenter Servers — vCenter Server resources are categorized into groups based on vCenter Server Tags on hosts and clusters. Resource membership in these groups cannot be edited in the Orchestrator UI — you must modify the tags in the vCenter environment. To learn how to tag infrastructure objects in the vSphere inventory, see VMware Docs.
For more information on working with storage recovery locations, see sections Adding Recovery Locations, Configuring Recovery Locations and Allowing Access to Recovery Locations.
Cloud recovery locations are used to define cloud resources required when running cloud plans.
Orchestrator 6.0 allows you to recover machines to Microsoft Azure. For limitations that may apply for restoring machines to Microsoft Azure, see the Veeam Backup & Replication User Guide, section Limitations to Restore to Microsoft Azure.
Note |
Restore to Microsoft Azure does not support Azure Hybrid Benefit. This means that all machines recovered to Microsoft Azure are deployed as unlicensed VMs. If required, you can apply your on-premises license by enabling the Azure Hybrid Benefit option after recovery, which will allow you to run your Azure VMs at a reduced cost. |
Before creating a cloud recovery location, ensure that:
- The Veeam Backup & Replication server that will manage the process of recovering machines to Microsoft Azure is running version 12.0 or later.
- You have a Microsoft Azure compute account added to the Veeam Backup & Replication server. For more information on adding a Microsoft Azure compute account, see the Veeam Backup & Replication User Guide, section Microsoft Azure Compute Accounts.
For more information on working with cloud recovery locations, see sections Adding Recovery Locations, Configuring Recovery Locations and Allowing Access to Recovery Locations.
