23 Recovery Catalog Creation.pptVIP

Recovery Catalog Creationand Maintenance Recovery Manager Features RMAN provides a flexible way to: Back up the database, tablespaces, datafiles, control files, and archive logs Store frequently executed backup and recovery operations Perform incremental block-level backup Skip unused blocks Specify limits for backups Recovery Manager Features RMAN provides a flexible way to: Detect corrupted blocks during backup Increase performance through: Automatic parallelization Generation of less redo Restricting I/O for backups Tape streaming Manage backup and recovery tasks Recovery Manager Components RMAN Repository: Using the Control File RMAN repository is metadata about target database and backup and recovery operations. RMAN repository is always stored in the control file of the target database. CONTROL_FILE_RECORD_KEEP_TIME determines the minimum age in days of a record before it can be overwritten. The control file can grow in size. Channel Allocation Automatic Channel Allocation Change the default device type: Configure parallelism for automatic channels: Configure automatic channel options: Manual Channel Allocation BACKUP, COPY, RESTORE, and RECOVER commands require at least one channel. Allocating a channel starts a server process on the target database. Channels affect the degree of parallelism. Channels write to different media types. Channels can be used to impose limits. Recovery Catalog Contents The recovery catalog is an optional repository containing information on: Datafile and archived redo log file backup sets and backup pieces Datafile copies Archived redo log files The physical structure of the target database Recovery Catalog Contents The recovery catalog can also contain: Persistent RMAN configuration settings Stored job scripts Benefits of Using a Recovery Catalog The following features are available only when you use a recovery catalog: Metadata about multiple target databases in one catalog Metadata about multiple incarnations of a single ta