Azure Traffic Manager
An Azure service that is used to route incoming network traffic for high performance and availability.
97 questions
Regional multi-service failover with Azure Traffic Manager
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 3%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPA%3C/text%3E%3C/svg%3E)
pramod ANCHUPARAYIL
6
Reputation points
We have a several services (API, Web APP, Config) that make up an application, deployed in multiple regions with failover in an Active/Passive (hot standby) fashion. Each of those services can be consumed independently and share underlying dataset. Any service failure in one region should initiate a failover to the secondary region for all those services.
How can we set up Azure Traffic manager profiles so an outage in any one of those services will fail over all services together the secondary region. Sort of grouping services that must failover together within a region. I don't see a way to accomplish this using nested profiles.
We have a workaround by creating traffic manager profiles for each service with multi-region endpoints, then set up an Azure function to respond to endpoint down alerts from any profiles to flip each profile/service to the secondary region.
Want to know if there is an easier way to do it, without having to route all traffic thru Azure.
Thanks
P
{count} votes
-
GitaraniSharma-MSFT 38,931 Reputation points Microsoft Employee2022-02-14T05:55:32.86+00:00 Hello @pramod ANCHUPARAYIL ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
Most of the HA and DR scenarios with Azure Traffic Manager are described in the below articles:
https://learn.microsoft.com/en-us/azure/networking/disaster-recovery-dns-traffic-manager
https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/n-tier/multi-region-sql-server
https://learn.microsoft.com/en-us/azure/architecture/high-availability/reference-architecture-traffic-manager-application-gateway
https://learn.microsoft.com/en-us/azure/architecture/example-scenario/infrastructure/multi-tier-app-disaster-recoveryCould you check if the Multi-tier web application built for HA/DR scenario meets your requirement?
Regards,
Gita -
pramod ANCHUPARAYIL 6 Reputation points
2022-02-14T15:13:35.54+00:00 The Multi-tier web architecture does not address my requirement. I have a Web App tier, Data Services tier and an API tier. All of which are accessible by customers independantly, any outage in any of the tier should trigger a failover for all tiers to ensure a consistent customer experience.
-
GitaraniSharma-MSFT 38,931 Reputation points Microsoft Employee
2022-02-15T06:12:54.357+00:00 Thank you for the update, @pramod ANCHUPARAYIL . Let me check internally regarding your scenario and also discuss this with the product group team for more information. Will keep you updated.
-
GitaraniSharma-MSFT 38,931 Reputation points Microsoft Employee
2022-02-16T10:41:40.89+00:00 Hello @pramod ANCHUPARAYIL ,
Below are the inputs from the Product group team:
The key here is designing your health probe endpoint response. In the most simple sense, the health probe endpoint is a web endpoint that when queried and healthy, will reply ‘200 OK’. In your case, you need to take advantage of the error/response mechanism. Your health probe endpoint should reflect the health of all components of your service. In this way, if any of your three tiers is compromised in any region (however you measure that) can be reflected in the http/https error code returned by a query from the ATM health probe service. This will have to be something you develop. It’s essentially another component in your service – one that specifically attests to multi-tier region health.
Looks like there is no in-built way to achieve your scenario. If you have any specific questions, please let me know and I can further discuss them with the Product group team to provide better clarity.
Regards,
Gita -
GitaraniSharma-MSFT 38,931 Reputation points Microsoft Employee
2022-02-21T12:28:09.43+00:00 Hello @pramod ANCHUPARAYIL ,
I'm following up on my previous comment. Please let us know if you have any specific questions and I can further discuss them with the Product group team to provide better clarity on this scenario.
Regards,
Gita -
pramod ANCHUPARAYIL 6 Reputation points
2022-02-22T22:58:50.56+00:00 Hi
We ended up doing like what I had described in the workaround. Seems to be working alright.
Thanks for your help, perhaps this could be a feature request back to the product team.
Thanks
P -
GitaraniSharma-MSFT 38,931 Reputation points Microsoft Employee
2022-02-23T10:27:53.403+00:00 Thank you for the update, @pramod ANCHUPARAYIL .
I will share the feedback to the product team internally and I would also request you to share your feedback in the below forum requesting this feature. All the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.
https://feedback.azure.com/d365community/forum/8ae9bf04-8326-ec11-b6e6-000d3a4f0789Regards,
Gita
Sign in to comment