Database Backup and Recovery (MOSC)

MOSC Banner

Merged Incremental Backup - redundancy settings

edited Dec 10, 2015 9:18AM in Database Backup and Recovery (MOSC) 3 commentsAnswered

Hello,

We have been using merged incremental backups for our 11.2.0.4 databases. 

Here is a snip-it of the RMAN script:

CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;

# Incrementally updated backup with a retention policy of 7 days

# The backup is set to check for logical corruption   (BACKUP CHECK LOGICAL)

RUN {

RECOVER COPY OF DATABASE WITH TAG 'PD_LVL0_MERGE_INCR' UNTIL TIME 'SYSDATE-8';

#RECOVER COPY OF DATABASE WITH TAG 'LVL0_MERGE_INCR';

BACKUP CHECK LOGICAL INCREMENTAL LEVEL 1 CUMULATIVE FOR RECOVER OF COPY WITH TAG 'PD_LVL0_MERGE_INCR' DATABASE;

}

The merged incremental backup script is working fine and so is the Oracle space management.  The retention policy is set to 1 and the backups are stored in the FRA.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center