backrecovery - CERN/IT/DB Oracle backup and recovery...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
CERN/IT/DB Oracle backup and recovery  strategy Catherine Delamare /IT DB 
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CERN/IT/DB AGENDA Why plan backups? Overview of backups Backup implementation in IT/DB Export/Import Recovery
Background image of page 2
CERN/IT/DB Why plan backups?
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CERN/IT/DB Why plan backups? Hardware never fails Oracle never makes a mistake Users never make mistakes Programmers never make mistakes Physicists never make mistakes Database administrators (DBAs) never  make mistakes
Background image of page 4
CERN/IT/DB Why plan backups?  The only insurance you have against  failures causing loss of data: Human errors Hardware failures Power failures Software errors  DBA’s job security!
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CERN/IT/DB Why plan backups?
Background image of page 6
CERN/IT/DB Overview of backups Physical  backups protect against global failure Cold backups : database needs to be stopped Hot backups : database keeps on running Logical   backups (or “exports”) protect against deletion of (a) table(s) can be run by the user himself
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CERN/IT/DB ARCHIVELOG Mode or not?  (1/3) Definition All changes are kept in “ archived logs The more activity, the more archived logs Central db: 600 logs per week (30M each=18G  transactions volume per week) Advantages of ARCHIVELOG mode Complete recovery up to the last committed  transaction before the failure (“point-in-time”  recovery) Mandatory for mission-critical applications Pre-requisite to run hot backups
Background image of page 8
CERN/IT/DB ARCHIVELOG Mode or not?  (2/3) Sunday Friday BACKUP CRASH 5 4 3 2 1
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CERN/IT/DB ARCHIVELOG Mode or not?  (3/3) ARCHIVELOG mode implications: Additional overhead (even more overhead during online backup) Oracle hangs if the archived disk fills up Archived logs must be kept in a safe place Tape facilities implied More work for the DBA:  Space management Log files tracking
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 32

backrecovery - CERN/IT/DB Oracle backup and recovery...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online