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
# Customer intent: "As a cloud administrator, I want to utilize Azure Resource Manager templates for configuring Azure Site Recovery, so that I can efficiently manage disaster recovery processes for my Azure virtual machines."
12
13
---
@@ -18,8 +19,8 @@ The following table includes links to Azure Resource Manager templates for using
18
19
| Template | Description |
19
20
|---|---|
20
21
|**Azure to Azure**||
21
-
|[Create a Recovery Services vault](./quickstart-create-vault-template.md)| Create a Recovery Services vault. The vault can be used for Azure Backup and Azure Site Recovery. |
22
-
|[Enable Replication for Azure VMs](https://aka.ms/asr-arm-enable-replication)| Enable replication for Azure VMs using the existing Vault and custom Target Settings.|
23
-
|[Trigger Failover and Reprotect](https://aka.ms/asr-arm-failover-reprotect)| Trigger a Failover and Reprotect operation for a set of Azure VMs. |
24
-
|[Run an End to End DR Flow for Azure VMs](https://aka.ms/asr-arm-e2e-flow)| Start a complete End to End Disaster Recovery Flow (Enable Replication + Failover and Reprotect + Failback and Reprotect) for Azure VMs, also called as 540° flow.|
22
+
|[Create a Recovery Services vault](./quickstart-create-vault-template.md)| Create a Recovery Services vault. Use the vault for Azure Backup and Azure Site Recovery. |
23
+
|[Enable Replication for Azure VMs](https://aka.ms/asr-arm-enable-replication)| Enable replication for Azure VMs by using the existing vault and custom target settings.|
24
+
|[Trigger Failover and Reprotect](https://aka.ms/asr-arm-failover-reprotect)| Trigger a failover and reprotect operation for a set of Azure VMs. |
25
+
|[Run an End to End DR Flow for Azure VMs](https://aka.ms/asr-arm-e2e-flow)| Start a complete end-to-end disaster recovery flow (Enable Replication + Failover and Reprotect + Failback and Reprotect) for Azure VMs, also called as 540° flow.|
Copy file name to clipboardExpand all lines: articles/site-recovery/avs-tutorial-dr-drill-azure.md
+25-24Lines changed: 25 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,12 @@
1
1
---
2
-
title: Run a disaster recovery drill from Azure VMware Solution to Azure by using Azure Site Recovery
2
+
title: Run a disaster recovery drill from Azure VMware Solution to Azure by using Azure Site Recovery
3
3
description: Learn how to run a disaster recovery drill from an Azure VMware Solution private cloud to Azure, by using Azure Site Recovery.
4
4
author: Jeronika-MS
5
5
ms.service: azure-site-recovery
6
6
ms.topic: tutorial
7
-
ms.date: 02/19/2024
7
+
ms.date: 02/11/2026
8
8
ms.author: v-gajeronika
9
+
ms.reviewer: v-gajeronika
9
10
ms.custom: MVC
10
11
11
12
# Customer intent: "As a cloud administrator, I want to run a disaster recovery drill from Azure VMware Solution to Azure, so that I can validate my replication strategy and ensure system resilience without data loss."
@@ -14,9 +15,9 @@ ms.custom: MVC
14
15
15
16
This tutorial describes how to run a disaster recovery drill for an Azure VMware Solution virtual machine (VM) to Azure by using the [Azure Site Recovery](site-recovery-overview.md) service. A drill validates your replication strategy without data loss.
16
17
17
-
This is the fourth tutorial in a series that shows you how to set up disaster recovery to Azure for Azure VMware Solution machines.
18
+
This tutorial is the fourth in a series that shows you how to set up disaster recovery to Azure for Azure VMware Solution machines.
18
19
19
-
In this tutorial, learn how to:
20
+
In this tutorial, you learn how to:
20
21
21
22
> [!div class="checklist"]
22
23
>
@@ -32,16 +33,16 @@ In this tutorial, learn how to:
32
33
Before you begin, complete the previous tutorials. Confirm that you finished these tasks:
33
34
34
35
1.[Set up Azure](avs-tutorial-prepare-azure.md) for disaster recovery to Azure.
35
-
2.[Prepare your Azure VMware Solution deployment](avs-tutorial-prepare-avs.md) to for disaster recovery to Azure.
36
-
3.[Set up disaster recovery](avs-tutorial-replication.md) for Azure VMware Solution VMs.
36
+
1.[Prepare your Azure VMware Solution deployment](avs-tutorial-prepare-avs.md) for disaster recovery to Azure.
37
+
1.[Set up disaster recovery](avs-tutorial-replication.md) for Azure VMware Solution VMs.
37
38
38
39
## Verify VM properties
39
40
40
41
Before you run a test failover, verify the VM properties and make sure that the [VMware vSphere VM](vmware-physical-azure-support-matrix.md#replicated-machines) complies with Azure requirements:
41
42
42
43
1. In **Protected Items**, select **Replicated Items**, and then select the VM.
43
-
2. On the **Replicated item** pane, there's a summary of VM information, health status, and the latest available recovery points. Select **Properties** to view more details.
44
-
3. In **Compute and Network**, you can modify these properties as needed:
44
+
1. On the **Replicated item** pane, you see a summary of VM information, health status, and the latest available recovery points. Select **Properties** to view more details.
45
+
1. In **Compute and Network**, you can modify these properties as needed:
45
46
46
47
* Azure name
47
48
* Resource group
@@ -51,41 +52,41 @@ Before you run a test failover, verify the VM properties and make sure that the
51
52
52
53
You can also view and modify network settings, including:
53
54
54
-
* The network and subnet in which the Azure VM will be located after failover.
55
-
* The IP address that will be assigned to the network and subnet.
55
+
* The network and subnet in which the Azure VM is located after failover.
56
+
* The IP address that you assign to the network and subnet.
56
57
57
-
4. In **Disks**, you can get information about the operating system and data disks on the VM.
58
+
1. In **Disks**, you can get information about the operating system and data disks on the VM.
58
59
59
60
## Create a network for test failover
60
61
61
-
We recommend that for test failover, you choose a network that's isolated from the production recovery site network that's specified in the **Compute and Network** settings for each VM. By default, when you create an Azure virtual network, it's isolated from other networks. The test network should mimic your production network as follows:
62
+
For test failover, choose a network that's isolated from the production recovery site network that's specified in the **Compute and Network** settings for each VM. By default, when you create an Azure virtual network, it's isolated from other networks. The test network should mimic your production network as follows:
62
63
63
-
* The test network should have same number of subnets as the production network. Subnets should have the same names.
64
-
* The test network should use same IP address class and subnet range as the production network.
64
+
* The test network has the same number of subnets as the production network. Subnets have the same names.
65
+
* The test network uses the same IP address class and subnet range as the production network.
65
66
* Update the DNS of the test network with the IP address specified for the DNS VM in **Compute and Network** settings. For details, read [Test failover considerations](site-recovery-active-directory.md#test-failover-considerations).
66
67
67
68
## Run a test failover for a single VM
68
69
69
70
When you run a test failover, the following actions happen:
70
71
71
72
1. A prerequisites check runs to make sure that all of the conditions required for failover are in place.
72
-
2. Failover processes the data, so that an Azure VM can be created. If you select the latest recovery point, a recovery point is created from the data.
73
-
3. An Azure VM is created from the data processed in the previous step.
73
+
1. Failover processes the data, so that an Azure VM can be created. If you select the latest recovery point, a recovery point is created from the data.
74
+
1. An Azure VM is created from the data processed in the previous step.
74
75
75
76
**Run the test failover as follows:**
76
77
77
78
1. In **Settings** > **Replicated Items**, select the VM, and then select **+Test Failover**.
78
-
2. Select the **Latest processed** recovery point for this tutorial. This step fails over the VM to the latest available point in time. The time stamp is shown.
79
+
1. Select the **Latest processed** recovery point for this tutorial. This step fails over the VM to the latest available point in time. The time stamp is shown.
79
80
80
-
With this option, no time is spent processing data, so it provides a low recovery time objective (RTO).
81
-
3. In **Test Failover**, select the target Azure network to which Azure VMs will be connected after failover.
82
-
4. Select **OK** to begin the failover.
81
+
By using this option, you spend no time processing data, so it provides a low recovery time objective (RTO).
82
+
1. In **Test Failover**, select the target Azure network to which Azure VMs connect after failover.
83
+
1. Select **OK** to begin the failover.
83
84
84
-
You can track progress by selecting the VM to open its properties. Or you can select the **Test Failover** job in *vault name* > **Settings** > **Jobs** > **Site Recovery jobs**.
85
-
5. After the failover finishes, the replica Azure VM appears in the Azure portal, under **Virtual Machines**. Check that the VM is the appropriate size, that it's connected to the right network, and that it's running.
85
+
You can track progress by selecting the VM to open its properties. Or you can select the **Test Failover** job in *vault name* > **Settings** > **Jobs** > **Site Recovery jobs*.
86
+
1. After the failover finishes, the replica Azure VM appears in the Azure portal, under **Virtual Machines**. Check that the VM is the appropriate size, that it's connected to the right network, and that it's running.
86
87
87
88
You should now be able to connect to the replicated VM in Azure.
88
-
6. To delete Azure VMs created during the test failover, select **Cleanup test failover** on the VM. In **Notes**, record and save any observations associated with the test failover.
89
+
1. To delete Azure VMs created during the test failover, select **Cleanup test failover** on the VM. In **Notes**, record and save any observations associated with the test failover.
89
90
90
91
In some scenarios, failover requires additional processing that takes around 8 to 10 minutes to complete. You might notice longer test failover times for:
91
92
@@ -95,7 +96,7 @@ In some scenarios, failover requires additional processing that takes around 8 t
95
96
96
97
## Connect after failover
97
98
98
-
If you want to connect to Azure VMs by using Remote Desktop Protocol (RDP) or Secure Shell (SSH) after failover, [prepare to connect](site-recovery-test-failover-to-azure.md#prepare-to-connect-to-azure-vms-after-failover). If you encounter any connectivity problems after failover, follow the [troubleshooting guide](site-recovery-failover-to-azure-troubleshoot.md).
99
+
To connect to Azure VMs by using Remote Desktop Protocol (RDP) or Secure Shell (SSH) after failover, [prepare to connect](site-recovery-test-failover-to-azure.md#prepare-to-connect-to-azure-vms-after-failover). If you encounter any connectivity problems after failover, follow the [troubleshooting guide](site-recovery-failover-to-azure-troubleshoot.md).
Copy file name to clipboardExpand all lines: articles/site-recovery/avs-tutorial-failover.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,20 @@
1
1
---
2
-
title: Fail over Azure VMware Solution VMs to Azure by using Site Recovery
2
+
title: Fail over Azure VMware Solution VMs to Azure by using Site Recovery
3
3
description: Learn how to fail over Azure VMware Solution VMs to Azure in Azure Site Recovery.
4
4
author: Jeronika-MS
5
5
ms.service: azure-site-recovery
6
6
ms.topic: tutorial
7
-
ms.date: 02/19/2024
7
+
ms.date: 02/11/2026
8
8
ms.author: v-gajeronika
9
+
ms.reviewer: v-gajeronika
9
10
ms.custom: MVC, engagement-fy23
10
11
# Customer intent: As a cloud administrator, I want to fail over Azure VMware Solution VMs to Azure using disaster recovery tools, so that I can ensure business continuity and protect against data loss during outages.
11
12
---
12
13
# Fail over Azure VMware Solution VMs
13
14
14
15
This tutorial describes how to fail over Azure VMware Solution virtual machines (VMs) to Azure by using [Azure Site Recovery](site-recovery-overview.md).
15
16
16
-
This is the fifth tutorial in a series that shows you how to set up disaster recovery to Azure for Azure VMware Solution VMs.
17
+
This tutorial is the fifth in a series that shows you how to set up disaster recovery to Azure for Azure VMware Solution VMs.
17
18
18
19
In this tutorial, you learn how to:
19
20
@@ -32,19 +33,19 @@ To better understand the following tasks, you can learn about the [types of fail
32
33
Before you begin, complete the previous tutorials. Confirm that you finished these tasks:
33
34
34
35
1.[Set up Azure](avs-tutorial-prepare-azure.md) for disaster recovery to Azure.
35
-
2.[Prepare your Azure VMware Solution deployment](avs-tutorial-prepare-avs.md) for disaster recovery to Azure.
36
-
3.[Set up disaster recovery](avs-tutorial-replication.md) for Azure VMware Solution VMs.
37
-
4.[Run a disaster recovery drill](avs-tutorial-dr-drill-azure.md) to make sure that everything works as expected.
36
+
1.[Prepare your Azure VMware Solution deployment](avs-tutorial-prepare-avs.md) for disaster recovery to Azure.
37
+
1.[Set up disaster recovery](avs-tutorial-replication.md) for Azure VMware Solution VMs.
38
+
1.[Run a disaster recovery drill](avs-tutorial-dr-drill-azure.md) to make sure that everything works as expected.
38
39
39
40
## Verify VM properties
40
41
41
42
Before you run a failover, check the VM properties to make sure that the VMs meet [Azure requirements](vmware-physical-azure-support-matrix.md#replicated-machines):
42
43
43
44
1. In **Protected Items**, select **Replicated Items**, and then select the VM that you want to verify.
44
45
45
-
2. On the **Replicated item** pane, there's a summary of VM information, health status, and the latest available recovery points. Select **Properties** to view more details.
46
+
1. On the **Replicated item** pane, you see a summary of VM information, health status, and the latest available recovery points. Select **Properties** to view more details.
46
47
47
-
3. In **Compute and Network**, you can modify these properties as needed:
48
+
1. In **Compute and Network**, you can modify these properties as needed:
48
49
49
50
* Azure name
50
51
* Resource group
@@ -54,40 +55,40 @@ Before you run a failover, check the VM properties to make sure that the VMs mee
54
55
55
56
You can also view and modify network settings, including:
56
57
57
-
* The network and subnet in which the Azure VM will be located after failover.
58
-
* The IP address that will be assigned to the network and subnet.
58
+
* The network and subnet in which the Azure VM is located after failover.
59
+
* The IP address that you assign to the network and subnet.
59
60
60
-
4. In **Disks**, you can get information about the operating system and data disks on the VM.
61
+
1. In **Disks**, you can get information about the operating system and data disks on the VM.
61
62
62
63
## Run a failover to Azure
63
64
64
65
1. In **Settings** > **Replicated items**, select the VM that you want to fail over, and then select **Failover**.
65
-
2. In **Failover**, for **Recovery Point**, select a recovery point to fail over to. You can use one of the following options:
66
+
1. In **Failover**, for **Recovery Point**, select a recovery point to fail over to. Use one of the following options:
66
67
***Latest**: This option first processes all the data sent to Site Recovery. It provides the lowest recovery point objective (RPO) because the Azure VM that's created after failover has all the data that was replicated to Site Recovery when the failover was triggered.
67
-
***Latest processed**: This option fails over the VM to the latest recovery point that Site Recovery processed. This option provides a low recovery time objective (RTO) because no time is spent processing unprocessed data.
68
+
***Latest processed**: This option fails over the VM to the latest recovery point that Site Recovery processed. This option provides a low recovery time objective (RTO) because the process doesn't spend any time on unprocessed data.
68
69
***Latest app-consistent**: This option fails over the VM to the latest app-consistent recovery point that Site Recovery processed.
69
70
***Custom**: This option lets you specify a recovery point.
70
71
71
-
3. Select **Shut down machine before beginning failover** to try to shut down source VMs before triggering the failover. Failover continues even if the shutdown fails. You can follow the failover progress on the **Jobs** page.
72
+
1. Select **Shut down machine before beginning failover** to try to shut down source VMs before triggering the failover. Failover continues even if the shutdown fails. You can follow the failover progress on the **Jobs** page.
72
73
73
-
In some scenarios, failover requires additional processing that takes around 8 to 10 minutes to complete. You might notice longer test failover times for:
74
+
In some scenarios, failover requires extra processing that takes around 8 to 10 minutes to complete. You might notice longer test failover times for:
74
75
75
76
* VMware vSphere VMs running a Mobility service version older than 9.8.
76
77
* VMware vSphere Linux VMs.
77
78
* VMware vSphere VMs that don't have the DHCP service enabled.
78
79
* VMware vSphere VMs that don't have the following boot drivers: storvsc, vmbus, storflt, intelide, atapi.
79
80
80
81
> [!WARNING]
81
-
> Don't cancel a failover in progress. Before failover is started, VM replication stops. If you cancel a failover in progress, failover stops, but the VM won't replicate again.
82
+
> Don't cancel a failover in progress. Before failover starts, VM replication stops. If you cancel a failover in progress, failover stops, but the VM won't replicate again.
82
83
83
84
## Connect to a failed-over VM
84
85
85
-
If you want to connect to an Azure VM after failover by using Remote Desktop Protocol (RDP) and Secure Shell (SSH):
86
+
To connect to an Azure VM after failover by using Remote Desktop Protocol (RDP) or Secure Shell (SSH):
86
87
87
88
1. Verify that you meet [the requirements](failover-failback-overview.md#connect-to-azure-after-failover).
88
-
2. After failover, go to the VM and validate by [connecting](/azure/virtual-machines/windows/connect-logon) to it.
89
-
3. Use**Change recovery point** if you want to use a different recovery point after failover. After you commit the failover in the next step, this option will no longer be available.
90
-
4. After validation, select **Commit** to finalize the recovery point of the VM after failover.
89
+
1. After failover, go to the VM and validate by [connecting](/azure/virtual-machines/windows/connect-logon) to it.
90
+
1. Select**Change recovery point** if you want to use a different recovery point after failover. After you commit the failover in the next step, this option isn't available.
91
+
1. After validation, select **Commit** to finalize the recovery point of the VM after failover.
91
92
92
93
After you commit, all the other available recovery points are deleted. This step completes the failover.
0 commit comments