Administering Cloud EPM: The Platform Beneath the Business Processes · Module 12 · Business Continuity and Recovery
Writing and testing a recovery plan
Lesson 145 of 201 · 2 min
What a recovery plan contains. The scenarios covered, and their recovery point and time objectives. Who declares each scenario, and their deputy. The step sequence per scenario, in enough detail that a competent colleague could follow it. The post-restore checklist. Communication: who is told, when, by whom. And the measured time from the last test. Scenarios worth covering. An artefact deleted in error. An application corrupted. An environment unavailable. A regional event. And the one people forget: SOMEBODY DELETED THE ENVIRONMENT. THE PLAN MUST BE READABLE UNDER PRESSURE BY SOMEBODY WHO DID NOT WRITE IT. Test that specifically. Hand it to a colleague and ask them to follow it. Not read it. Follow it. The testing cadence: at minimum annually, and after any significant change to the estate. Record the measured time each time. A recovery time that is growing tells you something. And where the plan lives. NOT ONLY…
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