8i | 9i | 10g | 11g | 12c | 13c | 18c | 19c | Misc | PL/SQL | SQL | RAC | WebLogic | Linux

Home » Misc » Here

Comments for Incrementally Updated Backups : Rolling Forward Image Copies Using RMAN


Jamal said...

This feature a lot of people are unaware the reason maybe incremental update copy is not mandatory for backup planing but the concept is really cool and I personally feel this concept Should aware

d.vega said...

Line: "...The BACKUP INCREMENTAL line will perform a complete backup (level 0) the first day it is run..."
This line can confuse readers making them think it will perform a "level 0 incremental backup set" (just like as if you perform a BACKUP DATABASE INCREMENTAL LEVEL 0 command), when this strategy is based on IMAGE COPIES rather than BACKUP SETS. i.e: it will create level 0 datafile copies.

Tim... said...

Hi.

Agreed. I've altered the wording so that misunderstanding is less likely.

Cheers

Tim...

Akshay said...

RUN {
RECOVER COPY OF DATABASE WITH TAG 'mydb_incr_backup' UNTIL TIME 'SYSDATE - 7';
BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'mydb_incr_backup' DATABASE;
}

Would it make a difference if the 1st line (RECOVER COPY OF DATABASE...) be on the 2nd line ?
and vice-versa 2nd line become the 1st.

Tim... said...

Hi.

The order doesn't matter in this case. I tend to do it this way with a delete obsolete between them to minimise the space I'm using on disk. Delete the old before making the new. :)

Cheers

Tim...

DO NOT ask technical questions here! They will be deleted!

These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!

If you post personal information (name, email address etc.) you are agreeing to them being stored and displayed. Feel free to remain anonymous.