However, to perform a cumulative backup, we add the cumulative keyword:
RMAN> backup as compressed backupset
2> incremental level 1 cumulative database;
How much database activity is performed may also dictate whether you use cumulative or
differential backups. In an OLTP environment with heavy insert and update activity, incremental
backups may be more manageable in terms of disk space usage. For a data warehouse environment
with infrequent changes, a differential backup policy may be more suitable. Compared to using
redo log files, both types of incremental backups are far superior in terms of the time to recover
a database. In any case, we have addressed RMAN??™s retention policy:
RMAN> report need backup;
starting full resync of recovery catalog
full resync complete
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 4 days
Report of files whose recovery needs more than 4 days of archived logs
File Days Name
---- ----- -----------------------------------------------------
RMAN>
Incrementally Updated Backups
An incrementally updated backup can potentially make a recover and restore operation even
more efficient by rolling the changes from a level 1 incremental backup to a level 0 incremental
image backup. If the incrementally updated backup is run on a daily basis, then any recovery
operation would require at most the updated image copy, one incremental level 1 backup, and
the most recent archived and online redo logs.
Pages:
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691