Administering Cloud EPM: The Platform Beneath the Business Processes · Module 12 · Business Continuity and Recovery
Version compatibility
Lesson 138 of 201 · 1 min
A snapshot's compatibility with a target environment depends on their relative versions, and the rules are specific. Why it bites in recovery specifically. Your environment is patched monthly. A snapshot from several months ago may not import into today's environment. THAT SILENTLY SHORTENS YOUR EFFECTIVE RECOVERY WINDOW. YOUR REAL RECOVERY POINT IS BOUNDED BY VERSION COMPATIBILITY, NOT BY HOW LONG YOU KEPT THE FILE. Most people do not know this. They have a retention policy, they believe it is their recovery window, and the two numbers are different. What to do about it: know the rule, check it as part of your recovery plan, and TEST a restore from the oldest snapshot you intend to rely on. And verify the current rules against documentation.
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
