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/concepts-public-ip-address-with-site-recovery.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,9 @@
1
1
---
2
2
title: Assign public IP addresses after failover with Azure Site Recovery
3
3
description: Describes how to set up public IP addresses with Azure Site Recovery and Azure Traffic Manager for disaster recovery and migration
4
-
services: site-recovery
5
4
author: ankitaduttaMSFT
6
-
manager: rochakm
7
5
ms.service: azure-site-recovery
8
-
ms.topic: conceptual
6
+
ms.topic: overview
9
7
ms.date: 10/31/2023
10
8
ms.author: ankitadutta
11
9
@@ -14,7 +12,7 @@ ms.author: ankitadutta
14
12
15
13
Public IP addresses serve two purposes in Azure. First, they allow inbound communication from Internet resources to Azure resources. Secondly, they enable Azure resources to communicate outbound to the Internet and public-facing Azure services that have an IP address assigned to the resource.
16
14
17
-
- Allow inbound communication from the Internet to the resource, such as Azure Virtual Machines (VM), Azure Application Gateways, Azure Load Balancers, Azure VPN Gateways, and others. You can still communicate with some resources, such as VMs, from the Internet, if a VM doesn't have a public IP address assigned to it, as long as the VM is part of a load balancer back-end pool, and the load balancer is assigned a public IP address.
15
+
- Allow inbound communication from the Internet to the resource, such as Azure Virtual Machines (VM), Azure Application Gateways, Azure Load Balancers, Azure VPN Gateways, and others. You can still communicate with some resources, such as virtual machines, from the Internet, if a virtual machines doesn't have a public IP address assigned to it, as long as the virtual machines is part of a load balancer back-end pool, and the load balancer is assigned a public IP address.
18
16
- Outbound connectivity to the Internet using a predictable IP address. For example, a virtual machine can communicate outbound to the Internet without a public IP address assigned to it, but its address is network address translated by Azure to an unpredictable public address, by default. Assigning a public IP address to a resource enables you to know which IP address is used for the outbound connection. Though predictable, the address can change, depending on the assignment method chosen. For more information, see [Create a public IP address](../virtual-network/ip-services/virtual-network-public-ip-address.md#create-a-public-ip-address). To learn more about outbound connections from Azure resources, see [Understand outbound connections](../load-balancer/load-balancer-outbound-connections.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
19
17
20
18
In Azure Resource Manager, a Public IP address is a resource that has its own properties. Some of the resources you can associate a public IP address resource with are:
@@ -33,7 +31,7 @@ Public IP address of the production application **cannot be retained on failover
33
31
The setup is as follows:
34
32
35
33
- Create a [recovery plan](../site-recovery/site-recovery-create-recovery-plans.md#create-a-recovery-plan) and group your workloads as necessary into the plan.
36
-
- Customize the plan by adding a step to attach a public IP address using [Azure Automation runbooks](../site-recovery/site-recovery-runbook-automation.md#customize-the-recovery-plan) scripts to the failed over VM.
34
+
- Customize the plan by adding a step to attach a public IP address using [Azure Automation runbooks](../site-recovery/site-recovery-runbook-automation.md#customize-the-recovery-plan) scripts to the failed over virtual machines.
37
35
38
36
39
37
## Public endpoint switching with DNS level Routing
Copy file name to clipboardExpand all lines: articles/site-recovery/concepts-types-of-failback.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
-
title: Failback during disaster recovery with Azure Site Recovery | Microsoft Docs
2
+
title: Failback during disaster recovery with Azure Site Recovery
3
3
description: This article provides an overview of various types of failback and caveats to be considered while failing back to on-premises during disaster recovery with the Azure Site Recovery service.
4
4
ms.service: azure-site-recovery
5
-
ms.topic: conceptual
5
+
ms.topic: overview
6
6
ms.date: 08/07/2019
7
7
ms.author: ankitadutta
8
8
author: ankitaduttaMSFT
9
9
10
10
---
11
11
12
-
# Failback of VMware VMs after disaster recovery to Azure
12
+
# Failback of VMware virtual machines after disaster recovery to Azure
13
13
14
14
After you have failed over to Azure as part of your disaster recovery process, you can fail back to your on-premises site. There are two different types of failback that are possible with Azure Site Recovery:
0 commit comments