Oracle Apps DBA: Keeping E-Business Suite Alive · Module 5 · Backup and recovery
How long does a restore actually take
Lesson 53 of 184 · 2 min
MEASURED, not estimated. The number the business needs, and THE ONE NOBODY HAS UNTIL AN OUTAGE PRODUCES IT. "About two hours" is the answer every estate gives, and it is a guess wearing the clothes of a fact. The business is making decisions with it — whether to have a standby, what to promise customers, how much downtime insurance to hold — and nobody has ever measured it. THE MEASURED NUMBER IS RELIABLY LARGER THAN THE GUESS, AND THE REASON IS THAT THE GUESS COUNTS ONE STEP. People estimate the time to copy the files back. A real restore is: realising what has happened, deciding to restore, finding the procedure, locating the backup, retrieving it from wherever it lives, restoring, applying archives, opening, starting the application tier, and checking that the system actually works. SEVERAL OF THOSE ARE LONGER THAN THE COPY. Retrieving from off-site storage can be hours before…
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