Azure SQL Database-Business Continuity During Disaster
summary
Five concrete continuity options with demos and scripts: automated backups with point-in-time restore (default 7 days, configurable to 35; long‑term retention to 10 years), built‑in single‑region HA, zone‑redundant replicas (SLA 99.99 → 99.995), active geo‑replication (async, up to 4 secondaries) and auto‑failover group (listener endpoint, grouped DB failover). Live demos use Azure Data Studio notebooks, OStress load, and PowerShell from a GitHub repo; measured failover times ~47s for general purpose and under 10s for business critical.
AI-written summary · about
chapters (21)
- 0:00Start
- 3:08Rto and Rpo
- 4:33Estimated Recovery Time
- 13:08Automated Backup
- 14:52Differential Backup and Transaction Log Backup
- 15:16Point in Time Backup Retention
- 15:36Long-Term Retention
- 17:22Long Term Retention Backup
- 17:55Point in Time Restore to Your Existing Azure Sql Server
- 19:39Can I Restore a Azure Sql Database on on-Premises Sql Server Natively
- 21:38Connecting to a Azure Sql Database
- 25:27Zone Redundancy
- 29:43Region Redundancy
- 30:12Asynchronous Replication
- 32:05Why Microsoft Needed the Auto Failover Group
- 32:42Auto Failover Groups
- 34:18Auto Failover
- 37:52Demo
- 53:07Failover Groups
- 53:54How Do I Convince My Business Owners
- 56:17Failover Group
related talks
46mAzure SQL Database Business Continuity During Disaster
47mPerfecting business continuity for Azure SQL DB
54mDesigning Azure Data Disaster Recovery Strategies
43mLearn Azure SQL Database through Demos
50mSQL Server to Azure SQL: Performance and Availability
46mBusiness continuity of on-prem SQL Servers using Azure services through Arc
28mHA and DR at a glance with Azure Database for PostgreSQL
49mEverything you always wanted to know about HA/DR for SQL Server on Azure VMs but were afraid to ask