Skip to main content

Azure Backup Recovery

 This article describes how to restore Azure VM data from the recovery points stored in Azure Backup Recovery Services vaults.


Restore options

Azure Backup provides several ways to restore a VM.

Restore optionDetails
Create a new VMQuickly creates and gets a basic VM up and running from a restore point.

You can specify a name for the VM, select the resource group and virtual network (VNet) in which it will be placed, and specify a storage account for the restored VM. The new VM must be created in the same region as the source VM.

If a VM restore fails because an Azure VM SKU wasn't available in the specified region of Azure, or because of any other issues, Azure Backup still restores the disks in the specified resource group.
Restore diskRestores a VM disk, which can then be used to create a new VM.

Azure Backup provides a template to help you customize and create a VM.

The restore job generates a template that you can download and use to specify custom VM settings, and create a VM.

The disks are copied to the Resource Group you specify.

Alternatively, you can attach the disk to an existing VM, or create a new VM using PowerShell.

This option is useful if you want to customize the VM, add configuration settings that weren't there at the time of backup, or add settings that must be configured using the template or PowerShell.
Replace existingYou can restore a disk, and use it to replace a disk on the existing VM.

The current VM must exist. If it's been deleted, this option can't be used.

Azure Backup takes a snapshot of the existing VM before replacing the disk, and stores it in the staging location you specify. Existing disks connected to the VM are replaced with the selected restore point.

The snapshot is copied to the vault, and retained in accordance with the retention policy.

After the replace disk operation, the original disk is retained in the resource group. You can choose to manually delete the original disks if they aren't needed.

Replace existing is supported for unencrypted managed VMs, including VMs created using custom images. It's unsupported for classic VMs, unmanaged VMs, and generalized VMs.

If the restore point has more or less disks than the current VM, then the number of disks in the restore point will only reflect the VM configuration.

Replace existing is also supported for VMs with linked resources, like user-assigned managed-identity or Key Vault.
Cross Region (secondary region)Cross Region restore can be used to restore Azure VMs in the secondary region, which is an Azure paired region.

You can restore all the Azure VMs for the selected recovery point if the backup is done in the secondary region.

During the backup, snapshots aren't replicated to the secondary region. Only the data stored in the vault is replicated. So secondary region restores are only vault tier restores. The restore time for the secondary region will be almost the same as the vault tier restore time for the primary region.

