Skip to content

Commit f0aa998

Browse files
v-ccolinv-ccolin
authored
Merge pull request #288326 from ankitaduttaMSFT/extended-zones
Backup extended zone
2 parents dae9271 + 3434216 commit f0aa998

File tree

4 files changed

+207
-2
lines changed

4 files changed

+207
-2
lines changed

‎articles/backup/backup-azure-vms-extended-zones.md

Lines changed: 194 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,194 @@
1+
---
2+
title: Back up an Azure virtual machine with Azure extended zones portal
3+
description: In this article, learn how to back up an Azure VM with the Azure Backup extended zones service.
4+
ms.topic: how-to
5+
ms.date: 09/27/2024
6+
author: ankitaduttaMSFT
7+
ms.author: ankitadutta
8+
---
9+
10+
# Back up an Azure Virtual Machine in Azure Extended Zones (preview)
11+
12+
This article describes how to back up an existing Azure VM with the [Azure Extended Zones portal](https://ms.portal.azure.com/#home).
13+
14+
Azure Backups can be created through the Azure portal. You can use the browser-based interface to create and configure backups and related resources to protect your data by taking regular backups. [Azure Backup](backup-overview.md) creates and stores recovery points in geo-redundant recovery vaults.
15+
16+
[Azure Extended Zones](../extended-zones/overview.md) provide enhanced resiliency by distributing resources across multiple physical locations within an Azure region. This approach minimizes the impact of potential failures for critical infrastructure. By using Extended Zones, your organizations can achieve higher availability and fault tolerance for their applications.
17+
18+
To use Azure Extended Zones, sign in to the [Azure Extended Zones portal](https://ms.portal.azure.com/#home).
19+
20+
## Before you start
21+
22+
Before you start backing up a VM in Extended Zones, review the [supported scenario](./backup-support-matrix-iaas.md).
23+
24+
25+
[!INCLUDE [backup-create-rs-vault.md](../../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 select **+Backup** from the **Overview** tab.
32+
33+
:::image type="content" source="./media/backup-azure-arm-vms-prepare/backup-button.png" alt-text="Screenshot showing the Backup button." lightbox="./media/backup-azure-arm-vms-prepare/backup-button.png":::
34+
35+
1. On the **Start: Configure Backup** blade, select **Azure Virtual machines** as the **Datasource type** and select the vault you have created. Then select **Continue**.
36+
37+
:::image type="content" source="./media/backup-azure-arm-vms-prepare/select-backup-goal-1.png" alt-text="Screenshot showing Backup and Backup Goal blades." lightbox="./media/backup-azure-arm-vms-prepare/select-backup-goal-1.png":::
38+
39+
1. Select the [Enhanced Backup policy](./backup-azure-vms-enhanced-policy.md), as that is the one compatible with Azure Extended Zones.
40+
41+
> [!NOTE]
42+
> To enable Azure Backup on Azure VMs in Azure Extended Zones, you can only use the Enhanced policy. This policy allows multiple daily backups, enabling hourly backups. [Learn more](backup-azure-vms-enhanced-policy.md).
43+
1. Assign the Backup policy.
44+
45+
:::image type="content" source="./media/backup-azure-arm-vms-prepare/default-policy.png" alt-text="Screenshot showing the default backup policy." lightbox="./media/backup-azure-arm-vms-prepare/default-policy.png":::
46+
47+
If you don't want to use the default policy, select **Create New**, and create a custom policy as described in the next procedure.
48+
49+
50+
## Select a VM to back up
51+
52+
To create a simple scheduled daily backup to a Recovery Services vault, follow these steps:
53+
54+
1. Under **Virtual Machines**, select **Add**.
55+
56+
:::image type="content" source="./media/backup-azure-arm-vms-prepare/add-virtual-machines.png" alt-text="Screenshot showing to add virtual machines." lightbox="./media/backup-azure-arm-vms-prepare/add-virtual-machines.png":::
57+
58+
1. The **Select virtual machines** pane opens. Select the VMs you want to back up using the policy. Then select **OK**.
59+
60+
:::image type="content" source="./media/backup-azure-arm-vms-prepare/select-vms-to-backup.png" alt-text="Screenshot showing the Select virtual machines blade." lightbox="./media/backup-azure-arm-vms-prepare/select-vms-to-backup.png":::
61+
62+
>[!NOTE]
63+
> You can configure backup for all VMs in the same region and subscription as the vault.
64+
65+
## Enable backup on a VM
66+
67+
A Recovery Services vault is a logical container that stores backup data for protected resources like Azure VMs. When a backup job runs for a protected resource, it creates a recovery point in the Recovery Services vault. You can use these recovery points to restore data to a specific point in time.
68+
69+
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.
70+
71+
After enabling backup:
72+
73+
- The Backup service installs the backup extension whether or not the VM is running.
74+
- An initial backup runs in accordance with your backup schedule.
75+
- When backups run, note that:
76+
- A VM that's running has the highest chance for capturing an application-consistent recovery point.
77+
- However, if the VM is turned off (an offline VM), it is still backed up, resulting in a crash-consistent recovery point.
78+
- Explicit outbound connectivity isn't required for back up of Azure VMs.
79+
80+
### Create a custom policy
81+
82+
If you selected to create a new backup policy, fill in the policy settings.
83+
84+
1. In **Policy name**, specify a meaningful name.
85+
2. In **Backup schedule**, specify when backups should be taken. You can take daily or weekly backups for Azure VMs.
86+
3. In **Instant Restore**, specify how long you want to retain snapshots locally for instant restore.
87+
* When you restore, backed-up VM disks are copied from storage across the network to the recovery storage location. With instant restore, you can use locally stored snapshots taken during a backup job without waiting for the backup data to transfer to the vault.
88+
* You can retain snapshots for instant restore for between one to five days. The default value is two days.
89+
4. In **Retention range**, specify how long you want to keep your daily or weekly backup points.
90+
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.
91+
6. Select **OK** to save the policy.
92+
> [!NOTE]
93+
> To enable Azure Backup on Azure VMs in Azure Extended Zones, use only the Enhanced policy. The Backup service creates a separate resource group (RG) to store the restore point collection (RPC). This RG is different from the RG of the VM.
94+
95+
:::image type="content" source="./media/backup-azure-arm-vms-prepare/new-policy.png" alt-text="Screenshot showing the new backup policy." lightbox="./media/backup-azure-arm-vms-prepare/new-policy.png":::
96+
97+
98+
## Run an on-demand backup
99+
100+
The initial backup runs in accordance with the schedule in the Backup policy. However, to run a backup job immediately, follow these steps:
101+
102+
1. Go to **Backup center** and select the **Backup Instances** menu item.
103+
1. Select **Azure Virtual machines** as the **Datasource type**. Then search for the VM that you have configured for backup.
104+
1. Select the relevant row or select the more icon (…), and then select **Backup Now**.
105+
1. In **Backup Now**, use the calendar control to select the last day that the recovery point should be retained. Then select **OK**.
106+
107+
108+
## Monitor the backup job
109+
110+
Monitor the portal notifications. To monitor the job progress, go to **Backup center** > **Backup Jobs** and filter the list for **In progress** jobs. Depending on the size of your VM, creating the initial backup may take a while.
111+
112+
The Backup job details for each VM backup consist of two phases, the **Snapshot** phase followed by the **Transfer data to vault** phase.
113+
114+
- The snapshot phase ensures 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.
115+
- Transfer data to vault creates a recovery point in the vault for long-term retention. This phase starts after the snapshot phase is completed.
116+
117+
:::image type="content" source="./media/backup-azure-arm-vms-prepare/backup-job-status.png" alt-text="Screenshot showing the backup job status." lightbox="./media/backup-azure-arm-vms-prepare/backup-job-status.png":::
118+
119+
There are two **Sub Tasks** running at the backend, one for front-end backup job that can be checked from the **Backup Job** details blade as shown:
120+
121+
:::image type="content" source="./media/backup-azure-arm-vms-prepare/backup-job-phase.png" alt-text="Screenshot showing backup job status sub-tasks." lightbox="./media/backup-azure-arm-vms-prepare/backup-job-phase.png":::
122+
123+
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.
124+
125+
Job status can vary depending on the following scenarios:
126+
127+
**Snapshot** | **Transfer data to vault** | **Job Status**
128+
--- | --- | ---
129+
Completed | In progress | In progress
130+
Completed | Skipped | Completed
131+
Completed | Completed | Completed
132+
Completed | Failed | Completed with warning
133+
Failed | Failed | Failed
134+
135+
With this capability, for the same VM, two backups can run in parallel, but only one sub task can run at a time in either the snapshot or transfer data to vault phase. This decoupling prevents next-day backups from failing due to a backup job already in progress. 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.
136+
137+
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.
138+
139+
## Optional steps
140+
141+
### Install the VM agent
142+
143+
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 already installed and running.
144+
However, if you create a custom VM or migrate an on-premises machine, you might need to install the agent manually, as summarized in the following table:
145+
146+
**VM** | **Details**
147+
--- | ---
148+
**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).
149+
**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](/azure/virtual-machines/linux/endorsed-distros) 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>
150+
151+
## Clean up deployment
152+
153+
When no longer needed, you can disable protection on the VM, remove the restore points and Recovery Services vault, then delete the resource group and associated VM resources.
154+
155+
If you want to restore the VM using the recovery points, skip the steps in this section and go to [Next steps](#next-steps).
156+
157+
1. Select the **Backup** option for your VM.
158+
159+
2. Choose **Stop backup**.
160+
161+
:::image type="content" source="./media/quick-backup-vm-portal/stop-backup.png" alt-text="Screenshot showing to stop VM backup from the Azure portal." lightbox="./media/quick-backup-vm-portal/stop-backup.png":::
162+
163+
3. Select **Delete Backup Data** from the drop-down menu.
164+
165+
4. In the **Type the name of the Backup item** dialog, enter your VM name, such as *myVM*. Select **Stop Backup**.
166+
167+
Once the VM backup has been stopped and recovery points removed, you can delete the resource group. If you used an existing VM, you may want to leave the resource group and VM in place.
168+
169+
5. In the menu on the left, select **Resource groups**.
170+
6. From the list, choose your resource group. If you used the sample VM quickstart commands, the resource group is named *myResourceGroup*.
171+
7. Select **Delete resource group**. To confirm, enter the resource group name, then select **Delete**.
172+
173+
174+
## Next steps
175+
176+
- To learn more about Azure Extended Zones, continue to [Azure Extended Zones](../extended-zones/overview.md).
177+
- To learn more about Azure VM restore, continue to [Azure VM restore](./about-azure-vm-restore.md).
178+
179+
180+
181+
182+
183+
184+
185+
186+
187+
188+
189+
190+
191+
192+
193+
194+

‎articles/backup/backup-azure-vms-introduction.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,9 @@ Azure Backup provides independent and isolated backups to guard against unintend
1515

1616
As part of the backup process, a [snapshot is taken](#snapshot-creation), and the data is transferred to the Recovery Services vault with no impact on production workloads. The snapshot provides different levels of consistency, as described [here](#snapshot-consistency). You can opt for an agent-based application-consistent/file-consistent backup or an agentless crash-consistent backup in the backup policy.
1717

18-
Azure Backup also has specialized offerings for database workloads like [SQL Server](backup-azure-sql-database.md) and [SAP HANA](sap-hana-db-about.md) that are workload-aware, offer 15 minute RPO (recovery point objective), and allow backup and restore of individual databases.
18+
Azure Backup also has specialized offerings for database workloads like [SQL Server](backup-azure-sql-database.md) and [SAP HANA](sap-hana-db-about.md) that are workload-aware, offer 15 minute RPO (recovery point objective), and allow backup and restore of individual databases.
19+
20+
You can now also back up your virtual machines with Azure Backup in Azure Extended Zones (preview). [Azure Extended Zones](../extended-zones/overview.md) (preview) provide enhanced resiliency by distributing resources across multiple physical locations within an Azure region. This approach minimizes the impact of potential failures for critical infrastructure. By using Extended Zones, your organizations can achieve higher availability and fault tolerance for their applications. Learn how to [back up an Azure VM in Azure Extended Zones (preview)](./backup-azure-vms-extended-zones.md).
1921

2022
## Backup process
2123

‎articles/backup/backup-support-matrix-iaas.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,7 @@ Back up daily via DPM or MABS | Two scheduled backups per day.
4848
Back up monthly or yearly| Not supported when you're backing up with the Azure VM extension. Only daily and weekly are supported.<br/><br/> You can set up the policy to retain daily or weekly backups for a monthly or yearly retention period.
4949
Automatically adjust the clock | Not supported.<br/><br/> Azure Backup doesn't automatically adjust for daylight saving time when you're backing up a VM.<br/><br/> Modify the policy manually as needed.
5050
[Disable security features for hybrid backup](./backup-azure-security-feature.md) |Not supported.
51+
Back up Azure VMs with Azure Extended zones | Supported through [Enhanced policy](backup-azure-vms-enhanced-policy.md).<br/><br/> Snapshot is crash-consistent only, you can also retain snapshots locally for instant restore.
5152
Back up a VM whose machine time is changed | Not supported.<br/><br/> If you change the machine time to a future date/time after enabling backup for that VM, even if the time change is reverted, successful backup isn't guaranteed.
5253
Do multiple backups per day | Supported through **Enhanced policy**. <br><br> For hourly backup, the minimum recovery point objective (RPO) is 4 hours and the maximum is 24 hours. You can set the backup schedule to 4, 6, 8, 12, and 24 hours, respectively. <br><br> Note that the maximum limit of instant recovery point retention range depends on the number of snapshots you take per day. If the snapshot count is more (for example, every *4 hours* frequency in *24 hours* duration - *6* scheduled snapshots), then the maximum allowed days for retention reduces. However, if you choose lower RPO of *12* hours, the snapshot retention is increased to *30 days*. <br><br> Learn about how to [back up an Azure VM using Enhanced policy](backup-azure-vms-enhanced-policy.md).
5354
Back up a VM with a deprecated plan when the publisher has removed it from Azure Marketplace | Not supported. <br><br> Backup is possible. However, restore will fail. <br><br> If you've already configured backup for a VM with a deprecated virtual machine offer and encounter a restore error, see [Troubleshoot backup errors with Azure VMs](backup-azure-vms-troubleshoot.md#usererrormarketplacevmnotsupported---vm-creation-failed-due-to-market-place-purchase-request-being-not-present).
@@ -181,7 +182,7 @@ Configure standalone Azure VMs in Windows Storage Spaces | Not supported.
181182
Restore with managed identities | Supported for managed Azure VMs. <br><br> Not supported for classic and unmanaged Azure VMs. <br><br> Cross-region restore isn't supported with managed identities. <br><br> Currently, this is available in all Azure public and national cloud regions. <br><br> [Learn more](backup-azure-arm-restore-vms.md#restore-vms-with-managed-identities).
182183
<a name="tvm-backup">Back up trusted launch VMs</a> | Backup is supported. <br><br> Backup of trusted launch VMs is supported through [Enhanced policy](backup-azure-vms-enhanced-policy.md). You can enable backup through a [Recovery Services vault](./backup-azure-arm-vms-prepare.md), the [pane for managing a VM](./backup-during-vm-creation.md#start-a-backup-after-creating-the-vm), and the [pane for creating a VM](backup-during-vm-creation.md#create-a-vm-with-backup-configured). <br><br> **Feature details** <br><br> - Backup is supported in all regions where trusted launch VMs are available. <br><br> - Configuration of backups, alerts, and monitoring for trusted launch VMs is supported through the backup center. <br><br> - Migration of an existing [Gen2 VM](/azure/virtual-machines/generation-2) (protected with Azure Backup) to a trusted launch VM is currently not supported. [Learn how to create a trusted launch VM](/azure/virtual-machines/trusted-launch-portal?tabs=portal#deploy-a-trusted-launch-vm). <br><br> - Item-level restore is supported for the scenarios mentioned [here](backup-support-matrix-iaas.md#support-for-file-level-restore). <br><br> Note that if the trusted launch VM was created by converting a Standard VM, ensure that you remove all the recovery points created using Standard policy before enabling the backup operation for the VM.
183184
[Back up confidential VMs](../confidential-computing/confidential-vm-overview.md) | Unsupported. <br><br> Note that the following limited preview support scenarios are discontinued and currently not available: <br><br> - Backup of Confidential VMs with no confidential disk encryption. <br> - Backup of Confidential VMs with confidential OS disk encryption through a platform-managed key (PMK).
184-
Backup of VMs with SSE and CMK encryption using HSM | Supported. <br><br> You must assign the permissions get, wrap, and uwrap key to the Key Vault to User-assgined managed identity.
185+
Backup of VMs with SSE and CMK encryption using HSM | Supported. <br><br> You must assign the permissions get, wrap, and unwrap key to the Key Vault to User-assgined managed identity.
185186

186187
## VM storage support
187188

0 commit comments

Comments
 (0)