You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Quickstart - Back up a VM with the Azure portal
3
3
description: In this Quickstart, learn how to create a Recovery Services vault, enable protection on an Azure VM, and backup the VM, with the Azure portal.
4
-
ms.date: 05/12/2020
4
+
ms.date: 01/11/2022
5
5
ms.topic: quickstart
6
6
ms.devlang: azurecli
7
7
ms.custom: mvc, mode-ui
8
+
author: v-amallick
9
+
ms.service: backup
10
+
ms.author: v-amallick
8
11
---
9
12
10
13
# Back up a virtual machine in Azure
@@ -17,44 +20,134 @@ This quickstart enables backup on an existing Azure VM. If you need to create a
17
20
18
21
Sign in to the [Azure portal](https://portal.azure.com).
[!INCLUDE [How to create a Recovery Services vault](../../includes/backup-create-rs-vault.md)]
26
+
27
+
## Apply a backup policy
28
+
29
+
To apply a backup policy to your Azure VMs, follow these steps:
30
+
31
+
1. Go to **Backup center** and click **+Backup** from the **Overview** tab.
32
+
33
+
34
+
35
+
1. Select **Azure Virtual machines** as the **Datasource type** and select the vault you have created. Then click **Continue**.
36
+
37
+
38
+
39
+
1. Assign a Backup policy.
40
+
41
+
- The default policy backs up the VM once a day. The daily backups are retained for _30 days_. Instant recovery snapshots are retained for two days.
42
+
43
+
44
+
45
+
- If you don't want to use the default policy, select **Create New**, and create a custom policy as described in the next procedure.
46
+
47
+
20
48
## Select a VM to back up
21
49
22
50
Create a simple scheduled daily backup to a Recovery Services vault.
23
51
24
-
1. In the menu on the left, select **Virtual machines**.
25
-
2. From the list, choose a VM to back up. If you used the sample VM quickstart commands, the VM is named *myVM* in the *myResourceGroup* resource group.
26
-
3. In the **Operations** section, choose **Backup**. The **Enable backup** window opens.
52
+
1. Under **Virtual Machines**, select **Add**.
53
+
54
+
55
+
56
+
1. The **Select virtual machines** pane will open. Select the VMs you want to back up using the policy. Then select **OK**.
57
+
58
+
* The selected VMs are validated.
59
+
* You can only select VMs in the same region as the vault.
60
+
* VMs can only be backed up in a single vault.
61
+
62
+
63
+
64
+
>[!NOTE]
65
+
> All the VMs in the same region and subscription as that of the vault are available to configure backup. When configuring backup, you can browse to the virtual machine name and its resource group, even though you don’t have the required permission on those VMs. If your VM is in soft deleted state, then it won't be visible in this list. If you need to re-protect the VM, then you need to wait for the soft delete period to expire or undelete the VM from the soft deleted list. For more information, see [the soft delete for VMs article](soft-delete-virtual-machines.md#soft-delete-for-vms-using-azure-portal).
27
66
28
67
## Enable backup on a VM
29
68
30
69
A Recovery Services vault is a logical container that stores the backup data for each protected resource, such as Azure VMs. When the backup job for a protected resource runs, it creates a recovery point inside the Recovery Services vault. You can then use one of these recovery points to restore data to a given point in time.
31
70
32
-
1. Select **Create new** and provide a name for the new vault, such as *myRecoveryServicesVault*.
33
-
2. If not already selected, choose **Use existing**, then select the resource group of your VM from the drop-down menu.
71
+
To enable VM backup, in **Backup**, select **Enable backup**. This deploys the policy to the vault and to the VMs, and installs the backup extension on the VM agent running on the Azure VM.
34
72
35
-
73
+
After enabling backup:
36
74
37
-
By default, the vault is set for Geo-Redundant storage. To further protect your data, this storage redundancy level ensures that your backup data is replicated to a secondary Azure region that's hundreds of miles away from the primary region.
75
+
- The Backup service installs the backup extension whether or not the VM is running.
76
+
- An initial backup will run in accordance with your backup schedule.
77
+
- When backups run, note that:
78
+
- A VM that's running has the greatest chance for capturing an application-consistent recovery point.
79
+
- However, even if the VM is turned off, it's backed up. Such a VM is known as an offline VM. In this case, the recovery point will be crash-consistent.
80
+
- Explicit outbound connectivity isn't required to allow backup of Azure VMs.
38
81
39
-
You create and use policies to define when a backup job runs and how long the recovery points are stored. The default protection policy runs a backup job each day and retains recovery points for 30 days. You can use these default policy values to quickly protect your VM.
82
+
### Create a custom policy
40
83
41
-
3. To accept the default backup policy values, select **Enable Backup**.
84
+
If you selected to create a new backup policy, fill in the policy settings.
42
85
43
-
It takes a few moments to create the Recovery Services vault.
86
+
1. In **Policy name**, specify a meaningful name.
87
+
2. In **Backup schedule**, specify when backups should be taken. You can take daily or weekly backups for Azure VMs.
88
+
3. In **Instant Restore**, specify how long you want to retain snapshots locally for instant restore.
89
+
* When you restore, backed up VM disks are copied from storage, across the network to the recovery storage location. With instant restore, you can leverage locally stored snapshots taken during a backup job, without waiting for backup data to be transferred to the vault.
90
+
* You can retain snapshots for instant restore for between one to five days. The default value is two days.
91
+
4. In **Retention range**, specify how long you want to keep your daily or weekly backup points.
92
+
5. In **Retention of monthly backup point** and **Retention of yearly backup point**, specify whether you want to keep a monthly or yearly backup of your daily or weekly backups.
93
+
6. Select **OK** to save the policy.
94
+
> [!NOTE]
95
+
> To store the restore point collection (RPC), the Backup service creates a separate resource group (RG). This RG is different than RG of the VM. [Learn more](backup-during-vm-creation.md#azure-backup-resource-group-for-virtual-machines).
44
96
45
-
## Start a backup job
97
+
46
98
47
-
You can start a backup now rather than wait for the default policy to run the job at the scheduled time. This first backup job creates a full recovery point. Each backup job after this initial backup creates incremental recovery points. Incremental recovery points are storage and time-efficient, as they only transfer changes made since the last backup.
99
+
> [!NOTE]
100
+
> Azure Backup doesn't support automatic clock adjustment for daylight-saving changes for Azure VM backups. As time changes occur, modify backup policies manually as required.
48
101
49
-
1. On the **Backup** window for your VM, select **Backup now**.
102
+
## Start a backup job
50
103
51
-
104
+
The initial backup will run in accordance with the schedule, but you can run it immediately as follows:
52
105
53
-
2. To accept the backup retention policy of 30 days, leave the default **Retain Backup Till** date. To start the job, select **Backup**.
106
+
1. Go to **Backup center** and select the **Backup Instances** menu item.
107
+
1. Select **Azure Virtual machines** as the **Datasource type**. Then search for the VM that you have configured for backup.
108
+
1. Right-click the relevant row or select the more icon (…), and then click **Backup Now**.
109
+
1. In **Backup Now**, use the calendar control to select the last day that the recovery point should be retained. Then select **OK**.
110
+
1. Monitor the portal notifications.
111
+
To monitor the job progress, go to **Backup center** > **Backup Jobs** and filter the list for **In progress** jobs.
112
+
Depending on the size of your VM, creating the initial backup may take a while.
54
113
55
114
## Monitor the backup job
56
115
57
-
In the **Backup** window for your VM, the status of the backup and number of completed restore points are shown. Once the VM backup job is complete, information on the **Last backup time**, **Latest restore point**, and **Oldest restore point** is shown on the right-hand side of the **Overview** window.
116
+
The Backup job details for each VM backup consist of two phases, the **Snapshot** phase followed by the **Transfer data to vault** phase.
117
+
118
+
The snapshot phase guarantees the availability of a recovery point stored along with the disks for **Instant Restores** and are available for a maximum of five days depending on the snapshot retention configured by the user. Transfer data to vault creates a recovery point in the vault for long-term retention. Transfer data to vault only starts after the snapshot phase is completed.
119
+
120
+
121
+
122
+
There are two **Sub Tasks** running at the backend, one for front-end backup job that can be checked from the **Backup Job** details pane as given below:
123
+
124
+
125
+
126
+
The **Transfer data to vault** phase can take multiple days to complete depending on the size of the disks, churn per disk and several other factors.
127
+
128
+
Job status can vary depending on the following scenarios:
129
+
130
+
**Snapshot** | **Transfer data to vault** | **Job Status**
131
+
--- | --- | ---
132
+
Completed | In progress | In progress
133
+
Completed | Skipped | Completed
134
+
Completed | Completed | Completed
135
+
Completed | Failed | Completed with warning
136
+
Failed | Failed | Failed
137
+
138
+
Now with this capability, for the same VM, two backups can run in parallel, but in either phase (snapshot, transfer data to vault) only one sub task can be running. So in scenarios where a backup job in progress resulted in the next day’s backup to fail, it will be avoided with this decoupling functionality. Subsequent days' backups can have the snapshot completed, while **Transfer data to vault** is skipped if an earlier day’s backup job is in progress state.
139
+
The incremental recovery point created in the vault will capture all the churn from the most recent recovery point created in the vault. There's no cost impact on the user.
140
+
141
+
## Optional steps
142
+
143
+
### Install the VM agent
144
+
145
+
Azure Backup backs up Azure VMs by installing an extension to the Azure VM agent running on the machine. If your VM was created from an Azure Marketplace image, the agent is installed and running. If you create a custom VM, or you migrate an on-premises machine, you might need to install the agent manually, as summarized in the table.
146
+
147
+
**VM** | **Details**
148
+
--- | ---
149
+
**Windows** | 1. [Download and install](https://go.microsoft.com/fwlink/?LinkID=394789&clcid=0x409) the agent MSI file. <br><br> 2. Install with admin permissions on the machine. <br><br> 3. Verify the installation. In *C:\WindowsAzure\Packages* on the VM, right-click **WaAppAgent.exe** > **Properties**. On the **Details** tab, **Product Version** should be 2.6.1198.718 or higher. <br><br> If you're updating the agent, make sure that no backup operations are running, and [reinstall the agent](https://go.microsoft.com/fwlink/?LinkID=394789&clcid=0x409).
150
+
**Linux** | Install by using an RPM or a DEB package from your distribution's package repository. This is the preferred method for installing and upgrading the Azure Linux agent. All the [endorsed distribution providers](../virtual-machines/linux/endorsed-distros.md) integrate the Azure Linux agent package into their images and repositories. The agent is available on [GitHub](https://github.com/Azure/WALinuxAgent), but we don't recommend installing from there. <br><br> If you're updating the agent, make sure no backup operations are running, and update the binaries.</li><ul>
58
151
59
152
## Clean up deployment
60
153
@@ -66,7 +159,7 @@ If you're going to continue on to a Backup tutorial that explains how to restore
66
159
67
160
2. Choose **Stop backup**.
68
161
69
-
162
+
70
163
71
164
3. Select **Delete Backup Data** from the drop-down menu.
72
165
@@ -78,7 +171,7 @@ If you're going to continue on to a Backup tutorial that explains how to restore
78
171
6. From the list, choose your resource group. If you used the sample VM quickstart commands, the resource group is named *myResourceGroup*.
79
172
7. Select **Delete resource group**. To confirm, enter the resource group name, then select **Delete**.
80
173
81
-
174
+
0 commit comments