Platform independence Backups written with RMAN commands will be syntactically
identical regardless of the hardware or software platform used, with the only difference
being the media management channel configuration. On the other hand, a Unix script
with lots of cp commands will not run very well if the backup script is migrated to a
Windows platform!
Tape manager support All major enterprise backup systems are supported within
RMAN by a third-party media management driver provided by a tape backup vendor.
Cataloging A record of all RMAN backups is recorded in the target database control
file, and optionally in a recovery catalog stored in a different database. This makes
restore and recovery operations relatively simple compared to manually tracking
operating system??“level backups using ???copy??? commands.
Scripting capabilities RMAN scripts can be saved in a recovery catalog for retrieval
during a backup session. The tight integration of the scripting language, the ease of
maintaining scripts in RMAN, and the Oracle scheduling facility make it a better choice
than storing traditional operating system scripts in an operating system directory with the
operating system??™s native scheduling mechanisms.
Encrypted backups RMAN uses backup encryption integrated into Oracle Database 11g
to store encrypted backups. Storing encrypted backups on tape requires the Advanced
Security Option.
In a few limited cases, a traditional backup method may have an advantage over RMAN; for
example, RMAN does not support the backup of password files and other non-database files such
as tnsnames.
Pages:
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657