Managing Enterprise-Wide Backup and Recovery Operations
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
677
On Slideshare
676
From Embeds
1
Number of Embeds
1

Actions

Shares
Downloads
19
Comments
0
Likes
0

Embeds 1

http://www.slideshare.net 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Media Recovery via Enterprise Manager Matthew Hart July 2006 TCOUG
  • 2. Agenda
    • Configuring Backup Settings
    • Configuring Recovery Settings
    • Configure Recovery Catalog Settings
    • EM and Oracle Suggested Backups
    • Scheduling Customized Backup Jobs
    • Recovery from EM
    • Managing Existing Backups in EM
    • Database cloning (duplication)
  • 3. Configure Backup Settings in EM
  • 4. Configure Backup Settings
    • Device Tab
      • Disk Settings
        • Set compression here
      • Tape Settings
        • Set compression here
      • Media Management Settings
      • Host Credentials
  • 5.  
  • 6.  
  • 7. Configure Backup Settings
    • Backup Set Tab
      • Max piece size
      • Tape settings
      • Host Credentials
  • 8.  
  • 9. Configure Backup Settings
    • Policy Tab
      • Set autobackup on
      • Backup optimization
      • Enable block change tracking
      • Tablespace exclusions
      • Retention policy
      • Host Credentials
  • 10.  
  • 11.  
  • 12. Configure Backup Settings
    • What’s missing?
      • Encryption
      • Default Device type
      • Archive Deletion Policy
      • Snapshot Controlfile Location
      • No throttling valuees available for permanent configuration
  • 13. Configure Recovery Settings
  • 14. Configure Recovery Settings
    • FAST_START_MTTR_TARGET
    • Archivelog Mode
    • Archivelog destinations
    • Flash Recovery Area
      • Note the nice little graph of used space in FRA
    • Flashback Database
  • 15.  
  • 16.  
  • 17.  
  • 18. Configuring the Recovery Catalog
  • 19. Configure Recovery Catalog Settings
    • Enterprise Manager is incapable of creating a recovery catalog. It can only register a catalog that has already been created from the command line
    • EM will only register an existing catalog in the EM repository
  • 20.  
  • 21. EM Suggested Backup Strategy
  • 22. Oracle-Suggested Backup Strategies
    • Oracle has built-in backup strategies within EM
    • Utilizes EM job system
    • Takes advantage of RMAN 10g innovations
    • Take them or leave them: they are not ‘tweakable’
  • 23. EM and Oracle Suggested Backups: Disk-only strategy
    • Oracle-Suggested Strategy uses incrementally updated image copies
      • Takes one image copy
      • Takes a new level 1 next day
      • Day 2, level 1 is applied to image copy, new level 1 is taken
      • Backup remains at least 24 hours behind current time, up to 48 hours
  • 24.  
  • 25. Oracle Suggested Backup Strategy: Tape Only
    • No backups ever created in the FRA
    • No incremental apply functionality
    • Two rman scripts: daily and weekly
    • Weekly: full database backup plus archivelogs
    • Daily: incremental backup of changed blocks, plus archivelogs (if desired)
  • 26. Oracle Suggested Backup Strategy: Disk and Tape
    • Disk strategy is the same as disk-only strategy
      • Full image copy in the FRA
      • Incremental backups, incremental apply
    • Tape strategy requires a decision: what do you want daily?
      • Weekly, all recovery files are backed up to tape
      • Daily, you choose: nothing, archivelogs only, archivelogs + incrementals, or archivelogs + full database backupset
  • 27. Oracle-Suggested Strategies: Right for You and Yours?
    • Benefits: ‘set and forget’
    • Good for low priority dev databases with permissive or non-existent SLAs
    • May not provide level of detail or control required for enterprise-dependent systems
  • 28. Scheduling Customized Backups in EM
  • 29. Scheduling Customized Backup Jobs
    • Always starts with type of backup
      • Database
      • Tablespace
      • Datafile
      • Archivelog
      • All recovery files
  • 30.  
  • 31.  
  • 32.  
  • 33.  
  • 34.  
  • 35. Performing Recovery in EM
  • 36. Performing Recovery from EM
    • Displayed as an option if the database is not up
    • In 10gR2, there is guided recovery based on health checks
    • Some intelligence concerning what type of recovery should be undertaken
    • Recovery includes object level recovery option
      • If tables is chosen, flashback recovery options are made available
  • 37. Should I use EM for critical database recovery?
    • EM and panic don’t go hand in hand
    • Down databases are no time for a big read ‘Easy’ button
    • Control is desired at every decision moment
    • It’s a good complement for databases that use the Oracle Suggested Backup Strategy
  • 38.  
  • 39. Managing Current Backups in EM
  • 40. Manage Current Backups
    • Perform common admin tasks
      • Catalog files
      • Crosscheck
      • Delete obsolete
      • Delete expired
    • Manage all files with quick links, or administer individual backupsets or image copies
    • Perform a search based on type of backup, and completion time
  • 41.  
  • 42.  
  • 43. Backup Reports
  • 44. Backup Reports
    • Backups can be viewed based on multiple criteria
    • Drill-down allows user to see which files are in which backupsets
    • In Grid Control, can view multiple-target report
      • This only works for 10.2 databases
  • 45.  
  • 46.  
  • 47. Oracle Database Cloning
  • 48. Database Cloning
    • Database cloning uses RMAN backups and the duplication process to build a clone
    • All RMAN use is ‘behind the scenes’ from EM
    • Clone from the deployments page
  • 49. Database Cloning (cont.)
    • Grid Control only
    • Can clone from a running db, or form a ‘working directory’ created from a previous clone
    • Existing RMAN backups cannot be used
  • 50.  
  • 51. Database Cloning
    • Choose a source host working directory
    • Choose to compress the backup
    • Choose to retain the working dir, or delete on completion
  • 52.  
  • 53. Database Cloning
    • Choose Destination database global_name, SID
    • Choose storage type (files, ASM, raw)
    • Choose host
  • 54.  
  • 55. Database Cloning
    • Choose Destination file locations
    • Provide information about networking files
    • Decide if new clone will be registered with EM Grid Control
  • 56.  
  • 57. Database Cloning
    • Schedule and review the job
  • 58.  
  • 59. Q & A
  • 60. Q & A