MSAMM
Back to course

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

Recovery objectives, in plain terms

Lesson 46 of 184 · 2 min

How much data the business will accept losing, and how long they will accept being down. TWO NUMBERS, agreed with SOMEBODY WHO CAN AGREE THEM. Every technical decision in this module follows from those two numbers, and most estates have never been asked for them. THE FIRST IS HOW MUCH DATA MAY BE LOST. Zero is not an answer available at any price most clients will pay. Fifteen minutes means archiving continuously to somewhere off the host; twenty-four hours means a nightly backup is enough. Those are different architectures and different costs, and the number decides which. THE SECOND IS HOW LONG THE BUSINESS MAY BE DOWN. Four hours means a restore procedure and a host to restore onto. One hour means the restore itself is too slow and something else is needed — a standby, a replicated copy — which is a much larger conversation. ASK IN THE BUSINESS'S…

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