In the following example, we will set the retention policy to a recovery window of four days
(from a default redundancy policy of 1 copy):
RMAN> configure retention policy to recovery window of 4 days;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 4 DAYS;
new RMAN configuration parameters are successfully stored
RMAN>
Device Type
If the default device type is set to DISK and no pathname parameter is specified, RMAN uses the
flash recovery area for all backups; you can easily override the disk backup location in OEM, as
you can see in Figure 12-4. As with many of the simplified administration tasks from Oracle 11g,
there is no need to allocate or deallocate a specific channel for backups unless you??™re using a
tape device.
Although configuring a tape device is specific to your installation, in general terms we
configure a tape device as follows:
RMAN> configure channel device type sbt
2> parms='ENV=(
)';
NOTE
sbt is the device type used for any tape backup subsystem, regardless
of vendor.
Although we can use the flash recovery area to restore and recover our database entirely from
disk, at some point it becomes inefficient to keep all our backups on disk, especially if we have a
large recovery window. As a result, we can make copies of our backup files to tape, and RMAN
will dutifully keep track of where the backups are in case we need to restore or recover the
database from tape, or restore archived redo logs to roll forward an image copy in the flash
recovery area.
Pages:
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670