Administering Cloud EPM: The Platform Beneath the Business Processes · Module 12 · Business Continuity and Recovery
What we are building
Lesson 134 of 201 · 1 min
An environment being restored from a snapshot, with a stopwatch running. That number is the deliverable. Not the plan. The number. The chain: WHAT EXISTS → WHAT IS CAPTURED → WHERE IT IS STORED → HOW LONG IT IS KEPT → HOW YOU GET IT BACK → HOW LONG THAT TAKES. THE OTHER TWO FLAGSHIPS ARE DECISIONS YOU CANNOT UNDO. THIS ONE IS UNRECOVERABLE. An identity domain designed badly is expensive. A backup strategy designed badly is a business that has lost its planning application in the middle of a budget cycle, with no way back. AND THE FAILURE IS INVISIBLE UNTIL THE DAY IT MATTERS. Nothing tells you your recovery plan does not work. You find out.
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 12 · Business Continuity and Recovery
- 1What we are building
- 2The belief problemFree preview
- 3Three things called backupFree preview
- 4What is in each, and what is not
- 5Version compatibility
- 6Managing daily backups
- 7Archival, retention and retrieval
- 8Data size and its limits
- 9Restoring an environment
- 10Self-service disaster recovery
- 11Capacity scaling
- 12Writing and testing a recovery plan
- 13What breaks
- 14Lab briefing: objectives, a real restore, and the gap
- 15Lab solution walkthrough
