Disaster Recovery Strategies for SQL Server
summary
Claims that every environment needs a tested DR plan and clear RTO/RPOs, then shows how to hit them: baseline backup and restore with offsite copies, log shipping for delayed rollbacks and fast migrations, mirroring/availability groups (up to eight secondaries, advise ≤80 DBs per AG) and distributed AGs, storage replication plus spinning up containers or Azure SQL for failover. Cites Netflix’s 3‑day outage and GitLab’s 2017 live recovery, gives bandwidth and scale limits, and recommends chaos engineering-style DR tests.
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
52mMicrosoft SQL Server HA/DR on AWS
47mPerfecting business continuity for Azure SQL DB
46mAzure SQL Database Business Continuity During Disaster
49mEverything you always wanted to know about HA/DR for SQL Server on Azure VMs but were afraid to ask
52mBusiness Continuity for Hybrid and Cloud Native SQL Server Deployments