The RMAN recovery catalog, whether using the target database control file or a dedicated
repository in a separate database, contains the location of recovery data, its own configuration
settings, and the target database schema. At a minimum, the target database control file contains
this data; to be able to store scripts and to maintain a copy of the target database control file, a
recovery catalog is highly recommended. In this chapter, all examples will use a recovery catalog.
FIGURE 12-1 Accessing RMAN functionality from OEM
420 Oracle Database 11g DBA Handbook
As of Oracle 10g, the flash recovery area simplifies disk-based backup and recovery by defining
a location on disk to hold all RMAN backups. Along with the location, the DBA can also specify
an upper limit to the amount of disk space used in the flash recovery area. Once a retention
policy is defined within RMAN, RMAN will automatically manage the backup files by deleting
obsolete backups from both disk and tape. The initialization parameters related to the flash recovery
area are covered in the next section.
To access all non-disk-based media, such as tape and DVD-ROM, RMAN utilizes third-party
media management software to move backup files to and from these offline and near-line devices,
automatically requesting the mount and dismount of the appropriate media to support backup
and restore operations. Most major media management software and hardware vendors have
device drivers that directly support RMAN.
Pages:
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654