MSAMM
Back to course

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

What breaks: five backup failures

Lesson 55 of 184 · 2 min

A job that SUCCEEDED FOR MONTHS writing nothing usable, a retention policy that DELETED WHAT WAS NEEDED, an archive gap, a restore to a host with the wrong patch level, and A BACKUP NOBODY COULD DECRYPT. THE JOB THAT SUCCEEDED FOR MONTHS is Lesson 2 in its purest form. A script backing up a list of files written two years ago, missing every datafile added since. A backup to a destination that silently discarded what it received. Green every night, unusable, and only a restore would ever have said so. THE RETENTION POLICY THAT DELETED WHAT WAS NEEDED IS THE ONE THAT LOOKS LIKE GOOD HOUSEKEEPING. Backups older than fourteen days are removed — sensible, and it means a corruption discovered after fifteen days has no clean backup to go back to. Lesson 1's second failure meeting a policy written for the first one, and the retention period is a…

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.

See the course and enrol9 free lessons

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