Intro to the Class.ppt.ppt

RMAN The Oracle Recovery Manager (RMAN) Objectives At the end of this module the student will understand the following tasks and concepts. Understand the basic functionality of the Oracle Recovery Manager. Understand how to perform basic backup and recovery operations using RMAN. Intro to RMAN Oracle Recovery Manager Backup and Restore Client Complete or Partial Backups Full or Incremental Backups Detects corrupted blocks and reports them Automatically tracks new tablespaces and datafiles Does unused block compression Employs binary compression for disk backups Can test backups without restoring them The RMAN Recovery Catalog Recovery Catalog Used to store repository records Stores RMAN scripts Can be stored in its own tablespace on a separate server Can use the controlfiles if a recovery catalog database is not available Recovery Catalog Options RMAN defaults to the NOCATALOG connect option Uses the target database controlfile for storing recovery metadata Useful for simple backup and recovery options for a single database With the CATALOG connect option, a Recovery Catalog may be used A Recover Catalog is a centralized recovery metadata repository Useful for simple to complex backup and recovery options for multiple databases on multiple servers Issues with Using Controlfiles for RMAN Metadata RMAN records will eventually “age out” of the control file and the records will be reused Use the CONTROLFILE_RECORD_KEEP_TIME init.ora parameter to control the retention period (default is 7 days) Rebuilding the control file will result in RMAN record loss The command “alter database backup controlfile to trace;” does not backup RMAN records Use “alter database backup controlfile to ‘location’;” instead to create a binary controlfile copy that maintains RMAN records Why Use a Recovery Catalog? Offers a single enterprise-wide repository for maximum flexibility Allows the use of stored RMAN scripts Allows you to restore a database from a previous incarnation (period befor