The second backup of the control file, however, has a record of
the first control file and SPFILE backup.
Archived Redo Logs
Even when archived redo logs are sent to multiple destinations, including the flash recovery area,
due to the critical nature of the archived redo logs, we want to back up copies of the logs to tape
or another disk destination. Once the backup is completed, we have the option to leave the logs
in place, to delete only the logs that RMAN used for the backup, or to delete all copies of the
archived logs that were backed up to tape.
In the following example, we back up all the archived log files in the flash recovery area and
then remove them from disk:
RMAN> backup device type sbt archivelog all delete input;
Chapter 12: Using Recovery Manager (RMAN) 445
If archived log files are being sent to multiple locations, then only one set of the archived redo
log files are deleted. If we want all copies to be deleted, we use delete all input instead of delete
input. As of Oracle Database 11g, corrupt or missing archived log files do not prevent a successful
RMAN backup of the archived logs as in previous releases; as long as one of the archive log file
destinations has a valid log file for a given log sequence number, the backup is successful.
Backing up and deleting only older archived redo log files can be accomplished by specifying
a date range in the backup archivelog command:
RMAN> backup device type sbt
2> archivelog from time 'sysdate-30' until time 'sysdate-7'
3> delete all input;
In the preceding example, all archived redo logs older than one week, going back for three
weeks, are copied to tape and deleted from disk.
Pages:
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687