HADR on SQL Server on Azure VMs: Everything you Need to Know
summary
Covers concrete choices and tradeoffs for HA/DR on SQL Server in Azure VMs: use SQL IaaS Agent extension to provision multi-VM Always On AGs (VMs, listener, networking, GMSA, storage pools) end-to-end in minutes; Azure VM storage keeps three copies; backup-to-URL striping limit is 12.8 TB backup limit; SQL Server 2022 adds parallel redo threads so redo scales beyond the old 100‑thread cap; prefer multi‑subnet listeners over load balancers, set availability set/zone at provision, and relax cluster heartbeat thresholds to avoid flapping.
AI-written summary · about
chapters (17)
- 0:00HADR on SQL Server Azure VMs
- 1:10Introduction
- 3:36High availability vs disaster recovery
- 8:18RPO and RTO in HADR
- 13:17HADR strategies in cloud
- 15:06SQL Server HADR options in Azure
- 21:10Backup and restore for DR
- 25:20Failover cluster in Azure
- 27:06Storage for HADR in cloud
- 31:02Availability groups in Azure
- 33:08Redundancy with availability sets and zones
- 36:58Monitoring sync replication
- 37:40Choosing HADR solutions
- 39:46HADR scenarios and recommendations
- 44:45Demo: key settings
- 46:09Simplified AG deployment
- 50:29Post-deployment validation
related talks
49mEverything you always wanted to know about HA/DR for SQL Server on Azure VMs but were afraid to ask
52mMicrosoft SQL Server HA/DR on AWS
54mDesigning Azure Data Disaster Recovery Strategies
50mSQL Server to Azure SQL: Performance and Availability
59mWhat's new on Azure IaaS for SQL Server VMs
46mAzure SQL Database Business Continuity During Disaster
47mDisaster Recovery Strategies for SQL Server
20mFlying High with Highly Available SQL Server Deployments