The following example uses an RMAN script that
can be scheduled to run at the same time every day to support an incrementally updated backup
strategy:
run
{
recover copy of database with tag 'incr_upd_img';
backup incremental level 1
for recover of copy with tag 'incr_upd_img' database;
}
The key part of both commands within the run script is the recover copy clause. Rather than
doing a recovery of the actual database datafiles, we are recovering a copy of a database datafile
by applying incremental backups. Using a tag with an RMAN backup allows us to apply the
incremental backup to the correct image copy. Tags allow DBAs to easily refer to a specific
backup for recovery or catalog cleanup operations; if the backup command does not provide
448 Oracle Database 11g DBA Handbook
a tag, one is automatically generated for the backupset and is unique within the backupsets for
the target database.
The basics of standard recovery operations and RMAN scripting capabilities are covered later
in this chapter.
The OEM backup wizards make it easy to automate an incrementally updated backup strategy.
In the figures that follow, we??™ll cover the steps needed to configure this strategy within OEM.
In Figure 12-9, we??™re specifying the strategy for backing up our database.
The database is open, archivelog mode is enabled, and backups will follow the Oracle-suggested
guidelines for a backup strategy. The other option in the pull-down menu is Customized.
Pages:
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692