In addition, RMAN supports a failover location
for archived redo log files when the flash recovery area is full. Finally, the duplicate command
now supports creating a duplicate database or physical standby database without using database
backup files; this dramatically reduces the amount of time needed to create a copy of a database.
Due to the wide variety of tape backup management systems available, discussing any particular
hardware configuration would be beyond the scope of this book. Instead, the focus in this chapter
will be on using the flash recovery area, a dedicated area allocated on disk to store disk-based
copies of all types of objects that RMAN can back up. The flash recovery area is new to Oracle 10g.
For all the examples in this chapter, we will use a recovery catalog with RMAN. Although most
of the functionality of RMAN is available by only using the control file of the target database,
benefits such as being able to store RMAN scripts and additional recovery capabilities far outweigh
the relatively low cost of maintaining an RMAN user account in a different database.
RMAN Features and Components
RMAN is more than just a client-side executable that can be used with a web interface. It comprises
a number of other components, including the database to be backed up (the target database), an
optional recovery catalog, an optional flash recovery area, and media management software to
support tape backup systems.
Pages:
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652