Skip to content

Commit 673c767

Browse files
Merge pull request #272194 from raghavendermareddy/patch-124
Update use-s2s-vpn-as-backup-for-expressroute-privatepeering.md
2 parents b4f82a9 + 74a126e commit 673c767

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/expressroute/use-s2s-vpn-as-backup-for-expressroute-privatepeering.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,18 @@ author: duongau
66
ms.service: expressroute
77
ms.custom: devx-track-azurepowershell
88
ms.topic: how-to
9-
ms.date: 12/28/2023
9+
ms.date: 04/15/2024
1010
ms.author: duau
1111
---
1212

1313
# Using S2S VPN as a backup for ExpressRoute private peering
1414

1515
In the article titled [Designing for disaster recovery with ExpressRoute private peering][DR-PP], we discussed the need for a backup connectivity solution when using ExpressRoute private peering. We also discussed how to use geo-redundant ExpressRoute circuits for high-availability. In this article, we explain how to use and maintain a site-to-site (S2S) VPN as a backup for ExpressRoute private peering.
1616

17+
> [!NOTE]
18+
> Using site-to-site VPN as a backup solution for ExpressRoute connectivity is not recommended when dealing with latency-sensitive, mission-critical, or bandwidth-intensive workloads. In such cases, it's advisable to design for disaster recovery with ExpressRoute multi-site resiliency to ensure maximum availability.
19+
>
20+
1721
Unlike geo-redundant ExpressRoute circuits, you can only use ExpressRoute and VPN disaster recovery combination in an active-passive setup. A major challenge of using any backup network connectivity in the passive mode is that the passive connection would often fail alongside the primary connection. The common reason for the failures of the passive connection is lack of active maintenance. Therefore, in this article, the focus is on how to verify and actively maintain a S2S VPN connectivity that is backing up an ExpressRoute private peering.
1822

1923
> [!NOTE]

0 commit comments

Comments
 (0)