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
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-vm-migrate-enhanced-policy.md
+80-9Lines changed: 80 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Move VM backup - standard to enhanced policy in Azure Backup
3
3
description: Learn how to trigger Azure VM backups migration from standard policy to enhanced policy, and then monitor the configuration backup migration job.
4
4
ms.topic: reference
5
-
ms.date: 05/19/2025
5
+
ms.date: 05/27/2025
6
6
ms.service: azure-backup
7
7
author: jyothisuri
8
8
ms.author: jsuri
@@ -11,19 +11,22 @@ ms.custom:
11
11
- build-2025
12
12
---
13
13
14
-
# Migrate Azure VM backups from standard to enhanced policy (preview)
14
+
# Migrate Azure VM backups from standard to enhanced policy
15
15
16
-
This article describes how to migrate Azure VM backups from standard to enhanced policy using Azure Backup.
16
+
This article describes how to migrate Azure Virtual Machine (VM) backups from standard to enhanced policy using Azure Backup.
17
17
18
18
Azure Backup now supports migration to the enhanced policy for Azure VM backups using standard policy. The migration of VM backups to enhanced policy enables you to schedule multiple backups per day (up to every 4 hours), retain snapshots for longer duration, and use multi-disk crash consistency for VM backups. Snapshot-tier recovery points (created using enhanced policy) are zonally resilient. The migration of VM backups to enhanced policy also allows you to migrate your VMs to Trusted Launch and use Premium SSD v2 and Ultra-disks for the VMs without disrupting the existing backups.
19
19
20
+
>[!Note]
21
+
>Standard policy supports backup only for unprotected trusted launch VMs via PowerShell (version Az 14.0.0 and later), and REST API (version 2025-01-01 and later). To enable trusted launch for existing VMs protected by Standard Policy, migrate to Enhanced Policy first.
22
+
20
23
## Considerations
21
24
22
25
- Before you start the migration, ensure that there are no ongoing backup jobs for the VM that you plan to migrate.
23
26
- Migration is supported for Managed VMs only and isn’t supported for Classic or unmanaged VMs.
24
27
- Once the migration is complete, you can’t change the backup policy back to standard policy.
25
28
- Migration operations trigger a backup job as part of the migration process and might take up to several hours to complete for large VMs.
26
-
- The change from standard policy to enhanced policy can result in additional costs. [Learn More](backup-instant-restore-capability.md#cost-impact).
29
+
- The change from standard policy to enhanced policy can result in extra costs. [Learn More](backup-instant-restore-capability.md#cost-impact).
27
30
28
31
>[!Note]
29
32
> If the VM already has a shared disk attached to it, then perform migration by following these steps:
@@ -43,27 +46,95 @@ To do the policy migration, follow these steps:
43
46
44
47
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/select-backup-item-type.png" alt-text="Screenshot shows the selection of backup type as Azure VM." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/select-backup-item-type.png":::
45
48
46
-
4. On the **Backup Items**blade, you can view the list of *protected VMs* and *last backup status with latest restore points time*.
49
+
4. On the **Backup Items**pane, you can view the list of *protected VMs* and *last backup status with latest restore points time*.
47
50
48
51
Select **View details**.
49
52
50
53
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/view-backup-item-details.png" alt-text="Screenshot shows how to view the backup item details." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/view-backup-item-details.png":::
51
54
52
-
5. On the **Change Backup Policy**blade, select **Policy subtype** as **Enhanced**, choose a *backup policy* to apply to the virtual machine, and then select **Change**.
55
+
5. On the **Change Backup Policy**pane, select **Policy subtype** as **Enhanced**, choose a *backup policy* to apply to the virtual machine, and then select **Change**.
53
56
54
57
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/change-to-enhanced-policy.png" alt-text="Screenshot shows how to change the Azure VM backup policy to enhanced." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/change-to-enhanced-policy.png":::
55
58
56
59
## Monitor the policy migration job
57
60
58
-
To monitor the migration job on the **Backup Items**blade, select **View jobs**.
61
+
To monitor the migration job on the **Backup Items**pane, select **View jobs**.
59
62
60
-
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/view-backup-migration-job-progress.png" alt-text="Screenshot shows how to go to the Backup Jobs blade." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/view-backup-migration-job-progress.png":::
63
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/view-backup-migration-job-progress.png" alt-text="Screenshot shows how to go to the Backup Jobs pane." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/view-backup-migration-job-progress.png":::
61
64
62
65
The migration job is listed with Operation type Configure backup (Migrate policy).
## Migrate protected VMs to Enhanced policy in bulk.
70
+
71
+
Azure Backup allows seamless bulk migration of protected VMs from the Standard policy to the Enhanced policy. This transition strengthens security, enhances operational efficiency, and optimizes data protection across your Azure infrastructure.
72
+
73
+
**Choose a path to change policy**:
74
+
75
+
# [Backup Items tile](#tab/backup-items-tile)
76
+
77
+
To trigger bulk migration of VMs protected using Standard policy to an Enhanced policy using the **Backup Items** tile, follow these steps:
78
+
79
+
1. In the [Azure portal](https://portal.azure.com/), go the **Recovery Services vault**.
80
+
1. On the **Backup Items** tile, select **Azure Virtual Machine**.
81
+
1. On the **Backup Items** pane, select the VMs from the list of protected VMs (using Standard policy) that you want to migrate, and then select **Change policy**.
82
+
83
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/change-policy-for-backup-items.png" alt-text="Screenshot shows how to change policy from the Backup Items pane." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/change-policy-for-backup-items.png":::
84
+
85
+
1. On the **Change policy** pane, on the **Basics** tab, review the selection of VMs, and then select **Next > Target policy**.
86
+
87
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/review-vm-selection-for-change-policy.png" alt-text="Screenshot shows how to review the VM selection." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/review-vm-selection-for-change-policy.png":::
88
+
89
+
You can modify the VM selection if necessary.
90
+
91
+
1. On the **Target policy** tab, under **Target policy**, select a target Enhanced policy from the dropdown list.
92
+
93
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/select-enhanced-policy.png" alt-text="Screenshot shows how to select a different backup policy." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/select-enhanced-policy.png":::
94
+
95
+
1. Review the selected Enhanced policy details, and then select **Next > Review + Change policy**.
96
+
1. On the **Review + Change policy** tab, verify the selection of VMs and target policy, and then select **Change policy**.
97
+
98
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/trigger-change-policy.png" alt-text="Screenshot shows how to trigger the change policy operation." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/trigger-change-policy.png":::
To trigger bulk migration of VMs protected using Standard policy to an Enhanced policy via the **Backup Policies** pane, follow these steps:
104
+
105
+
1. In the [Azure portal](https://portal.azure.com/), go the **Recovery Services vault** >**Backup Policies**.
106
+
1. On the **Backup Policy** pane, select a backup policy with **Policy sub type** as **Standard**.
107
+
108
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/select-standard-policy.png" alt-text="Screenshot shows the selection of a Standard backup policy." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/select-standard-policy.png":::
109
+
110
+
1. On the **Modify policy** pane, select **Associated items**.
111
+
112
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/select-associated-items-option.png" alt-text="Screenshot shows the selection of the Associated items option." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/select-associated-items-option.png":::
113
+
114
+
1. On the **Associated items** pane, select the VMs to migrate, and then select **Change policy**.
115
+
116
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/view-associated-items.png" alt-text="Screenshot shows the associated items to the policy." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/view-associated-items.png":::
117
+
118
+
1. On the **Change policy** pane, on the **Basics** tab, review the selection of VMs, and then select **Next > Target policy**.
119
+
120
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/review-vm-selection-for-change-policy-1.png" alt-text="Screenshot shows the VMs associated with the policy." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/review-vm-selection-for-change-policy-1.png":::
121
+
122
+
You can modify the VM selection if necessary.
123
+
124
+
1. On the **Target policy** tab, under **Target policy**, select a target Enhanced policy from the dropdown list.
125
+
126
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/select-enhanced-policy-1.png" alt-text="Screenshot shows the selection of a different backup policy." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/select-enhanced-policy-1.png":::
127
+
128
+
1. Review the selected Enhanced policy details, and then select **Next > Review + Change policy**.
129
+
1. On the **Review + Change policy** tab, verify the selection of VMs and target policy, and then select **Change policy**.
130
+
131
+
:::image type="content" source="./media/backup-azure-vm-migrate-enhanced-policy/trigger-change-policy-1.png" alt-text="Screenshot shows how to run the change policy operation." lightbox="./media/backup-azure-vm-migrate-enhanced-policy/trigger-change-policy-1.png":::
132
+
133
+
134
+
---
135
+
66
136
## Next steps
67
137
68
-
- Learn about [standard VM backup policy](backup-during-vm-creation.md#create-a-vm-with-backup-configuration).
138
+
- Learn about [Standard VM backup policy](backup-during-vm-creation.md#create-a-vm-with-backup-configuration).
69
139
- Learn how to [back up an Azure VM using Enhanced policy](backup-azure-vms-enhanced-policy.md).
@@ -19,7 +19,7 @@ Azure Backup now supports Enhanced policy for Azure VM backup that offers:
19
19
- Longer retention in snapshot (operational) tier up to 30 days.
20
20
21
21
>[!Note]
22
-
>- Standard policy doesn't support protecting newer Azure offerings, such as Ultra SSD and Premium SSD v2. Backup of trusted launch VM using standard policy is available in preview in [selected regions](backup-support-matrix-iaas.md#tvm-backup).
22
+
>- Standard policy doesn't support protecting newer Azure offerings, such as Ultra SSD and Premium SSD v2. Only PowerShell (version Az 14.0.0 and later), and REST API (version 2025-01-01 and later) support trusted launch VM backup with Standard policy.
23
23
>- Backups for VMs with data access authentication enabled disks fails.
24
24
>- Protection of a VM with an enhanced policy incurs additional snapshot costs. [Learn more](backup-instant-restore-capability.md#cost-impact).
25
25
>- Once you enable a VM backup with Enhanced policy, Azure Backup doesn't allow to change the policy type to Standard.
@@ -118,7 +118,7 @@ In this sample cmdlet:
118
118
- The second and third command fetches the India timezone and updates the timezone in the $schedulePolicy.
119
119
- The fourth and fifth command initializes the schedule window start time and updates the $schedulePolicy.
120
120
121
-
>[Note]
121
+
>[!Note]
122
122
>The start time must be in UTC even if the timezone is not UTC.
123
123
124
124
- The sixth and seventh command updates the interval (in hours) after which the backup will be retriggered on the same day, duration (in hours) for which the schedule will run.
description: In this article, learn how to troubleshoot errors encountered with backup and restore of Azure virtual machines.
4
4
ms.reviewer: srinathv
5
5
ms.topic: troubleshooting
6
-
ms.date: 01/21/2025
6
+
ms.date: 06/02/2025
7
7
ms.service: azure-backup
8
8
author: jyothisuri
9
9
ms.author: jsuri
@@ -577,3 +577,15 @@ Get more information on how to set up a static IP through PowerShell:
577
577
578
578
* [How to add a static internal IP to an existing VM](/powershell/module/az.network/set-aznetworkinterfaceipconfig#description)
579
579
* [Change the allocation method for a private IP address assigned to a network interface](../virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps.md)
580
+
581
+
## Migration from Standard to Enhanced policy issue
582
+
583
+
### BackUpOperationFailedV2
584
+
585
+
**Error code**: `BackUpOperationFailedV2`
586
+
587
+
**Error message**: The backups of VMs have failed after the policy migration from Standard to Enhanced policy.
588
+
589
+
**Cause**: Snapshot retention of the Enhanced policy is applied on the older recovery points that were originally created under the Standard policy when you move a VM from a Standard to Enhanced policy.
590
+
591
+
**Recommended action**: Contact Microsoft Support for resolution.
Copy file name to clipboardExpand all lines: articles/backup/backup-instant-restore-capability.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Azure Instant Restore Capability
3
3
description: Azure Instant Restore Capability and FAQs for VM backup stack, Resource Manager deployment model
4
4
ms.topic: overview
5
-
ms.date: 04/02/2025
5
+
ms.date: 05/19/2025
6
6
author: jyothisuri
7
7
ms.author: jsuri
8
8
---
@@ -57,7 +57,8 @@ Enhanced policy uses Managed disk snapshots for Instant Restore functionality. T
57
57
For example, a VM with 100GB in size has a change rate of 2% and retention of 5 days for Instant Restore. In this case, the snapshot storage billed will be 108GB (100 + 100 X 0.02 X 4).
58
58
59
59
>[!NOTE]
60
-
>Snapshot retention is fixed to 5 days for weekly policies for Standard policy and can vary between 5 to 20 days for enhanced policy.
60
+
>- Snapshot retention is fixed to 5 days for weekly policies for Standard policy and can vary between 5 to 20 days for enhanced policy.
61
+
>- Trusted Launch virtual machines with standard policy use managed disk snapshots for Instant Restore. In this scenario, you incur Snapshot storage cost same as that of Enhanced policy.
Copy file name to clipboardExpand all lines: articles/backup/backup-support-matrix-iaas.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -185,7 +185,7 @@ Back up Azure VMs with locks | Supported for managed VMs. <br><br> Not supported
185
185
Configure standalone Azure VMs in Windows Storage Spaces | Not supported.
186
186
[Restore Virtual Machine Scale Sets](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes#scale-sets-with-flexible-orchestration) | Supported for the flexible orchestration model to back up and restore a single Azure VM.
187
187
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).
188
-
<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#run-an-on-demand-backup-after-vm-creation), and the [pane for creating a VM](backup-during-vm-creation.md#create-a-vm-with-backup-configuration). <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.
188
+
<a name="tvm-backup">Back up trusted launch VMs</a> | Supported via [Enhanced policy](backup-azure-vms-enhanced-policy.md) and [Standard policy](backup-instant-restore-capability.md). <br><br> **Feature details**: <br><br> - Backup is supported in all regions where trusted launch VMs are available. <br> - Item-level restore is supported for the [applicable scenarios](#support-for-file-level-restore). <br><br> **Backup support via Enhanced policy**: <br><br> - Azure portal, PowerShell, and REST API clients support trusted launch VM backup with Enhanced policy. <br> - The Azure portal allows you to enable backup through a [Recovery Services vault](backup-azure-arm-vms-prepare.md), the [VM management pane](backup-during-vm-creation.md#run-an-on-demand-backup-after-vm-creation), and the VM creation pane. <br> - Azure Business Continuity Center supports [backup](../business-continuity-center/tutorial-configure-protection-datasource.md), [alerts](../business-continuity-center/tutorial-monitor-alerts-metrics.md), and [monitoring](../business-continuity-center/tutorial-monitor-protection-summary.md) for trusted launch VMs. <br><br> **Backup support via Standard policy**: <br><br> - PowerShell (version Az 14.0.0 and later), and REST API (version 2025-01-01 and later) only support trusted launch VM backup with Standard policy. <br> - Trusted Launch virtual machines with standard policy use managed disk snapshots for Instant Restore. In this scenario, you incur Snapshot storage cost same as that of Enhanced policy. [Learn more](backup-instant-restore-capability.md#cost-impact). <br><br> Note that migration of an existing Gen2 VM (protected by Azure Backup Standard policy) to Trusted Launch VM requires first [switching to Enhanced policy](backup-azure-vm-migrate-enhanced-policy.md).
189
189
[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).
190
190
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-assigned managed identity.
0 commit comments