Figure
12-10 shows the next step in the backup configuration process: a summary of the database name,
the strategy selected, where the backups will be sent, the recovery catalog in use, and a brief
explanation as to how the backup will be performed.
In Figure 12-11, we specify when the backups will start, and what time of day they will run.
Although the backup job can run any time during the day, because we are performing a hot backup
(the database is open and users can process transactions), we want to minimize the possible impact
on query and DML response time by scheduling the job during a time period with low activity.
Figure 12-12 gives us one more chance to review how the backup will be performed and
where it will reside.
FIGURE 12-9 OEM backup strategy selection
Chapter 12: Using Recovery Manager (RMAN) 449
FIGURE 12-10 OEM backup setup summary
FIGURE 12-11 OEM backup schedule
450 Oracle Database 11g DBA Handbook
At the bottom of the browser window is the actual RMAN script that will be scheduled to
run on a daily basis (see Figure 12-13). Coincidentally, it strongly resembles the RMAN script
we presented earlier in this section.
Incremental Backup Block Change Tracking
Another way to improve the performance of incremental backups is to enable block change
tracking. For a traditional incremental backup, RMAN must inspect every block of the tablespace
or datafile to be backed up to see if the block has changed since the last backup.
Pages:
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693