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/reliability/reliability-traffic-manager.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,7 +103,7 @@ When you have complex architectures and multiple sets of resources capable of pe
103
103
104
104
In the following example, both the primary region and the secondary region have a full deployment. This deployment includes the cloud services and a synchronized database.
105
105
106
-

106
+

107
107
108
108
*Figure - Automatic failover using Azure Traffic Manager*
109
109
@@ -123,7 +123,7 @@ This scenario is ideal for the use of Azure Traffic Manager that has inbuilt pro
123
123
Create a new Azure Traffic manager profile with the name contoso123 and select the Routing method as Priority.
124
124
If you have a pre-existing resource group that you want to associate with, then you can select an existing resource group, otherwise, create a new resource group.
125
125
126
-

126
+

127
127
128
128
*Figure - Create a Traffic Manager profile*
129
129
@@ -132,7 +132,7 @@ This scenario is ideal for the use of Azure Traffic Manager that has inbuilt pro
132
132
In this step, you create endpoints that point to the production and disaster recovery sites. Here, choose the **Type** as an external endpoint, but if the resource is hosted in Azure, then you can choose **Azure endpoint** as well. If you choose **Azure endpoint**, then select a **Target resource** that is either an **App Service** or a **Public IP** that is allocated by Azure. The priority is set as **1** since it's the primary service for Region 1.
133
133
Similarly, create the disaster recovery endpoint within Traffic Manager as well.
134
134
135
-

135
+

136
136
137
137
*Figure - Create disaster recovery endpoints*
138
138
@@ -144,7 +144,7 @@ This scenario is ideal for the use of Azure Traffic Manager that has inbuilt pro
144
144
If the Retry is set to 1 and TTL is set to 10 secs, then the time for failover 10 + 1 * 10 = 20 seconds. Set the Retry to a value greater than **1** to eliminate chances of failovers due to false positives or any minor network blips.
145
145
146
146
147
-

147
+

148
148
149
149
*Figure - Set up health check and failover configuration*
150
150
@@ -153,4 +153,4 @@ This scenario is ideal for the use of Azure Traffic Manager that has inbuilt pro
153
153
-[Reliability in Azure](/azure/reliability/availability-zones-overview)
154
154
155
155
- Learn more about [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md).
156
-
- Learn more about [Azure DNS](../dns/dns-overview.md).
156
+
- Learn more about [Azure DNS](../dns/dns-overview.md).
0 commit comments