This tutorial takes you through the steps for backing up an Azure virtual machine (VM) to a backup vault in Azure. This article describes the classic model or Service Manager deployment model, for backing up VMs. The following steps apply only to Backup vaults created in the classic portal. Microsoft recommends using the Resource Manager model for new deployments.
If you are interested in backing up a VM to a Recovery Services vault that belongs to a Resource Group, see First look: Protect VMs with a recovery services vault.
To successfully complete the following tutorial, these prerequisites must exist:
- You have created a VM in your Azure subscription.
- The VM has connectivity to Azure public IP addresses. For additional information, see Network connectivity.
Azure has two deployment models for creating and working with resources: Resource Manager and Classic. This tutorial is for use with virtual machines created in the classic portal.
Create a backup vault
A backup vault is an entity that stores all the backups and recovery points that have been created over time. The backup vault also contains the backup policies that are applied to the virtual machines being backed up.
Starting March 2017, you can no longer use the classic portal to create Backup vaults. Existing Backup vaults are still supported, and it is possible to use Azure PowerShell to create Backup vaults. However, Microsoft recommends you create Recovery Services vaults for all deployments because future enhancements apply to Recovery Services vaults, only.
Discover and Register Azure virtual machines
Before registering the VM with a vault, run the discovery process to identify any new VMs. This returns a list of virtual machines in the subscription, along with additional information like the cloud service name and the region.
- Sign in to the Azure Classic portal
- In the Azure classic portal, click Recovery Services to open the list of Recovery Services vaults.
From the list of vaults, select the vault to back up a VM.
When you select your vault, it opens in the Quick Start page
From the vault menu, click Registered Items.
From the Type menu, select Azure Virtual Machine.
Click DISCOVER at the bottom of the page.
The discovery process may take a few minutes while the virtual machines are being tabulated. There is a notification at the bottom of the screen that lets you know that the process is running.
The notification changes when the process is complete.
- Click REGISTER at the bottom of the page.
In the Register Items shortcut menu, select the virtual machines that you want to register.
Multiple virtual machines can be registered at one time.
A job is created for each virtual machine that you've selected.
Click View Job in the notification to go to the Jobs page.
The virtual machine also appears in the list of registered items, along with the status of the registration operation.
When the operation completes, the status changes to reflect the registered state.
Install the VM Agent on the virtual machine
The Azure VM Agent must be installed on the Azure virtual machine for the Backup extension to work. If your VM was created from the Azure gallery, the VM Agent is already present on the VM; you can skip to protecting your VMs.
If your VM migrated from an on-premises datacenter, the VM probably does not have the VM Agent installed. You must install the VM Agent on the virtual machine before proceeding to protect the VM. For detailed steps on installing the VM Agent, see the VM Agent section of the Backup VMs article.
Create the backup policy
Before you trigger the initial backup job, set the schedule when backup snapshots are taken. The schedule when backup snapshots are taken, and the length of time those snapshots are retained, is the backup policy. The retention information is based on Grandfather-father-son backup rotation scheme.
- Navigate to the backup vault under Recovery Services in the Azure Classic portal, and click Registered Items.
Select Azure Virtual Machine from the drop-down menu.
Click PROTECT at the bottom of the page.
The Protect Items wizard appears and lists only virtual machines that are registered and not protected.
Select the virtual machines that you want to protect.
If there are two or more virtual machines with the same name, use the Cloud Service to distinguish between the virtual machines.
On the Configure protection menu select an existing policy or create a new policy to protect the virtual machines that you identified.
New Backup vaults have a default policy associated with the vault. This policy takes a daily snapshot each evening, and the daily snapshot is retained for 30 days. Each backup policy can have multiple virtual machines associated with it. However, the virtual machine can only be associated with one policy at a time.
A backup policy includes a retention scheme for the scheduled backups. If you select an existing backup policy, you will be unable to modify the retention options in the next step.
On Retention Range define the daily, weekly, monthly, and yearly scope for the specific backup points.
Retention policy specifies the length of time for storing a backup. You can specify different retention policies based on when the backup is taken.
Click Jobs to view the list of Configure Protection jobs.
Now that you've established the policy, go to the next step and run the initial backup.
Once a virtual machine has been protected with a policy, you can view that relationship on the Protected Items tab. Until the initial backup occurs, the Protection Status shows as Protected - (pending initial backup). By default, the first scheduled backup is the initial backup.
To start the initial backup now:
On the Protected Items page, click Backup Now at the bottom of the page.
The Azure Backup service creates a backup job for the initial backup operation.
Click the Jobs tab to view the list of jobs.
When initial backup is complete, the status of the virtual machine in the Protected Items tab is Protected.
Backing up virtual machines is a local process. You cannot back up virtual machines from one region to a backup vault in another region. So, for every Azure region that has VMs that need to be backed up, at least one backup vault must be created in that region.
Now that you have successfully backed up a VM, there are several next steps that could be of interest. The most logical step is to familiarize yourself with restoring data to a VM. However, there are management tasks that will help you understand how to keep your data safe and minimize costs.
If you have questions, or if there is any feature that you would like to see included, send us feedback.