Five hybrid cloud backup and disaster recovery mistakes to avoid
summary
Common mistakes: assuming AWS already backs up your data instead of following the shared responsibility model; using separate point tools that create 4 to 16 excess data copies across regions and accounts; treating snapshots as a single reliable copy; designing for backup but not recovery and skipping tests (result: ~34% of orgs fail to failover). Practical fixes shown include cloud-native archive to S3/Glacier, snapshot management, runbook automation, 10x faster recovery via cloud spin or spun appliances, and dedupe that yields 2–5x storage reduction on backups.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:20Customer panelists
- 3:43Assuming doud data is backed up
- 4:48You are responsible for your data and backups
- 6:40Point solutions for the cloud
- 11:14Snapshot management complexity
- 13:24Designing for backup vs. recovery
- 18:05Poor DR testing
- 23:55Redefining data management for the cloud
- 27:00Cohesity cloud solutions
- 32:45Back up your cloud
- 36:48DR with failover and fallback
- 40:49Innovate by using your data
related talks
57mCloud security, data responsibility, and recovery: 10 key strategies
25mData protection design for business continuity
19mPreparing for disaster: going Multi-Region
32mSchroedingers Backup
14mExpect the unexpected: Building resilience with AWS
41mWays to optimize Cloud Disaster Recovery cost
48mRTO & RPO – Best Practices in Hybrid Architectures
44mUnderstanding Cloud Disaster Recovery Cost