Business Continuity for Hybrid and Cloud Native SQL Server Deployments
summary
Defines recovery targets like restore timing (RTO) and data currency (RPO), insists native backups are mandatory and tested, and warns a multi‑TB seed to the cloud can take days to weeks to copy and restore. Compares protection layers: FCI for instance objects, Availability Groups (including contained AGs in SQL Server 2022 Enterprise) and log shipping for DB level, replication for reporting, and PaaS vs IaaS tradeoffs. Covers Azure concepts—availability sets/zones, ILB vs distributed network name, VM IOPS/network limits, and using cloud witness for quorum.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:40Allan's Basic Definitions
- 4:48Recovery Goals
- 15:19SQL Server Availability Options
- 45:29Distributed Network Name
related talks
46mAzure SQL Database Business Continuity During Disaster
25mData protection design for business continuity
49mEverything you always wanted to know about HA/DR for SQL Server on Azure VMs but were afraid to ask
48mRTO & RPO – Best Practices in Hybrid Architectures
50mAzure SQL Managed Instance Roadmap
47mNext Level Availability on SQL Server 2022
23mState in a stateless world: data serving in the cloud
57mCloud security, data responsibility, and recovery: 10 key strategies