Using the Azure Stack Infrastructure Backup Service to restore configuration and service data requires a complete redeployment of Azure Stack Hub. Using infrastucture backups allows you to quickly restore identity, security, and Azure Resource Manager data after a cloud recovery deployment. The following figure describes the Azure Stack recovery process.
Figure 20. Azure Stack recovery process
In the event of catastrophic data loss, where the OEM hardware is still operational, you must redploy Azure Stack Hub. During redeployment, you must specify the storage location and credentials required to access the infrastructure backups. In this mode, there is no need to specify the services that must be restored. The Infrastructure Backup Controller injects the control plane state as part of the deployment workflow.
In the event of catastrophic data loss, where the OEM hardware is inoperable, you must redeploy Azure Stack Hub on new hardware. You can do a restore of control plane data at any time after the deployment takes place. However, if the Azure Stack Hub build is more than one version later than the version used in the last backup, restores will not be supported.
Only use Cloud Recovery Mode to recover Azure Stack Hub if a disaster or product issue renders the solution unrecoverable. This deployment mode does not recover any of the IaaS, PaaS, or user data stored in the solution. The scope of this deployment mode is limited to restoring the following:
After you complete the redeployment and apply the infrastructure backups, your operators and users can log in to the Azure Stack Administration Portal. They can begin restoring PaaS services, IaaS virtual machines, and all the user data that was previously backed up, as shown in the following figure.
Figure 21. Restoring Azure Stack IaaS, PaaS, and user data
The following list provides information that can help you with planning and running a backup recovery plan for your Azure Stack Hub environment: