Administering Cloud EPM: The Platform Beneath the Business Processes · Module 12 · Business Continuity and Recovery
What breaks
Lesson 146 of 201 · 2 min
Sequence first. "We need to restore and something is wrong." Check in this order. One. Do we have a snapshot from the point we need? Two. Is it version-compatible with the target? Three. Is it complete and readable? Four. Is the identity domain intact — do the users still exist? Five. Have we worked the post-restore checklist, or just imported? Six. Are integrations and automation pointing at the right place? Then nine cases. One. "We have never tested a restore." The belief problem. The whole module. Two. "The snapshot will not import — version." Effective recovery window shorter than retention. Lesson 5. Three. "We restored and nobody has access." Identity and roles are not in the snapshot. Expected — and repeatedly a surprise. Four. "We needed something from five weeks ago and retention was four." The retention decision was never made deliberately. Five. "The archived backup took hours to retrieve."…
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