This feature is available for the options below:
  • Create a VM
  • Restore Disks

    We don't currently support the Replace existing disks option.

    Permissions
    The restore operation on secondary region can be performed by Backup Admins and App admins.

    • Storage accounts

    Some details about storage accounts:

    • Create VM: When you create a new VM, the VM will be placed in the storage account you specify.
    • Restore disk: When you restore a disk, the disk is copied to the storage account you specify. The restore job generates a template that you can download and use to specify custom VM settings. This template is placed in the specified storage account.
    • Replace disk: When you replace a disk in an existing VM, Azure Backup takes a snapshot of the existing VM before replacing the disk. The snapshot is also copied to the Recovery Services vault through data transfer, as a background process. However, once the snapshot phase is completed, the replace disks operation is triggered. After the replace disk operation, the disks of the source Azure VM are left in the specified Resource group for your operation and the VHDs are stored in the specified storage account. You can choose to delete or retain these VHDs and disks.
    • Storage account location: The storage account must be in the same region as the vault. Only these accounts are displayed. If there are no storage accounts in the location, you need to create one.
    • Storage type: Blob storage isn't supported.
    • Storage redundancy: Zone redundant storage (ZRS) isn't supported. The replication and redundancy information for the account is shown in parentheses after the account name.
    • Premium storage:
      • When restoring non-premium VMs, premium storage accounts aren't supported.
      • When restoring managed VMs, premium storage accounts configured with network rules aren't supported.

    VM Restore:

    Select a restore point

    1. Navigate to Backup center in the Azure portal and click Restore from the Overview tab.

    2. Select Azure Virtual machines as the Datasource type, and then select a Backup instance.

    3. Select a VM and click Continue.

    4. In the next screen that appears, select a restore point to use for the recovery.

    Choose a VM restore configuration:

    1. In Restore Virtual Machine, select a restore option:

    • Create new: Use this option if you want to create a new VM. You can create a VM with simple settings, or restore a disk and create a customized VM.

    • Replace existing: Use this option if you want to replace disks on an existing VM

    2. Specify settings for your selected restore option

    Create a VM:

    As one of the restore options, you can create a VM quickly with basic settings from a restore point.

    1. In Restore Virtual Machine > Create new > Restore Type, select Create a virtual machine.

    2. In Virtual machine name, specify a VM that doesn't exist in the subscription.

    3. In Resource group, select an existing resource group for the new VM, or create a new one with a globally unique name. If you assign a name that already exists, Azure assigns the group the same name as the VM.

    4. In Virtual network, select the VNet in which the VM will be placed. All VNets associated with the subscription in the same location as the vault, which are active and not attached with any affinity group, are displayed. Select the subnet.

      The first subnet is selected by default.

    5. In Staging Location, specify the storage account for the VM.

         6. Select Restore to trigger the restore operation

    Comments

    Post a Comment

    Popular posts from this blog

    Connect SparkThriftServer with Tableau/PowerBI

      Connect SparkThriftServer with Tableau/PowerBI REFERENCE : https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-apache-spark-use-bi-tools Use Power BI for Spark data visualization Note This section is applicable only for Spark 1.6 on HDInsight 3.4 and Spark 2.0 on HDInsight 3.5.   Once you have saved the data as a table, you can use Power BI to connect to the data and visualize it to create reports, dashboards, etc.   1.       Make sure you have access to Power BI. You can get a free preview subscription of Power BI from http://www.powerbi.com/ . 2.       Sign in to Power BI . 3.       From the bottom of the left pane, click Get Data . 4.       On the Get Data page, under Import or Connect to Data , for Databases , click Get . 5.       On the next screen, click Spark on Azure HDInsight and then click Connect . When prompted, enter th...
    Post a Comment
    Read more

    Docker In Details

      Course Contents:- 1. Overview of Docker 2. Difference between Virtualization & Containerization 3. Installation & Configuration of Docker Runtime on Linux & Windows 4. Practice on Docker commands 5. launch a Webserver in a container 6. Launch public & official images of application like Jenkins, Nginx, DB etc.. 7. Launch a base OS Container 8. How to save changes inside the container & create a fresh image(commit) 9. How to ship image & container from one hardware to another. 10. How to remove stop/rm multiple container/images 11. Docker Registry 12. Docker Networking       Check current docker network                  Docker Network Bridge                     Docker Network Weaving                  Launch our own Docker Cluster with our defined Network             ...
    Post a Comment
    Read more

    Roadmap to DevOps

        DevOps is nothing but the combination of process and philosophies which contains four basic component culture, collaboration, tools, and practices. In return, this gives a good automated system and infrastructure which helps an organisation to deliver a quality and reliable build. The beauty of this culture is it enables a quality for organizations to better serve their customers and compete more effectively in the market and also add some promised benefits which include confidence and trust, faster software releases, ability to solve critical issues quickly, and better manage unplanned work.   1. What are the tasks of a DevOps Engineer? Design, build, test and deploy scalable, distributed systems from development through production Manage the code repository(such as Git, SVN, BitBucket, etc.) including code merging and integrating, branching and maintenance and remote repository management Manage, configure and maintain infra...
    Post a Comment
    Read more

    Git

    Git Git  has steadily risen from being just a preferred skill to a must-have skill in last few years. in this blog we will go through top 20 git commands that every devops uses daily. If you don't have a gitlab account. please follow below link to create it free.   https://gitlab.com/ before using git please install git on your linux machine using below command. yum install git -y Use below command to create ssh keyol ssh-keygen -t rsa Below are the git command which we will cover in this blog. ·          git config ·          git init ·          git clone ·          git add ·          git commit ·          git diff ·          git reset ·      ...
    2 comments
    Read more

    Azure VM Snapshot

      Create a VM from a VHD by using the Azure portal Create a snapshot and then create a disk from the snapshot. This strategy allows you to keep the original VHD as a fallback: 1.       From the  Azure portal , on the left menu, select  All services . 2.       In the  All services  search box, enter  disks  and then select  Disks  to display the list of available disks. 3.       Select the disk that you would like to use. The  Disk  page for that disk appears. 4.       From the menu at the top, select  Create snapshot . 5.       Enter a  Name  for the snapshot. 6.       Choose a  Resource group  for the snapshot. You can use either an existing resource group or create a new one. 7.       For  Account type , choose ei...
    Post a Comment
    Read more