Skip to content

Commit 48a7f5e

Browse files
authored
Merge pull request #210181 from v-amallick/Sept-1-2022-VMCSR
Azure VM backup - Cross Subscription Restore (GA) release
2 parents 55297dd + 46dfa2a commit 48a7f5e

File tree

5 files changed

+114
-15
lines changed

5 files changed

+114
-15
lines changed

articles/backup/backup-azure-arm-restore-vms.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Restore VMs by using the Azure portal
33
description: Restore an Azure virtual machine from a recovery point by using the Azure portal, including the Cross Region Restore feature.
44
ms.reviewer: geg
55
ms.topic: conceptual
6-
ms.date: 03/23/2022
6+
ms.date: 09/07/2022
77
author: v-amallick
88
ms.service: backup
99
ms.author: v-amallick
@@ -22,6 +22,8 @@ Azure Backup provides several ways to restore a VM.
2222
**Restore disk** | Restores a VM disk, which can then be used to create a new VM.<br/><br/> Azure Backup provides a template to help you customize and create a VM. <br/><br> The restore job generates a template that you can download and use to specify custom VM settings, and create a VM.<br/><br/> The disks are copied to the Resource Group you specify.<br/><br/> Alternatively, you can attach the disk to an existing VM, or create a new VM using PowerShell.<br/><br/> 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.
2323
**Replace existing** | You can restore a disk, and use it to replace a disk on the existing VM.<br/><br/> The current VM must exist. If it's been deleted, this option can't be used.<br/><br/> 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.<br/><br/> The snapshot is copied to the vault, and retained in accordance with the retention policy. <br/><br/> 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. <br/><br/>Replace existing is supported for unencrypted managed VMs, including VMs [created using custom images](https://azure.microsoft.com/resources/videos/create-a-custom-virtual-machine-image-in-azure-resource-manager-with-powershell/). It's unsupported for classic VMs, unmanaged VMs, and [generalized VMs](../virtual-machines/windows/upload-generalized-managed.md).<br/><br/> 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.<br><br> Replace existing is also supported for VMs with linked resources, like [user-assigned managed-identity](../active-directory/managed-identities-azure-resources/overview.md) or [Key Vault](../key-vault/general/overview.md).
2424
**Cross Region (secondary region)** | Cross Region restore can be used to restore Azure VMs in the secondary region, which is an [Azure paired region](../availability-zones/cross-region-replication-azure.md).<br><br> You can restore all the Azure VMs for the selected recovery point if the backup is done in the secondary region.<br><br> 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](about-azure-vm-restore.md#concepts) restores. The restore time for the secondary region will be almost the same as the vault tier restore time for the primary region. <br><br> This feature is available for the options below:<br><br> - [Create a VM](#create-a-vm) <br> - [Restore Disks](#restore-disks) <br><br> We don't currently support the [Replace existing disks](#replace-existing-disks) option.<br><br> Permissions<br> The restore operation on secondary region can be performed by Backup Admins and App admins.
25+
**Cross Subscription Restore** | Allows you to restore Azure Virtual Machines or disks to any subscription (as per the Azure RBAC capabilities) from restore points. <br><br> You can trigger Cross Subscription Restore for managed virtual machines only. <br><br> Cross Subscription Restore is currently enabled only in [standard policy](backup-during-vm-creation.md#create-a-vm-with-backup-configured) from Vault tier. It's also supported for [Restore with Managed System Identities (MSI)](backup-azure-arm-restore-vms.md#restore-vms-with-managed-identities). <br><br> It's unsupported from [snapshots](backup-azure-vms-introduction.md#snapshot-creation) and [secondary region](backup-azure-arm-restore-vms.md#restore-in-secondary-region) restores. <br><br> It's unsupported for [Encrypted Azure VMs](backup-azure-vms-introduction.md#encryption-of-azure-vm-backups) and [Trusted Launch VMs](backup-support-matrix-iaas.md#tvm-backup).
26+
2527

2628
>[!Tip]
2729
>To receive alerts/notifications when a restore operation fails, use [Azure Monitor alerts for Azure Backup](backup-azure-monitoring-built-in-monitor.md#azure-monitor-alerts-for-azure-backup). This helps you to monitor such failures and take necessary actions to remediate the issues.
@@ -93,6 +95,14 @@ As one of the [restore options](#restore-options), you can create a VM quickly w
9395

9496
![Restore configuration wizard - choose restore options](./media/backup-azure-arm-restore-vms/recovery-configuration-wizard1.png)
9597

98+
1. Choose the required subscription from the **Subscription** drop-down list to restore an Azure VM to a different subscription.
99+
100+
Azure Backup now supports Cross Subscription Restore (CSR), you can now restore an Azure VM using a recovery point from default subscription to another. Default subscription is the subscription where recovery point is available.
101+
102+
The following screenshot lists all subscriptions under the tenant where you've permissions, which enable you to restore the Azure VM to another subscription.
103+
104+
:::image type="content" source="./media/backup-azure-arm-restore-vms/backup-azure-cross-subscription-restore.png" alt-text="Screenshot showing the list of all subscriptions under the tenant where you have permissions.":::
105+
96106
1. Select **Restore** to trigger the restore operation.
97107

98108
>[!Note]
@@ -112,6 +122,10 @@ As one of the [restore options](#restore-options), you can create a disk from a
112122

113123
:::image type="content" source="./media/backup-azure-arm-restore-vms/trigger-restore-operation-disks.png" alt-text="Screenshot showing to select Resource disks.":::
114124

125+
1. Choose the required subscription from the **Subscription** drop-down list to restore the VM disks to a different subscription.
126+
127+
Azure Backup now supports Cross Subscription Restore (CSR). Like Azure VM, you can now restore Azure VM disks using a recovery point from default subscription to another. Default subscription is the subscription where recovery point is available.
128+
115129
1. Select **Restore** to trigger the restore operation.
116130

117131
When your virtual machine uses managed disks and you select the **Create virtual machine** option, Azure Backup doesn't use the specified storage account. In the case of **Restore disks** and **Instant Restore**, the storage account is used only for storing the template. Managed disks are created in the specified resource group. When your virtual machine uses unmanaged disks, they're restored as blobs to the storage account.

articles/backup/backup-azure-vm-backup-faq.yml

Lines changed: 24 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ metadata:
44
description: In this article, discover answers to common questions about backing up Azure VMs with the Azure Backup service.
55
ms.topic: faq
66
ms.service: backup
7-
ms.date: 07/19/2022
7+
ms.date: 09/07/2022
88
author: v-amallick
99
ms.author: v-amallick
1010

@@ -234,7 +234,26 @@ sections:
234234
Microsoft Windows allows a VM name that has maximum of 15 characters. Also, you can't specify a DNS host name that differs from the *NETBIOS* host name. However, you can create host headers for a website hosted on an Azure VM with the name as per recommendation.
235235
236236
Learn more about the [VM naming convention limitations for Azure VMs](/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou).
237-
237+
238+
- question: Can I restore an Azure Virtual Machine in a different subscription?
239+
answer: |
240+
Yes, [Cross Subscription Restore now](backup-azure-arm-restore-vms.md#restore-options) allows you to restore Azure VMs from a recovery point in one subscription to another under tenant as per Azure role-based access control (Azure RBAC) rules. Cross Subscription Restore is only supported from vault tier and not from [snapshots](backup-azure-vms-introduction.md#snapshot-creation).
241+
242+
- question: Does Cross Subscription Restore support all Azure VM?
243+
answer: |
244+
No, it's unsupported for [Encrypted Azure VMs](backup-azure-vms-introduction.md#encryption-of-azure-vm-backups) and [Trusted Launch VMs](backup-support-matrix-iaas.md#tvm-backup).
245+
246+
- question: Can I use Azure VM snapshots to restore in another subscription?
247+
answer: |
248+
No, [Cross Subscription Restore](backup-azure-arm-restore-vms.md#restore-options) is only supported from vault tier and not from [snapshots](backup-azure-vms-introduction.md#snapshot-creation).
249+
250+
- question: Can I perform Cross Subscription Restore for Azure VMs running in secondary regions?
251+
answer: |
252+
No, [Cross Subscription Restore](backup-azure-arm-restore-vms.md#restore-options) does not support restore from [secondary regions](backup-azure-arm-restore-vms.md#restore-in-secondary-region).
253+
254+
- question: Can I use Enhanced policy for Cross Subscription Restore?
255+
answer: |
256+
No, [Cross subscription Restore](backup-azure-arm-restore-vms.md#restore-options) is currently enabled only in [standard policy](backup-during-vm-creation.md#create-a-vm-with-backup-configured).
238257
239258
- name: Manage VM backups
240259
questions:
@@ -281,13 +300,13 @@ sections:
281300
282301
One way to view the retention settings for your backups, is to navigate to the backup item [dashboard](./backup-azure-manage-vms.md#view-vms-on-the-dashboard) for your VM, in the Azure portal. Selecting the link to its backup policy helps you view the retention duration of all the daily, weekly, monthly and yearly retention points associated with the VM.
283302
284-
You can also use [Backup Explorer](./monitor-azure-backup-with-backup-explorer.md) to view the retention settings for all your VMs within a single pane of glass. Go to Backup Explorer from any Recovery Services vault, go to the **Backup Items** tab and select the Advanced View to see detailed retention information for each VM.
303+
You can also use [Backup Explorer](./monitor-azure-backup-with-backup-explorer.md) to view the retention settings for all your VMs within a single pane of glass. Go to the Backup Explorer from any Recovery Services vault, go to the **Backup Items** tab and select the Advanced View to see detailed retention information for each VM.
285304
- question: When the snapshot is moved from a storage account to a vault, how is encryption in the transit managed?
286305
answer: Azure VM Backup uses [HTTPS communication for encryption in transit](guidance-best-practices.md#encryption-of-data-in-transit-and-at-rest). The data transfer uses Azure fabric (and not public endpoints), which do not need Internet access for VM backup.
287306

288307
- question: How can I disable the File Recovery option?
289308
answer: |
290-
[This API](/rest/api/backup/item-level-recovery-connections/provision) provisions a script for invoking an **iSCSI connection** for file recovery from Azure Backup.
309+
[This API](/rest/api/backup/item-level-recovery-connections/provision) provision a script for invoking an **iSCSI connection** for file recovery from Azure Backup.
291310
- You can disable this option using **custom role-definitions** by excluding API action.
292311
- You can also use the [private endpoints](private-endpoints.md) to restrict access to the iSCSI server from within the private network.
293312
- You can also disable this option across an organization using the [deny assignment](../role-based-access-control/deny-assignments.md) feature.
@@ -326,7 +345,7 @@ sections:
326345
327346
- question: How do I manage key rotations? How to ensure which key is used during backup and if it’s present to be used with the restored VM?
328347
answer: |
329-
Azure Backup backs up the secrets and KEK data of the key version during backup, and restores the same. However, booting ADE VMs with older version keys is also possible.
348+
Azure Backup backs up the secrets and KEK data of the key version during backup, and restores the same. However, booting ADE VMs with older version keys are also possible.
330349
331350
332351

articles/backup/backup-azure-vms-troubleshoot.md

Lines changed: 66 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Troubleshoot backup errors with Azure VMs
33
description: In this article, learn how to troubleshoot errors encountered with backup and restore of Azure virtual machines.
44
ms.reviewer: srinathv
55
ms.topic: troubleshooting
6-
ms.date: 07/04/2022
6+
ms.date: 09/07/2022
77
author: v-amallick
88
ms.service: backup
99
ms.author: v-amallick
@@ -233,7 +233,7 @@ If you see permissions in the **MachineKeys** directory that are different than
233233
* Under **Personal** > **Certificates**, delete all certificates where **Issued To** is the classic deployment model or **Windows Azure CRP Certificate Generator**.
234234
3. Trigger a VM backup job.
235235

236-
### ExtensionStuckInDeletionState - Extension state is not supportive to backup operation
236+
### ExtensionStuckInDeletionState - Extension state is not supportive to the backup operation
237237

238238
Error code: ExtensionStuckInDeletionState <br/>
239239
Error message: Extension state is not supportive to the backup operation
@@ -408,6 +408,70 @@ To resolve this issue:
408408
>- With a different name than the original one, **or**
409409
>- In a different resource group with the same name.
410410
411+
#### UserErrorCrossSubscriptionRestoreNotSuppportedForOLR 
412+
413+
**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForOLR 
414+
415+
**Error message**: Operation failed as Cross Subscription Restore is not supported for Original Location Recovery.
416+
417+
**Resolution**: Ensure that you [select Create New/ Restore Disk](backup-azure-arm-restore-vms.md#restore-disks) for restore operation.
418+
419+
#### UserErrorCrossSubscriptionRestoreNotSuppportedForUnManagedAzureVM  
420+
421+
**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForUnManagedAzureVM  
422+
423+
**Error message**: Operation failed as Cross Subscription Restore is not supported for Azure VMs with Unmanaged Disks.
424+
425+
**Resolution**: Perform standard restores within the same subscription instead.
426+
427+
#### UserErrorCrossSubscriptionRestoreNotSuppportedForCRR
428+
429+
**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForCRR  
430+
431+
**Error message**: Operation failed as Cross Subscription Restore is not supported along-with Cross Region Restore.
432+
433+
**Resolution**: Use either Cross Subscription Restore' or Cross Region Restore. 
434+
435+
#### UserErrorCrossSubscriptionRestoreNotSuppportedFromSnapshot 
436+
437+
**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedFromSnapshot 
438+
439+
**Error message**: Operation failed as Cross Subscription Restore is not supported when restoring from a Snapshot recovery point.
440+
441+
**Resolution**: Select a different recovery point where Tier 2 (Vault-Tier) is available.
442+
443+
#### UserErrorCrossSubscriptionRestoreInvalidTenant 
444+
445+
**Error code**: UserErrorCrossSubscriptionRestoreInvalidTenant 
446+
447+
**Error message**: Operation failed as the tenant IDs for source and target subscriptions don't match.
448+
449+
**Resolution**: Ensure that the source and target subscriptions belong to the same tenant.
450+
451+
#### UserErrorCrossSubscriptionRestoreInvalidTargetSubscription 
452+
453+
**Error code**: UserErrorCrossSubscriptionRestoreInvalidTargetSubscription 
454+
455+
**Error message**: Operation failed as the target subscription specified for restore is not registered to the Azure Recovery Services Resource Provider. 
456+
457+
**Resolution**: Ensure the target subscription is registered to the Recovery Services Resource Provider before you attempt a cross subscription restore.
458+
459+
#### UserErrorCrossSubscriptionRestoreNotSuppportedForEncryptedAzureVM
460+
461+
**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForEncryptedAzureVM
462+
463+
**Error message**: Operation failed as Cross Subscription Restore is not supported for Encrypted Azure VMs.
464+
465+
**Resolution**: Use the same subscription for Restore of Encrypted AzureVMs.
466+
467+
#### UserErrorCrossSubscriptionRestoreNotSuppportedForTrustedLaunchAzureVM
468+
469+
**Error code**: UserErrorCrossSubscriptionRestoreNotSuppportedForTrustedLaunchAzureVM
470+
471+
**Error message**: Operation failed as Cross Subscription Restore is not supported for Trusted Launch Azure VMs (TVMs).
472+
473+
**Resolution**: Use the same subscription for Restore of Trusted Launch Azure VMs.
474+
411475
## Backup or restore takes time
412476

413477
If your backup takes more than 12 hours, or restore takes more than 6 hours, review [best practices](backup-azure-vms-introduction.md#best-practices), and

0 commit comments

Comments
 (0)