5 Copyright © 2004, Oracle. All rights reserved. Using Recovery Manager

5-2 Copyright © 2004, Oracle. All rights reserved. Objectives After completing this lesson, you should be able to do the following: Use the RMAN BACKUP command to create backup sets and image copies Manage the backups and image copies taken with RMAN

5-3 Copyright © 2004, Oracle. All rights reserved. Issuing Recovery Manager Commands Interactive client –Type commands at RMAN prompt –Use when doing analysis, running reports or stored scripts Batch mode –Use with automated jobs –Specify a command file when starting RMAN –Set the log file to obtain information Pipe interface –Specify the PIPE command line argument –Use to communicate data between sessions or between RMAN and an external application

5-4 Copyright © 2004, Oracle. All rights reserved.

5-5 Copyright © 2004, Oracle. All rights reserved. RMAN Command Overview Stored scripts Target database REPORT LIST Catalog database Enterprise Manager Restore/Recover/Flashback Catalog maintenance CROSSCHECK DELETE…EXPIRED LIST CHANGE SPFILE Backup Control file Archived log files RMAN

5-6 Copyright © 2004, Oracle. All rights reserved. RMAN Commands RMAN commands are of the following types: Stand-alone –Executed individually at the RMAN prompt –Cannot appear as subcommands within RUN Job –Must be within the brackets of RUN –Executed as a group Stand-alone or job –Can be executed at the RMAN prompt and run individually –Can be run within the brackets of RUN and executed within a group

5-7 Copyright © 2004, Oracle. All rights reserved. Job Command: Example RUN command: RMAN>RUN { 2>BACKUP AS BACKUPSET 3>FORMAT '/u01/db01/backup/%d_%s_%p' 4> DURATION 10:00 MINIMIZE LOAD 5>(DATABASE); 6>SQL 'alter system archive log current'; 7>}

5-8 Copyright © 2004, Oracle. All rights reserved. The BACKUP Command RMAN> BACKUP AS BACKUPSET 2> FORMAT '/BACKUP/df_%d_%s_%p.bus' 3> TABLESPACE hr_data; Backup set Data file 1 Data file 2 Data file 3 Data file 1 Data file 2 Data file 3 Tablespace HR_DATA

5-9 Copyright © 2004, Oracle. All rights reserved. Backup Constraints The database must be mounted or open. Online redo log backups are not supported. Only “clean” backups are usable in NOARCHIVELOG mode. Only “current” data file backups are usable in ARCHIVELOG mode.

5-10 Copyright © 2004, Oracle. All rights reserved. Parallelization of Backup Sets Allocate multiple channels and assign files to specific channels. Data file 4 Data file 1 Data file 5 Channel MML Backup piece 1 Backup piece 2 Data file 2 Data file 3 Data file 9 Channel MML Data file 6 Data file 7 Data file 8 Backup Piece 3 Channel MML

5-11 Copyright © 2004, Oracle. All rights reserved.

5-12 Copyright © 2004, Oracle. All rights reserved. Compressed Backups RMAN> BACKUP AS 2> COMPRESSED BACKUPSET 3> DATABASE; RMAN> CONFIGURE DEVICE TYPE 2> DISK PARALLELISM 2 3> BACKUP TYPE TO 4> COMPRESSED BACKUPSET; Compressed backup files Database files

5-13 Copyright © 2004, Oracle. All rights reserved. Image Copy Copy of data file 3 Copy of archived log Data file 3 Archived log file Data file 3 Archived log file RMAN> BACKUP AS COPY 2> DATAFILE '/ORADATA/users_01_db01.dbf' 3> FORMAT '/BACKUP/users01.dbf' tag=DF3; RMAN> BACKUP AS COPY 4> ARCHIVELOG LIKE 'arch_1060.arc' 5> FORMAT 'arch_1060.bak';

5-14 Copyright © 2004, Oracle. All rights reserved.

5-15 Copyright © 2004, Oracle. All rights reserved. Tags for Backups and Image Copies A tag is a logical name assigned to a backup set or image copy. month_full_backup week_full_backup Wednesday_1_backup Data file 3 Data file 4 Backup set Data files 1,3 Data files 2,4 Backup set Data file 1 Backup set

5-16 Copyright © 2004, Oracle. All rights reserved. BACKUP Options Check for physical block corruptions Scan for logical corruptions in addition to physical corruptions Set a threshold on the number of detected corruptions allowed before aborting Validate the target input files before performing a backup operation Duplex the backup set Overwrite an existing backup set or image copy Pass control over the data transfer between storage devices and the data files on disk to the media management layer

5-17 Copyright © 2004, Oracle. All rights reserved.

5-18 Copyright © 2004, Oracle. All rights reserved. Backing Up Archived Redo Logs Online redo log file switch is automatic. Archived log failover is performed. You can specify a range of archived redo logs to back up. Backup sets include only archived redo log files. RMAN> BACKUP 2> FORMAT '/disk1/backup/ar_%t_%s_%p' 3> ARCHIVELOG FROM SEQUENCE=234 4> DELETE INPUT;

5-19 Copyright © 2004, Oracle. All rights reserved. Copying the Whole Database RMAN> BACKUP DATABASE PLUS ARCHIVELOG; Archived log file copies SPFILE Control file Data file copies

