Administering Cloud EPM: The Platform Beneath the Business Processes · Module 12 · Business Continuity and Recovery
What is in each, and what is not
Lesson 137 of 201 · 1 min
IS THE THING I NEED ACTUALLY IN THERE? That is the question that matters in a crisis. What a snapshot carries: application artefacts, definitions, configuration. Four things it does not, and this is the important half. Identity. Users live in the identity domain (Module 3) not in the environment. A restored environment has an application and no users, unless the domain is intact. Role assignments, which are a separate operation (Module 6). Some environment-level configuration. And anything OUTSIDE the environment — the integrations, the automation, the credential files. RESTORING AN ENVIRONMENT IS ONE STEP OF A RECOVERY, NOT THE WHOLE THING. The full sequence includes identity, roles, integrations, automation and client connections. Build that list now, while nothing is on fire. One note: Narrative Reporting's restore path has its own considerations. Know them if that business process is in your estate. And the habit: after any restore, check what is…
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