The belief problem

A BACKUP YOU HAVE NEVER RESTORED IS NOT A BACKUP. IT IS A BELIEF. Most organizations running Cloud EPM believe they have a backup. Far fewer have restored one. The gap between those two states is where the risk lives. And what makes it worse here than elsewhere. Daily backups happen automatically, which produces a comfortable feeling that the problem is solved. It is not. Automatic capture is ONE of six things a recovery capability needs. Something is captured. It contains what you need. It is stored somewhere that survives the failure. It is retained long enough. You know how to restore it. And you know how long that takes. Five questions to ask any client, and they usually cannot answer past the second. How far back can you go? What is NOT in the backup? Where is it stored? How long would a restore take? When did you last…

In this module: Module 12 · Business Continuity and Recovery

1. 1What we are building
2. 2The belief problemFree preview
3. 3Three things called backupFree preview
4. 4What is in each, and what is not
5. 5Version compatibility
6. 6Managing daily backups
7. 7Archival, retention and retrieval
8. 8Data size and its limits
9. 9Restoring an environment
10. 10Self-service disaster recovery
11. 11Capacity scaling
12. 12Writing and testing a recovery plan
13. 13What breaks
14. 14Lab briefing: objectives, a real restore, and the gap
15. 15Lab solution walkthrough