Disaster recovery strategy for application gateway/load balancer

Question

Hi,

I have many application gateways, Internal load balancers where lots of endpoints are configured. In the event of region level disaster, I want to make these resources deployed in target region with preserving configurations like listener names, rules, backend settings, probes etc.

I assume frontend public IPs won't be preserved (as it is limited to specific region) hence a new public IP will have to be created and attached and accordingly DNS will have to be updated.

I have explored 2 options here:

1. Export ARM templates, but during disaster scenarios, expected recovery time objectives would be so low that I can't be adjusting each parameter for each resource group based deployment
2. Exploration of global solutions like Front door/Traffic manager

I am more inclined towards automated deployment of resources with preserving configuration with minimum possible time for business.

looking for some guidance and ideas here..

Answer 1

@WinTechie

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you are looking for Disaster recovery scenarios for Application Gateway.

I would suggest the best and recommended way to achieve DR is by using a Traffic Manager

For more detailed information on different DR scenarios, refer here

While you can export the ARM template and redeploy it, as you mentioned, it presents a challenge that you should maintain the latest ARM templates of the affected Application gateways.

Also, this would require you to match the backend configurations

P.S : Deploy Zone-Redundant App gateways to overcome Zonal failures.

Additional documents that may come handy:

Traffic Manager

Disaster recovery using Azure DNS and Traffic Manager

Thanks,

Kapil

---

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.