Disaster Recovery Strategies for SQL Server
summary
Covers concrete DR choices: standard backup/restore baseline with offsite copies, log shipping since 2000 for delayed recoveries, and when scale exceeds restore windows moving to mirroring / availability groups—recommendation to keep AGs under ~80–100 databases—and 2016’s distributed availability groups for cross-cluster DR. Quantifies tradeoffs: example 600 GB DB restored for small shop vs impractical for 1,000 instances, RTO/RPO tied to log cadence, explores storage replication, containers for fast rebuilds, and chaos engineering (Chaos Monkey) for repeatable testing.
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
47mPerfecting business continuity for Azure SQL DB
46mAzure SQL Database Business Continuity During Disaster
52mHADR on SQL Server on Azure VMs: Everything you Need to Know