Azure SQL Database Business Continuity During Disaster
summary
Real procedures and numbers: automated backups give point-in-time: 7→35 days by SKU, long‑term retention can store backups up to 10 years, and built‑in HADR includes active geo‑replication: up to 4 async secondaries plus auto‑failover groups with read/write and read‑only endpoints. Demos use Azure Data Studio notebooks and PowerShell, scripts are on GitHub, and live failovers show the portal behavior; watch if needing precise RPO/RTO tradeoffs after a quoted 16‑hour outage example.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:43Estimated Recovery Time
- 9:50Active Geo Replication
- 10:26Failover Groups
- 11:38Automated Backup
- 13:08Point in Time Backup Retention
- 14:16How Does Automatic Backup Impact the Cost if You Have a Large Database Do You Need Separate Storage for Backup
- 17:27Can You Restore on-Prem
- 20:15Zone Redundancy
- 26:45Asynchronous Replication
- 30:07The Demo
- 32:25Backup Retention
- 39:44Failover Group
related talks
01h 01mAzure SQL Database-Business Continuity During Disaster
47mPerfecting business continuity for Azure SQL DB
54mDesigning Azure Data Disaster Recovery Strategies
46mBusiness continuity of on-prem SQL Servers using Azure services through Arc
50mSQL Server to Azure SQL: Performance and Availability
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
47mDisaster Recovery Strategies for SQL Server