Restore to Azure VM Using Management Console
New Backup Format
Management Console currently does not support restoring the disk image backups in new backup format to Microsoft Azure. Use the Backup Agent to perform this operation.
Restore Legacy Image-Based Backups to Azure VM
Note that you must have the Restore to EC2 / Azure VM option enabled in Management Console. This feature can be enabled by request. To send a request, proceed as follows:
- Open the Management Console.
- In the Settings menu, select Global Agent Options.
- Find the Restore to EC2 / Azure VM option group, then click Send Request.
Before You Begin
First, make sure you have a sufficient space for temporary instance and for restored machine (Microsoft Azure VM) available.
To prepare your environment for this restore job, read the article.
You also will need to set the temporary storage account, which will be used to store the intermediate .vhdx/.vhd file and perform the import operations. The .vhdx/,vhd file will be placed to implicitly selected storage. When the restore starts, the Backup Agent downloads the disk data of the backup, locally processes it in memory and then puts the blocks of the *.vhdx disk file to the remote cloud bucket.
Restore Legacy Image-Based Backups in Management Console
To restore VM image to Azure VM perform the following:
- Open the Management Console.
- On Backup select Restore to Cloud (or Computers > Restore to Cloud if you are using legacy menu).
- Click Restore to Azure option
- As the restore wizard opens, specify the data source parameters:
Plan Name. The plan name will appear on the Management Console
User. Select the user which storage account contains the data
Destination. Select the storage account that contains the data
Computer. Select the computer which data is to be restored
Point in Time. Select the disk image backup version to restore. Click Next.
In fact, you can even select any disk image backup: Azure as source storage is not the mandatory condition for this.
Note that for the following backup destinations: any local or shared folders, LAN-only Minio, FTP, SFTP, S3-Compatible, and OpenStack applications for NAS, intranet OpenStack clusters restore via temporary instance is impossible
- In the second step, specify the disk partitions to restore. Once you are done, click Next.
Next, specify the target instance parameters:
- Azure Account. The account under which a new Azure VM instance will be stored.
- Computer Name.
- Location. The region that is to store the newly created Azure instance.
- Resource Group. Azure Resource Group.
- VM Size. Select the required VM size that meets your requirements in terms of cores and RAM.
- Subnet. Select one of the available subnets.
- Storage. Select your Azure storage.
- Container. The Azure container is to store the temporary disk for VM import.
- Boot Diagnostic Storage. Select the storage where you'd like to place diagnostic files. You can leave this option disabled.
To restore properly, Managed Backup uses a temporary Azure instance. In the next step, configure this instance's parameters. Managed Backup automatically copies the values from the previous step: if you modify these values, ensure that the target virtual machine has sufficient configuration and permissions.
Specify encryption password if you have encrypted objects. Consider, there is no password validation on this step. In case of wrong password, the restire will fail.
In a Preview step, review all the specified information earlier in the wizard, make sure everything is correct, then click Save and Run to start the restore.
If you click Save, the plan will be saved on the **Restore To Cloud ** where you can start it manually at any time.
During the plan execution, the progress is displayed in the Management Console.
Manage Azure Instance
You can access and manage the instance from Azure Management console.
In case you have Backup or Restore Agent on restored Azure instance you also can use the Remote Management or Backup > Computers tab in the same way you usually manage your regular computers.