Databases are 10G and several 11G databases.
Currently full RMAN backups are running nightly, but now because of nightly offsite disk replication that copies any changed files, I am looking to implement an incremental backup to lessen the data replicated nightly.
I was originally considering a rolling forward incremental something like this:
RUN {
RECOVER COPY OF DATABASE WITH TAG 'incr_update'
UNTIL TIME 'SYSDATE - 2';
BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'incr_update'
DATABASE PLUS ARCHIVELOG;
}
However once day 3 was reached then I am assuming that every day after that there will be a new level 0 backup created from an earlier incremental, thus network traffic will not be lessened.
Since bandwidth allocation for the nightly replication is not as big an issue from Friday to Sunday, I am thinking perhaps a level 0 backup every Friday, with level 1 backups on Sat-Thursday.
Currently I have a 300GB disk allocated for backups (I may be able to get more) and a full backup of the DB is about 70GB, so to keep the disk from getting too full the recovery window is currently set for a retention period of 1 day.
Until I actually run it, I'm not sure how large the level 1 backups will be, but I think the 300GB will suffice. Since the backups are stored in commvault for 30 days, I will just keep the one level 0 backup on disk, replacing it every Friday.
For this to happen I will need to set a recovery window of 6 days, correct?
Is it better to backup the archive logs separate, or can I just use "backup database plus archivelog" with the level 0 and level 1 backups?
Thanks in advance.