Oracle Apps DBA: Keeping E-Business Suite Alive · Module 5 · Backup and recovery
The restore you have never tested
Lesson 45 of 184 · 3 min · Free preview
THE MOST COMMON SERIOUS FINDING IN THIS COURSE. A green backup job proves A FILE WAS WRITTEN; only a restore proves YOU CAN COME BACK. Ask any estate whether it has backups and the answer is yes, with a job that has succeeded every night for a year. Ask when a restore was last performed and the answer is usually silence, or a date somebody is not sure about, or "we restored a table once". THAT GAP IS THE FINDING, AND IT IS THE MOST COMMON ONE IN THIS COURSE. A successful backup job proves the utility ran and wrote something. It does not prove the file is complete, that it is readable, that the archives to go with it exist, that anybody knows the procedure, or that the whole thing fits in the time the business assumes. Every one of those is only established by doing it. AND THE…
This lesson is free
Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.
Watch the full lessonIn 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
