Databases Reference
In-Depth Information
Chapter 18
RMAN Backups and Reporting
Chapter 17 provided the details on configuring RMAN and using specialized features to control the behavior of
RMAN. After you consider which features you require, you're ready to create backups. RMAN can back up the
following types of files:
•
Data files
•
Control files
•
Archived redo log files
spfile
s
•
•
Backup pieces
For most scenarios, you will use RMAN to back up data files, control files, and archive redo log files. If you have
the autobackup of the control file feature enabled, then RMAN will automatically back up the control file and the
spfile
(if you're using one) when a
BACKUP
or
COPY
command is issued. You can also back up the backup piece files
that RMAN has created.
RMAN does not back up Oracle Net files, password files, block change tracking files, flashback logs, or the Oracle
binary files (files created when you installed Oracle). If required, you should put in place OS backups that include
those files.
■
Tip
Consider using Oracle Secure Backup to back up OS files to tape (see Chapter 20 for details).
Also note that RMAN does not back up online redo log files. If you were to back up the online redo log files,
it would be pointless to restore them. The online redo log files contain the latest redo generated by the database.
You would not want to overwrite them from a backup with old redo information. When your database is in
archivelog mode, the online redo log files contain the most recently generated transactions required to perform
complete recovery.
This chapter details many of the features related to running the RMAN
BACKUP
command. Also covered are
creating a recovery catalog and techniques for logging output and reporting on RMAN backup operations. This
chapter begins by discussing a few common practices used to enhance what is displayed in the RMAN output when
running commands.
