Skip to content

Commit 46de594

Browse files
Merge pull request #227271 from AbhishekMallick01/Feb-14-2023-VM
VM restore doc updates
2 parents 68e4693 + e9a0251 commit 46de594

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

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

Lines changed: 2 additions & 3 deletions
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: 12/06/2022
6+
ms.date: 02/14/2023
77
ms.service: backup
88
author: jyothisuri
99
ms.author: jsuri
@@ -225,7 +225,6 @@ Currently, secondary region [RPO](azure-backup-glossary.md#rpo-recovery-point-ob
225225

226226
>[!NOTE]
227227
>
228-
>- You can cancel the restore job till the data transfer phase. Once it enters VM creation phase, you can't cancel the restore job.
229228
>- The Cross Region Restore feature restores CMK (customer-managed keys) enabled Azure VMs, which aren't backed-up in a CMK enabled Recovery Services vault, as non-CMK enabled VMs in the secondary region.
230229
>- The Azure roles needed to restore in the secondary region are the same as those in the primary region.
231230
>- While restoring an Azure VM, Azure Backup configures the virtual network settings in the secondary region automatically. If you are [restoring disks](#restore-disks) while deploying the template, ensure to provide the virtual network settings, corresponding to the secondary region.
@@ -249,7 +248,7 @@ In summary, the **Availability Zone** will only appear when
249248
![Choose availability zone](./media/backup-azure-arm-restore-vms/cross-zonal-restore.png)
250249

251250
>[!Note]
252-
>Cross-region restore jobs can't be canceled.
251+
>Cross region restore jobs once triggered, can't be canceled.
253252
254253
### Monitoring secondary region restore jobs
255254

0 commit comments

Comments
 (0)