Restore as an Azure VM in Backup Agent

Managed Backup supports restore of Hyper-V machine as either an Azure Virtual Machine or Azure Data disk.

Step 1

After launching the Backup Agent, you can run the Restore Wizard by clicking on Restore on the Home tab if the horizontal menu.

Step 2

Click on “Next” to advance past the welcome screen for the wizard

Step 3

The next step will prompt you to select the source for the restore.

If the desired source is not in the list, you can click “Add new Storage Account” to add it.

• The backup storage is the one that contains the backup data
• The required backup prefix is set for storage account

If necessary, switch the backup prefix.

Step 4

Once the source has been selected, the next screen allows you to choose between running the plan a single time or saving it for later use.

Step 5

With the type of restore selected, the next step is to select the correct Host server which the VM resides on.

Step 6

Next, you will be presented with a list of available backup types for the selected host. Select the Restore Hyper-V Virtual Machine option to continue.

Step 7

With the correct type of restore selected, the application will generate a list of available backup plans to restore from.

Step 8

Next you will be given a choice for what point in time you would like to restore the VM to.

• Latest Version: Automatically restores the newest version of each file in the source regardless of which restore point it belongs to.
• Select the Restore Point: Restores the files as they existed at the specified restore point.

Step 9

Next, you will be able to expand the list of VM backups on the selected host and choose which to restore.

Step 10

After selecting the files or folders to restore, you are able to select the restore method. In this example we perform restore to Microsoft Azure.

• Restore as virtual disk: Restores the virtual disks in the backup as a file which can later be mounted to a VM. No configuration files are included. Several formats are available:
• Restore as Hyper-V machine: Selecting this option restores the virtual machine configuration as well as the virtual disks as files, but does not import the VM into the hypervisor by default.
  • Import Virtual Machine: Use this option to have the VM automatically imported to the hypervisor.
• Restore to Amazon Web Services: If enabled, this will restore the selected VM directly to AWS Cloud either as an EC2 instance, EBS volume, or AMI.
• Restore to Microsoft Azure: This will restore the VM directly to Azure as either an Azure Virtual Machine or Azure Data disk.

Step 11

Next you will need to determine which available checkpoint to restore for the virtual disk.

Step 12

With the checkpoint selected, you can now specify the type of instance you would like to create in Azure.

Step 13: Restore as Azure Virtual Machine

If Restore as Azure Virtual Machine was selected: The next step allows you to select the appropriate Azure account from the upper dropdown box, and specify the configuration below. These options may vary depending on the type of instance selected in the previous step.

• Computer Name: Name to assign to the new virtual machine in Azure.
• Location: Azure region where the VM will be created (e.g., East US).
• Resource group: Azure Resource Group where the VM and associated resources will be deployed.
• VM Size: Specifies the virtual hardware profile (CPU, RAM, etc.) for the VM.
• Network: Azure virtual network to connect the VM. Defines subnet and IP range.
• Use default AddressPrefix: When enabled, the default IP address prefix for the selected network will be used.
• Storage: Specifies the Azure storage account where the VM disk will be restored.
• Container: The storage container (within the selected storage account) where the VM disk will be stored.
• Boot diagnostic storage: Storage account used by Azure to save diagnostic logs during VM boot.
• Operating system: OS of the restored VM (e.g., Windows or Linux). Used for compatibility and configuration during provisioning.

Step 13: Use Temporary Instance

If Use Temporary Instance was selected, specify the Temporary Instance details.

• Computer Name: Name to assign to the new virtual machine in Azure.
• Location: Azure region where the VM will be created (e.g., East US).
• Resource group: Azure Resource Group where the VM and associated resources will be deployed.
• VM Size: Specifies the virtual hardware profile (CPU, RAM, etc.) for the VM.
• Network: Azure virtual network to connect the VM. Defines subnet and IP range.
• Use default AddressPrefix: When enabled, the default IP address prefix for the selected network will be used.
• Storage: Specifies the Azure storage account where the VM disk will be restored.
• Container: The storage container (within the selected storage account) where the VM disk will be stored.
• Boot diagnostic storage: Storage account used by Azure to save diagnostic logs during VM boot.
• Operating system: OS of the restored VM (e.g., Windows or Linux). Used for compatibility and configuration during provisioning.

Step 14: Restore as Azure Virtual Machine

After completing the Azure Virtual Machine, you’ll have to choose if using a temporary instance or copy the files locally first.

Step 14: Use Temporary Instance

If Use Temporary Instance was selected, specify the Temporary Instance details.

• Location: Azure region where the VM will be created (e.g., East US).
• Resource group: Azure Resource Group where the VM and associated resources will be deployed.
• VM Size: Specifies the virtual hardware profile (CPU, RAM, etc.) for the VM.
• Network: Azure virtual network to connect the VM. Defines subnet and IP range.
• Storage: Specifies the Azure storage account where the VM disk will be restored.
• Container: The storage container (within the selected storage account) where the VM disk will be stored.
• Boot diagnostic storage: Storage account used by Azure to save diagnostic logs during VM boot.

Step 15

Next, you will be prompted to provide the password to decrypt the VM backup data, if encrypted

Step 16

(Optional) If you restore data from the S3 Glacier Flexible Retrieval or Glacier Deep Archive storage classes, specify Smart Restore options.

Step 17

If Save restore plan was selected at the start of the wizard then the next step is to set the schedule for the restore plan. Otherwise this step will be omitted.

• No schedule (run manually): Use this option only when you wish to execute the Restore manually.
• Specific date: Use this to schedule a one-time Restore at the specified date and time.
• Recurring: Using this option enables you to schedule recurring Restorations based on the criteria in the fields below.
• Synchronize repository before run: Enable this option to ensure the file tree reflects the latest modifications made to your storage. It is a good practice to use it when you restore to a different computer

Step 18

The next step is to set any custom scripts which should execute before and/or after the restore plan runs.

Step 19

Specify the notifications options, then click Next.

Step 20

The next step of the wizard displays a summary of the selections made throughout the process. Once you have reviewed your selections, click “Next”.

You can see the saved plan on the Restore Plans tab. If Run restore once was selected at the beginning of the wizard, the plan will immediately execute once you click Next.