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/site-recovery/tutorial-replicate-vms-edge-zone-to-azure-region.md
+32-23Lines changed: 32 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,35 @@
1
1
---
2
2
title: Set up disaster recovery to another region using PowerShell
3
-
description: This article describes how to replicate, failover, and failback Azure virtual machines (VMs) running an Azure Public MEC to the parent region where Azure Public MEC is an extension.
3
+
description: This article describes how to replicate, failover, and failback Azure virtual machines running in an Azure Extended Zone to its parent region.
4
4
author: ankitaduttaMSFT
5
5
ms.service: azure-site-recovery
6
6
ms.topic: tutorial
7
-
ms.date: 12/14/2022
7
+
ms.date: 12/11/2024
8
8
ms.author: ankitadutta
9
9
10
10
---
11
11
12
-
# Replicate virtual machines running in an Azure Public MEC to Azure region
12
+
# Replicate virtual machines running in an Azure Extended Zone to an Azure region
13
13
14
-
> [!IMPORTANT]
15
-
> The Azure Site Recovery functionality for Public MEC is in preview state.
14
+
This article describes how to replicate, failover, and failback Azure virtual machines (VMs) running on an Azure Extended Zone to its parent Azure region.
15
+
16
+
## Disaster recovery in Azure Extended Zone
17
+
18
+
Site Recovery ensures business continuity by keeping workloads running during outages by continuously replicating the workload from a primary to a secondary location. The ASR functionality for Extended Zones is in preview.
16
19
17
-
This article describes how to replicate, failover, and failback Azure virtual machines (VMs) running on Azure Public MEC to the parent Azure region where Azure Public MEC is an extension.
20
+
Here the primary location is an Azure Extended Zone and secondary location is the parent region to which the Azure Extended Zone is connected.
21
+
22
+
> [!IMPORTANT]
23
+
> - During VM creation, we don't support replication in Extended Zone. It can be enabled in the VM or in the Vault pages once the VM is created.
24
+
> - If using an Extended Zone Storage account as cache storage account, only Block Blob Premium Storage Accounts will be supported.
25
+
> - If using an Extended Zone Storage account as cache storage account, only High-Churn is supported.
18
26
19
-
## Disaster recovery in Azure Public MEC
27
+
If Azure region storage account is used as cache storage account, both normal & high churn are supported.
20
28
21
-
Site Recovery ensures business continuity by keeping workloads running during outages by continuously replicating the workload from primary to secondary location. The ASR functionality for MEC is in preview.
22
29
23
-
Here the primary location is an Azure Public MEC and secondary location is the parent region to which the Azure Public MEC is connected.
30
+
## Set up disaster recovery for VMs in an Azure Extended Zone using PowerShell
24
31
25
-
## Set up disaster recovery for VMs in an Azure Public MEC using PowerShell
32
+
Following are the prerequisites to set up disaster recovery for VMs in an Azure Extended Zone using PowerShell:
26
33
27
34
### Prerequisites
28
35
@@ -32,15 +39,16 @@ Here the primary location is an Azure Public MEC and secondary location is the p
32
39
```
33
40
Get-InstalledModule -Name Az
34
41
```
42
+
- Ensure the Linux distro version and kernel is supported by Azure Site Recovery. For more information, see the [support matrix](./azure-to-azure-support-matrix.md#linux).
35
43
36
-
- Ensure the Linux distro version and kernel is supported by Azure Site Recovery. For more information, see the [support matrix](./azure-to-azure-support-matrix.md#linux).
37
44
38
-
## Replicate Virtual machines running in an Azure Public MEC to Azure region
45
+
## Replicate Virtual machines running in an Azure Extended Zone to an Azure region
46
+
47
+
To replicate VMs running in an Azure Extended Zone to an Azure region, follow these steps:
39
48
40
-
To replicate VMs running in an Azure Public MEC to Azure region, Follow these steps:
41
49
42
50
> [!NOTE]
43
-
> For this example, the primary location is an Azure Public MEC, and the secondary/recovery location is the Azure Public MEC's region.
51
+
> For this example, the primary location is an Azure Extended Zone, and the secondary/recovery location is the Azure Extended Zone's region.
44
52
45
53
1. Sign-in to your Azure account.
46
54
@@ -51,21 +59,20 @@ To replicate VMs running in an Azure Public MEC to Azure region, Follow these st
@@ -235,7 +242,7 @@ To replicate VMs running in an Azure Public MEC to Azure region, Follow these st
235
242
$recoveryNetwork = $recoveryVnet.Id
236
243
```
237
244
238
-
1. Use the following PowerShell cmdlet to replicate an Azure Public MEC Azure virtual machine with managed disks. This step may take around 20 minutes to complete.
245
+
1. Use the following PowerShell cmdlet to replicate an Azure Extended Zone virtual machine with managed disks. This step may take around 20 minutes to complete.
239
246
240
247
1. Get the resource group that the virtual machine must be created in when it's failed
241
248
over.
@@ -380,6 +387,7 @@ To replicate VMs running in an Azure Public MEC to Azure region, Follow these st
380
387
After the test failover job completes successfully, you can connect to the test failed over virtual machine and validate the test failover. Once testing is complete on the test failed over virtual machine, clean up the test copy by starting the cleanup test failover operation. This operation deletes the test copy of the virtual machine that was created by the test failover.
381
388
Verify that all the target settings are right in the test failover VM including location, network setting, no data corruption, and no data is lost in the target VM. Now you can delete the test failover and start the failover.
0 commit comments