Oracle Apps DBA: Keeping E-Business Suite Alive · Module 5 · Backup and recovery
Backing up the application tier
Lesson 50 of 184 · 3 min
THE HALF EVERYBODY FORGETS. A recovered database with no application tier IS NOT A RECOVERED SYSTEM. Backup plans are written by database people and they cover the database. The application tier is a file system, so it falls to the infrastructure team, or to nobody — and "nobody" is discovered on the day the host is lost. WHAT IS ON THAT FILE SYSTEM IS NOT RECREATABLE FROM MEDIA IN ANY REASONABLE TIME. The application code, yes — but also every patch applied since the installation, the context file describing this instance, custom code in the custom top, generated configuration, and whatever somebody put in a directory five years ago that an interface depends on. REBUILDING IT MEANS A FRESH INSTALL PLUS EVERY PATCH IN ORDER, WHICH IS DAYS RATHER THAN HOURS — assuming you know which patches, which is Lesson 12's fourth failure. Against a recovery objective of four hours,…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.
In this module: Module 5 · Backup and recovery
- 1What you are actually protecting against
- 2The restore you have never testedFree preview
- 3Recovery objectives, in plain terms
- 4Cold backups: when they are still right
- 5RMAN, from nothing
- 6Full, incremental and the strategy behind them
- 7Backing up the application tier
- 8Point-in-time recovery
- 9Restoring to a different host
- 10How long does a restore actually take
- 11Where the backups live
- 12What breaks: five backup failures
- 13Lab briefing · Lose the database and get it back