Chapter 12: Using Recovery Manager (RMAN) 431
Control File Autobackup
Because of the importance of the control file, we want to back it up at least as often as it changes
due to modifications in the structure of the database. By default, the backup of the control file
does not occur automatically. This is a strange default, considering the importance of the control
file and how little disk space it takes to back it up. Fortunately, RMAN can easily be configured to
back up the control file automatically, either any time a successful backup must be recorded in
the repository or when a structural change affects the contents of the control file (in other words,
cases when a control file backup must occur to ensure a successful recovery if and when a recovery
operation is required).
RMAN> configure controlfile autobackup on;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
RMAN>
Every RMAN backup from this point on will automatically include a copy of the control file; the
control file is also backed up whenever a new tablespace is created or another datafile is added to
an existing tablespace.
FIGURE 12-4 Configuring backup destination using OEM
432 Oracle Database 11g DBA Handbook
Backup Compression
If disk space is at a premium, you have a very large database, and you have some extra CPU
capacity, it makes sense to compress the backups to save space.
Pages:
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671