Designing Azure Data Disaster Recovery Strategies
summary
Explains concrete DR choices: PaaS (Azure SQL DB/Managed Instance) gives automatic backups (weekly full, two dailies, log backups ~5–7 minutes) with 7‑day default retention (configurable to 10 years); IaaS (SQL on VM) lets you control backups or use Azure Backup/Azure Site Recovery block‑replication. Compares geo-replication (multiple readable async replicas, manual failover) vs failover groups (server‑level listener, automatic failover, one‑hour minimum grace). Recommends testing; demo creates East→West replica and failover group that successfully seeds and reads the secondary.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:07Denny Cherry & Associates
- 1:24Our Journey Today...
- 2:37BACKHOE PHENOMENON
- 4:11Objectives
- 6:09What Does That Mean?
- 7:02Geographies
- 9:24Availability Zones
- 12:25United States Sibling Regions
- 14:22Physics is a key element in DR
- 18:40Storage Terminology
- 24:33Matrix of Options Strategy
- 27:41Backup - Storage Tiers
- 30:30Azure Site Recovery/Azure Backup
- 33:25Platform As a Service
- 36:40Availability Groups
- 39:21Failover Groups
- 41:01Geo-Replication vs FGS
- 52:01Final Thoughts
- 53:09Further reading...
related talks
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
47mDisaster Recovery Strategies for SQL Server
01h 01mAzure SQL Database-Business Continuity During Disaster- 47mDisaster Recovery Strategies for SQL Server
47mPerfecting business continuity for Azure SQL DB- 47mDisaster Recovery Strategies for SQL Server
28mHA and DR at a glance with Azure Database for PostgreSQL