I speak to many people who use cloud technologies, especially database tech and how little consideration they give to their MISSION CRITICAL Databases that run in the cloud and its Disaster Recovery process. When I say mission critical, I mean its relative to the company I am talking to, so what might be a tier 1 app for you might not be the case for Bob.

The common mind set I see is “I know I use SQL MI and I have the fact that I am protected across the 3 AVZ – Availability Zones”. Yes, this is great I am sure suffice for many but what if something disastrous happens in the 1 region don’t you want the capability to flick over to an unaffected region and continue business? I would. So please consider DR for SQL MI. I will dive into this more over time, but my operational workflow looks like this:

The high-level workflow

1. Secondary server preparation – this includes a bit of setup:
   1. Same tiers and update settings.
   2. Correct Subnet configuration (no over lapping Ips).
   3. NSG setup.
   4. The right region!
   5. Having all relevant logins.
   6. Setting up all telemetry / auditing reqs.
2. Setting up failover groups.
   1. Leveraging the R/W endpoints.
3. Talking about failover vs forced failover and whether YOU are managing it or automating it via MS.
4. Advanced tips like monitoring replication lag and using sp_wait_for_database_copy_sync which blocks the calling thread until the last committed transaction has been transmitted and hardened in the transaction log of the secondary database.
5. Simulating the failover and testing!

It might seem like a lot but once done think of the benefits:

Minimize Downtime: For businesses that rely heavily on database-driven applications, any downtime can result in significant financial loss and operational disruption

Prevent Data Loss: Data is often one of the most valuable assets for a company. 

Legal Requirements: Many industries are subject to regulations that require robust DR plans. Ensuring databases are protected and recoverable can help organizations comply with these regulations

Cost of Downtime: The cost of downtime can be substantial, including lost revenue, lost productivity, and potential reputational damage. Effective DR strategies help mitigate these costs.

Customer Trust: Reliability is a key factor for maintaining customer trust and satisfaction. Ensuring that databases are always available and recoverable helps maintain a positive customer experience.