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-failover.md
+20-19Lines changed: 20 additions & 19 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/12/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. You can 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
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 no time is spent processing 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 doesn'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.
Copy file name to clipboardExpand all lines: articles/site-recovery/avs-tutorial-prepare-avs.md
+15-14Lines changed: 15 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,16 +4,17 @@ description: Learn how to prepare Azure VMware Solution servers for disaster rec
4
4
author: Jeronika-MS
5
5
ms.service: azure-site-recovery
6
6
ms.topic: tutorial
7
-
ms.date: 3/22/2024
7
+
ms.date: 02/12/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 prepare Azure VMware Solution servers for disaster recovery, so that I can ensure my virtual machines can be efficiently replicated and restored in case of a failure."
11
12
---
12
13
# Prepare Azure VMware Solution for disaster recovery to Azure Site Recovery
13
14
14
15
This tutorial describes how to prepare Azure VMware Solution servers for disaster recovery to Azure by using the [Azure Site Recovery](site-recovery-overview.md) service.
15
16
16
-
This is the second tutorial in a series that shows you how to set up disaster recovery to Azure for Azure VMware Solution virtual machines (VMs). In the first tutorial, you [set up the Azure components](avs-tutorial-prepare-azure.md) that you need for Azure VMware Solution disaster recovery.
17
+
This tutorial is the second tutorial in a series that shows you how to set up disaster recovery to Azure for Azure VMware Solution virtual machines (VMs). In the first tutorial, you [set up the Azure components](avs-tutorial-prepare-azure.md) that you need for Azure VMware Solution disaster recovery.
17
18
18
19
In this tutorial, you learn how to:
19
20
@@ -41,17 +42,17 @@ Site Recovery needs access to Azure VMware Solution servers to:
41
42
Create the account as follows:
42
43
43
44
1. To use a dedicated account, create a role at the vCenter server level. Give the role a name such as **Azure_Site_Recovery**.
44
-
2. Assign the role the permissions summarized in the following table.
45
-
3. Create a user on the vCenter server. Assign the role to the user.
45
+
1. Assign the role the permissions summarized in the following table.
46
+
1. Create a user on the vCenter server. Assign the role to the user.
46
47
47
-
Task | Role/Permissions | Details
48
+
|Task | Role/Permissions | Details|
48
49
--- | --- | ---
49
50
VM discovery | At least a read-only user<br/><br/> Data Center object > Propagate to Child Object, role=Read-only | User is assigned at the datacenter level and has access to all the objects in the datacenter.<br/><br/> To restrict access, assign the **No access** role with the **Propagate to child** object to the child objects (vSphere hosts, datastores, VMs, and networks).
50
51
Full replication, failover, failback | Create a role (Azure_Site_Recovery) with the required permissions, and then assign the role to a VMware user or group<br/><br/> Data Center object > Propagate to Child Object, role=Azure_Site_Recovery<br/><br/> Datastore > Allocate space, browse datastore, low-level file operations, remove file, update virtual machine files<br/><br/> Network > Network assign<br/><br/> Resource > Assign VM to resource pool, migrate powered off VM, migrate powered on VM<br/><br/> Scheduled Tasks > Create task, update task<br/><br/> Virtual machine > Configuration<br/><br/> Virtual machine > Interact > answer question, device connection, configure CD media, configure floppy media, power off, power on, VMware tools install<br/><br/> Virtual machine > Inventory > Create, register, unregister<br/><br/> Virtual machine > Provisioning > Allow virtual machine download, allow virtual machine files upload<br/><br/> Virtual machine > Snapshots > Remove snapshots | User is assigned at the datacenter level and has access to all the objects in the datacenter.<br/><br/> To restrict access, assign the **No access** role with the **Propagate to child** object to the child objects (vSphere hosts, datastores, VMs, and networks).
51
52
52
53
## Prepare an account for Mobility service installation
53
54
54
-
The Mobility service must be installed on machines that you want to replicate. Azure Site Recovery can do a push installation of this service when you enable replication for a machine. Or, you can install it manually or by using installation tools.
55
+
You must install the Mobility service on machines that you want to replicate. Azure Site Recovery can install this service through push installation when you enable replication for a machine. Or, you can install it manually or by using installation tools.
55
56
56
57
In this tutorial, you install the Mobility service by using the push installation. For this push installation, you need to prepare an account that Azure Site Recovery can use to access the VM. You specify this account when you set up disaster recovery in the Azure console.
57
58
@@ -71,8 +72,8 @@ Make sure that the VMware vCenter server and VMs comply with requirements:
71
72
* For Linux VMs, check [file system and storage requirements](vmware-physical-azure-support-matrix.md#linux-file-systemsguest-storage).
72
73
* Check [network](vmware-physical-azure-support-matrix.md#network) and [storage](vmware-physical-azure-support-matrix.md#storage) support.
73
74
* Check what's supported for [Azure networking](vmware-physical-azure-support-matrix.md#azure-vm-network-after-failover), [storage](vmware-physical-azure-support-matrix.md#azure-storage), and [compute](vmware-physical-azure-support-matrix.md#azure-compute) after failover.
74
-
* Verify that the Azure VMware Solution VMs that you'll replicate to Azure comply with [Azure VM requirements](vmware-physical-azure-support-matrix.md#azure-vm-requirements).
75
-
* For Linux VMs, ensure that no two devices or mount points have the same names. These names must be unique and aren't case-sensitive. For example, you can't name two devices for the same VM as *device1* and *Device1*.
75
+
* Verify that the Azure VMware Solution VMs that you replicate to Azure comply with [Azure VM requirements](vmware-physical-azure-support-matrix.md#azure-vm-requirements).
76
+
* For Linux VMs, ensure that no two devices or mount points have the same names. These names must be unique and aren't case-insensitive. For example, you can't name two devices for the same VM as *device1* and *Device1*.
76
77
77
78
78
79
## Prepare to connect to Azure VMs after failover
@@ -85,13 +86,13 @@ After failover, you might want to connect to the Azure VMs from your Azure VMwar
85
86
Before failover, enable Remote Desktop Protocol (RDP) on the Azure VMware Solution VM:
86
87
87
88
* For internet access:
88
-
*Make sure that TCP and UDP rules are added for the **Public** profile.
89
-
*Make sure that RDP is allowed in **Windows Firewall** > **Allowed Apps** for all profiles.
89
+
*Add TCP and UDP rules for the **Public** profile.
90
+
*Allow RDP in **Windows Firewall** > **Allowed Apps** for all profiles.
90
91
* For site-to-site VPN access:
91
-
*Make sure that RDP is allowed in **Windows Firewall** > **Allowed apps and features** for **Domain and Private** networks.
92
-
*Check that the operating system's SAN policy is set to **OnlineAll**. [Learn more](https://support.microsoft.com/kb/3031135).
92
+
*Allow RDP in **Windows Firewall** > **Allowed apps and features** for **Domain and Private** networks.
93
+
*Set the operating system's SAN policy to **OnlineAll**. [Learn more](https://support.microsoft.com/kb/3031135).
93
94
94
-
There should be no Windows updates pending on the VM when you trigger a failover. If there are, you won't be able to sign in to the virtual machine until the update finishes.
95
+
Don't leave any Windows updates pending on the VM when you trigger a failover. If you leave updates pending, you can't sign in to the virtual machine until the update finishes.
95
96
96
97
After failover, check **Boot diagnostics** to view a screenshot of the VM. If you can't connect, check that the VM is running and review [troubleshooting tips](https://social.technet.microsoft.com/wiki/contents/articles/31666.troubleshooting-remote-desktop-connection-after-failover-using-asr.aspx).
97
98
@@ -110,7 +111,7 @@ You can check **Boot diagnostics** to view a screenshot of the VM.
110
111
111
112
## Failback requirements
112
113
113
-
If you plan to fail back to your Azure VMware Solution cloud, there are several [prerequisites for failback](avs-tutorial-reprotect.md#before-you-begin). You can prepare these now, but you don't need to. You can prepare after you fail over to Azure.
114
+
If you plan to fail back to your Azure VMware Solution cloud, there are several [prerequisites for failback](avs-tutorial-reprotect.md#before-you-begin). You can prepare these prerequisites now, but you don't need to. You can prepare them after you fail over to Azure.
0 commit comments