Skip to content

Commit 53a0a8b

Browse files
author
Ankita Dutta
committed
acrofix
1 parent da84abc commit 53a0a8b

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/site-recovery/azure-vm-disaster-recovery-with-expressroute.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Integrate Azure ExpressRoute Azure VM disaster recovery with Azure Site Recovery
2+
title: Integrate Azure ExpressRoute Azure virtual machine disaster recovery with Azure Site Recovery
33
description: Describes how to set up disaster recovery for Azure virtual machines using Azure Site Recovery and Azure ExpressRoute
44
author: ankitaduttaMSFT
55
ms.service: azure-site-recovery
@@ -42,7 +42,7 @@ Before you begin, make sure you understand the following concepts:
4242
For best practice, and to ensure efficient Recovery Time Objectives (RTOs) for disaster recovery, we recommend you do the following when you set up Site Recovery to integrate with ExpressRoute:
4343

4444
- Provision networking components before failover to a secondary region:
45-
- When you enable replication for Azure virtual machines, Site Recovery can automatically deploy networking resources like networks, subnets, and gateways in the target Azure region, using the source network settings.
45+
- When you enable replication for Azure virtual machines, Site Recovery can automatically deploy networking resources using the source network settings. For example, networks, subnets, and gateways in the target Azure region.
4646
- Site Recovery can't automatically set up networking resources such as VNet gateways.
4747
- We recommend you provision these extra networking resources before failover. A small downtime is associated with this deployment, and it can impact the overall recovery time, if you didn't account for it during deployment planning.
4848
- Run regular disaster recovery drills:
@@ -74,7 +74,7 @@ If you want to set up replication for Azure virtual machines in a primary site,
7474

7575
## Replication example
7676

77-
Typically enterprise deployments have workloads split across multiple Azure VNets, with a central connectivity hub for external connectivity to the internet and to on-premises sites. A hub and spoke topology is typically used together with ExpressRoute.
77+
In typical enterprise deployments, workloads are distributed across multiple Azure VNets with a central hub for internet and on-premises connectivity. This setup often uses a hub-and-spoke topology with ExpressRoute.
7878

7979
![On-premises-to-Azure with ExpressRoute before failover](./media/azure-vm-disaster-recovery-with-expressroute/site-recovery-with-expressroute-before-failover.png)
8080

articles/site-recovery/concepts-expressroute-with-site-recovery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ Azure Site Recovery enables disaster recovery of [Azure virtual machines](azure-
5151

5252
For Azure VM disaster recovery, by default, ExpressRoute is not required for replication. After virtual machines fail over to the target Azure region, you can access them using [private peering](../expressroute/expressroute-circuit-peerings.md#privatepeering). Note that data transfer prices apply irrespective of the mode of data replication across Azure regions.
5353

54-
If you are already using ExpressRoute to connect from your on-premises datacenter to the Azure VMs on the source region, you can plan for re-establishing ExpressRoute connectivity at the failover target region. You can use the same ExpressRoute circuit to connect to the target region through a new virtual network connection or utilize a separate ExpressRoute circuit and connection for disaster recovery. The different possible scenarios are described [here](azure-vm-disaster-recovery-with-expressroute.md#fail-over-azure-vms-when-using-expressroute).
54+
If you are already using ExpressRoute to connect from your on-premises datacenter to the Azure VMs on the source region, you can plan for re-establishing ExpressRoute connectivity at the failover target region. You can use the same ExpressRoute circuit to connect to the target region through a new virtual network connection or utilize a separate ExpressRoute circuit and connection for disaster recovery. The different possible scenarios are described [here](azure-vm-disaster-recovery-with-expressroute.md#fail-over-azure-virtual-machines-when-using-expressroute).
5555

5656
You can replicate Azure virtual machines to any Azure region within the same geographic cluster as detailed [here](../site-recovery/azure-to-azure-support-matrix.md#region-support). If the chosen target Azure region is not within the same geopolitical region as the source, you might need to enable ExpressRoute Premium. For more details, check [ExpressRoute locations](../expressroute/expressroute-locations.md) and [ExpressRoute pricing](https://azure.microsoft.com/pricing/details/expressroute/).
5757

0 commit comments

Comments
 (0)