MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 5 · Backup and recovery

What you are actually protecting against

Lesson 44 of 184 · 3 min

Hardware loss, corruption, and SOMEBODY DELETING THE WRONG THING. Three different failures, and ONLY ONE OF THEM IS WHAT MOST BACKUP PLANS ASSUME. HARDWARE LOSS IS THE ONE EVERY PLAN IS BUILT FOR. A disk fails, a host dies, a data centre has an event. It is total, obvious and instant, and the response is a restore of everything — which is what a nightly full backup and a spare host are designed to deliver. CORRUPTION IS DIFFERENT AND MOST PLANS HANDLE IT BADLY. A block goes bad, a file is damaged, and the system keeps running — the damage is discovered when something reads that block, which may be weeks later. So the corruption may be in every backup you hold, faithfully copied each night. Restoring the most recent backup restores the corruption; the useful response is a partial restore of the affected object from a backup old enough

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.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 5 · Backup and recovery

  1. 1What you are actually protecting against
  2. 2The restore you have never testedFree preview
  3. 3Recovery objectives, in plain terms
  4. 4Cold backups: when they are still right
  5. 5RMAN, from nothing
  6. 6Full, incremental and the strategy behind them
  7. 7Backing up the application tier
  8. 8Point-in-time recovery
  9. 9Restoring to a different host
  10. 10How long does a restore actually take
  11. 11Where the backups live
  12. 12What breaks: five backup failures
  13. 13Lab briefing · Lose the database and get it back