Oracle9i DBA II: BackupRecovery and Network Administration

1
Chapter 6Overview of Recovery Manager
2
Chapter Objectives

• List some of the features provided by using
  Recovery Manager (RMAN) to perform backup and
  recovery operations
• Identify the four basic components of RMAN
• Identify the required components of RMAN

3
Chapter Objectives (Cont.)

• Explain the purpose of the Media Management
  Library (MML) interface
• Start the command-line interface of RMAN
• Identify the target database and catalog mode
  when starting RMAN
• List the contents of the RMAN repository

4
Chapter Objectives (Cont.)

• Identify the two possible locations for storing
  the RMAN repository
• Configure RMAN to perform automatic backup of the
  control file
• Explain the purpose of channel allocation

5
Recovery Manager (RMAN) Utility

• Used to backup, restore, and recover database
• Can backup only used data blocks or make image
  copies
• Tests validity of backups
• Requires a server session
• Can store scripts
• Perform incremental block level backup
• Compress unused blocks

6
RMAN Features

• RMAN provides a flexible way to
• Detect corrupted blocks during backup
• Support Oracle parallel server
• Increase performance through
• Automatic parallelization
• Less redo generated
• Restricted I/O for backup
• Tape streaming

7
RMAN Components

• RMAN Executable - required
• Target database - required
• Recovery catalog - optional
• Media Management Library (MML) - optional

8
RMAN Setup Consideration

• Resources Shared memory, more processes
• Privileges to users
• Database SYSDBA SYSOPER
• Operation system access to devices
• Remote operations
• Set up the password file
• Ensure that the password file is backed up
• NLS environment variables
• Format used for the time parameters in RMAN cmd.
• User recovery catalog
• More functionality and options
• Maintenance and storage requirements

9
Starting RMAN
10
RMAN Configuration
11
RMAN Repository

• Repository can be stored in target databases
  control file or in separate database (recovery
  catalog)
• Contains information regarding
• Backup sets and pieces
• Image copies
• Target database schema
• Configuration settings

12
Repository Control File Approach

• Can dramatically increase in size
• Use CONTROL_FILE_RECORD_KEEP_TIME parameter
  specify days worth of retention
• Information regarding RMAN backups unavailable if
  control file is damaged

13
Automatic Control File Backup

• Automatically backup the control file when
• COPY command is executed
• BACKUP command is executed
• Structural change occurs within the database
• Use CONFIGURE CONTROLFILE AUTOBACKUP ON
  statement in RMAN

14
Automating Control File Backup - Example
15
Recovery Catalog

• Stored in separate database
• Can store scripts
• Target database does not have to be mounted for
  recovery
• Can be used to backup and recover multiple
  databases

16
Channel Allocation

• Channel link to the target database via server
  session
• Required for all backup and recovery operations
  in RMAN
• Allocation can be automatic or manual

17
Channel Function
18
Chapter Summary

• RMAN provides more flexibility and options than
  user-managed procedures
• Consists of four components RMAN executable,
  target database, repository, MML interface
• Only RMAN executable and target database are
  required
• Target database can be specified, or default is
  used
• SYSDBA privileged account is required

19
Chapter Summary (Cont.)

• Repository can be in the control file or a
  recovery catalog
• A recovery catalog enables the use of scripts and
  management of multiple databases
• Amount of backup information stored can affect
  the size of the control file
• Channel allocation is required can be automatic
  or manual