5-20 Copyright © 2004, Oracle. All rights reserved. Making Incremental Backups A level 0 incremental backup, similar to a full backup, contains all data file blocks. A cumulative level 1 incremental backup contains only blocks modified since the last level 0 incremental backup. A differential level 1 incremental backup contains only blocks modified since the last incremental backup. Full backup Differential incremental backup Cumulative incremental backup

5-21 Copyright © 2004, Oracle. All rights reserved.

5-22 Copyright © 2004, Oracle. All rights reserved. Incremental Backup: Example A differential incremental backup contains all blocks changed since the last incremental backup A cumulative incremental backup contains all blocks changed since the last level 0 incremental backup Lvl Day SunMonTueWedThuFriSatSun Level 0 111c1100

5-23 Copyright © 2004, Oracle. All rights reserved. Block Change Tracking Records changed blocks in a change tracking file Is used automatically by RMAN if enabled Optimizes incremental backups by avoiding full data file scans during backup List of changed blocks Redo generation Redo log Change tracking file SGA CTWR

5-24 Copyright © 2004, Oracle. All rights reserved. Enabling Block Change Tracking SQL> ALTER DATABASE ENABLE 2> BLOCK CHANGE TRACKING 3> USING FILE '/mydir/rman_change_track.f' 4> REUSE;

5-25 Copyright © 2004, Oracle. All rights reserved. Incrementally Updating Backups Incremental backup files Recovered data file Image copy of data file Image copy of data file updated to a more recent state RMAN> RECOVER COPY OF 2> DATAFILE {n|'file_name'} 3> WITH TAG 'incr_upd_df1';

5-26 Copyright © 2004, Oracle. All rights reserved. LIST Command Operations List backup sets and copies of data files Lists backup sets and copies of any data file for a specified tablespace Lists backup sets and copies containing archive logs for a specified range RMAN> LIST BACKUP OF DATAFILE 2> "/db01/ORADATA/u03/users01.dbf"; RMAN> LIST BACKUP OF DATABASE; RMAN> LIST COPY OF TABLESPACE "SYSTEM"; RMAN> LIST COPY OF DATABASE ARCHIVELOG 2> FROM TIME='SYSDATE-7';

5-27 Copyright © 2004, Oracle. All rights reserved. The REPORT Command Produces a detailed analysis of the repository Produces reports to answer: –Which files need a backup? –Which backups can be deleted? –Which files are unrecoverable?

5-28 Copyright © 2004, Oracle. All rights reserved. The REPORT NEED BACKUP Command Lists all data files that require a backup Assumes the most recent backup is used during a restore Provides four options: –Incremental –Days –Redundancy –Recovery window Uses the current retention policy configuration if no options are specified

5-29 Copyright © 2004, Oracle. All rights reserved. REPORT NEED BACKUP : Examples Files needing three or more incremental backups for recovery: Files have not been backed up for three days: Backup needed if there are not two or more: Backup needed to recover 3 days past: RMAN> REPORT NEED BACKUP days 3; RMAN> REPORT NEED BACKUP incremental 3; RMAN> REPORT NEED BACKUP redundancy 2; RMAN> REPORT NEED BACKUP 2> recovery window of 3 days;

5-30 Copyright © 2004, Oracle. All rights reserved. REPORT OBSOLETE and DELETE OBSOLETE Find all obsolete recovery files using the current retention policy settings: List the obsolete recovery files, if no more than two backup copies are needed: Delete the backup set with a backup set key of 4: Delete the recovery files considered obsolete, because they have more than two backups: RMAN> REPORT OBSOLETE REDUNANCY 2; RMAN> REPORT OBSOLETE; RMAN> DELETE BACKUPSET 4; RMAN> DELETE OBSOLETE REDUNDANCY 2;

5-31 Copyright © 2004, Oracle. All rights reserved. Managing Backups with EM

5-32 Copyright © 2004, Oracle. All rights reserved. RMAN Dynamic Views V$ARCHIVED_LOG V$BACKUP_CORRUPTION V$BACKUP_DEVICE V$BACKUP_FILES V$BACKUP_PIECE V$BACKUP_REDOLOG V$BACKUP_SET V$BACKUP_SPFILE V$COPY_CORRUPTION V$RMAN_CONFIGURATION

5-33 Copyright © 2004, Oracle. All rights reserved.

5-34 Copyright © 2004, Oracle. All rights reserved. Monitoring RMAN Backups Correlate server sessions with channels using the SET COMMAND ID command. Query V$PROCESS and V$SESSION to determine which sessions correspond to which RMAN channels. Query V$SESSION_LONGOPS to monitor the progress of backups and copies. Use an operating system utility to monitor the process or threads.

5-35 Copyright © 2004, Oracle. All rights reserved.

5-36 Copyright © 2004, Oracle. All rights reserved. Summary In this lesson, you should have learned how to: Use the RMAN BACKUP command to create backup sets and image copies Manage the backups and image copies taken with RMAN

5-37 Copyright © 2004, Oracle. All rights reserved. Practice 5 Overview: Using RMAN This practice covers the following topics: Enabling archival of redo logs for a database Using RMAN to display the database structure Using Recovery Manager to back up data files and the control file Using Recovery Manager to make image copies of data files Creating a compressed backup of a database Scheduling a backup job

5-38 Copyright © 2004, Oracle. All rights reserved.