Disaster Recovery Strategies for SQL Server
summary
Starts with backups as the non-negotiable baseline and defines RTO/RPO tradeoffs, shows how log shipping (transaction log backup, copy, restore) saves time for midsize systems while availability groups and distributed AGs scale HA/DR across sites, warns about spec parity and limits (~80–100 DBs per AG), cites real outages (Netflix 2008, GitLab 2017) and recommends scripted restores with dbatools/Powershell, centralized monitoring to avoid alert fatigue, and chaos engineering style DR tests with rollbacks and GitHub runbooks.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:26About me
- 1:47Agenda
- 2:34Hope is not a strategy
- 5:57Top 3 DBA tasks
- 7:15High availability vs Disaster Recovery
- 9:29Recovery Objectives
- 11:58Backup and Restore
- 17:44Mirroring
- 20:36Availability Groups
- 27:36Distributed AGS
- 29:54Monitoring Alerting
- 32:26Enact Dr
- 37:16Dr Testing
- 39:49Other implementations
- 42:26Experiments
related talks
47mDisaster Recovery Strategies for SQL Server- 47mDisaster Recovery Strategies for SQL Server
54mDesigning Azure Data Disaster Recovery Strategies
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
46mAzure SQL Database Business Continuity During Disaster
52mBusiness Continuity for Hybrid and Cloud Native SQL Server Deployments
21mSQL Horror Stories