Incremental level backup

If I take incremental level 0 backup on Monday, full database image copy backup on Tuesday, incremental level 1 on Wednesday and Incremental level 2 backup on Thursday;
Can i do complete recovery on Friday by applying incremental level 1 & 2 backup on the image copy backup???

Atiq wrote:
If I take incremental level 0 backup on Monday, full database image copy backup on Tuesday, incremental level 1 on Wednesday and Incremental level 2 backup on Thursday;
Can i do complete recovery on Friday by applying incremental level 1 & 2 backup on the image copy backup???There is no incremental level 2 backup in oracle, only level zero and level one. Or do you mean a second incremental level one?
Your first incremental level 1 will have all the changes since the incremental level 0. The fact that you took an image copy will not be considered by that backup.
was your image copy taken when the db was cleanly shut down? Did it include the control files?

Similar Messages

Incremental RMAN Backup to tape.

Hi,
We have 2.2 TByte Oracle Dataware House. At weekends, we would like to take inceremental level 0 backup to tape and then incemental level 1 to disk daily.
So that we expect to reduce disk space for backup. We also handle the cover risk of direct path load by mains of incremental level backup.
But, I would like to know that, taking incremental level 0 to tape causes performance problems. Rman try to discover changes between the incemental level 0 on the tape and incemental level 1 on the disk.
Should we take both incremental level 0 and incremental level 1 to disk or tape?
I need your recomendations.
Thank you.

Thank you Satish Kandi for your reply,
As far as understand accourding to document that you refer,
if we configure well adjustment for channel of disk and tape io buffers,
and multiplexing, then we can take backup incemental level 0 to tape.
We don't want to use encryption and compression in order not to consume CPU resources.
In fact, we should try and obsorve the performance.
Thank you.

Backup RMAN Incremental Level 1 without Level 0 - 10gR2

Hi,
I'm a bit confused after some tests.
The Question: It's mandatory to perform backup incremental level 0 before the level 1 using Oracle 10gR2 ?
On Oracle 11.2 it's mandatory but on Oracle 10.2.0.5 I don't know.
Test on 11.2. If doesn't exists level 0 rman take care about it and perform automaticaly level 0 before level1
RMAN> backup incremental level 1 database;
Starting backup at 29-APR-11
using channel ORA_DISK_1
no parent backup or copy of datafile 1 found
channel ORA_DISK_1: starting incremental level 0 datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
...Docs said:
Incremental backups capture only those blocks that change between backups in each datafile.
In a typical incremental backup strategy, a level 0 incremental backup is used as a starting point. A level 0 backup captures all blocks in the datafile.
So, on Oracle 10.2.0.5 this not happen like on 11.2:
Perfoming backup level 1 without level 0:
RMAN> list backup;
RMAN> backup incremental level 1 database;
Starting backup at 29-APR-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+DG_ORCL/db10g/datafile/system.260.749756975
channel ORA_DISK_1: starting piece 1 at 29-APR-11
channel ORA_DISK_1: finished piece 1 at 29-APR-11
piece handle=+DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421 tag=TAG20110429T190340 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 29-APR-11
channel ORA_DISK_1: finished piece 1 at 29-APR-11
piece handle=+DG_FRA/db10g/backupset/2011_04_29/ncsnn1_tag20110429t190340_0.262.749761449 tag=TAG20110429T190340 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:05
Finished backup at 29-APR-11
RMAN> backup archivelog all delete input;
Starting backup at 29-APR-11
current log archived
using channel ORA_DISK_1
Finished backup at 29-APR-11
RMAN> shutdown abort;
Oracle instance shut downDelete all files on ASM (except SPFILE).
ASMCMD> cd +DG_ORCL/DB10g
ASMCMD> ls
PARAMETERFILE/
spfiledb10g.oraSo, let's perfom restore of database
oracle@butao:/home/oracle> rman target /
Recovery Manager: Release 10.2.0.5.0 - Production on Fri Apr 29 19:06:52 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount
Oracle instance started
Total System Global Area     293601280 bytes
Fixed Size                     2095872 bytes
Variable Size                 92275968 bytes
Database Buffers             192937984 bytes
Redo Buffers                   6291456 bytes
RMAN> restore controlfile from '+DG_FRA/db10g/backupset/2011_04_29/ncsnn1_tag20110429t190340_0.262.749761449';
Starting restore at 29-APR-11
using channel ORA_DISK_1
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
output filename=+DG_ORCL/db10g/controlfile/current.263.749761699
output filename=+DG_FRA/db10g/controlfile/current.263.749761699
Finished restore at 29-APR-11
RMAN> startup mount
database is already started
database mounted
released channel: ORA_DISK_1
RMAN> restore database;
Starting restore at 29-APR-11
Starting implicit crosscheck backup at 29-APR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 29-APR-11
Starting implicit crosscheck copy at 29-APR-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 29-APR-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: +dg_fra/DB10G/BACKUPSET/2011_04_29/ncsnn1_TAG20110429T190340_0.262.749761449
File Name: +dg_fra/DB10G/BACKUPSET/2011_04_29/annnf0_TAG20110429T190442_0.264.749761485
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DG_ORCL/db10g/datafile/system.260.749756975
restoring datafile 00002 to +DG_ORCL/db10g/datafile/undotbs1.261.749757085
restoring datafile 00003 to +DG_ORCL/db10g/datafile/sysaux.262.749757095
restoring datafile 00004 to +DG_ORCL/db10g/datafile/users.264.749757107
channel ORA_DISK_1: reading from backup piece +DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421
channel ORA_DISK_1: restored backup piece 1
piece handle=+DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421 tag=TAG20110429T190340
channel ORA_DISK_1: restore complete, elapsed time: 00:00:26
Finished restore at 29-APR-11
RMAN> recover database;
Starting recover at 29-APR-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 27 is already on disk as file +DG_FRA/db10g/onlinelog/group_3.259.749756971
archive log thread 1 sequence 28 is already on disk as file +DG_FRA/db10g/onlinelog/group_1.257.749756963
archive log filename=+DG_FRA/db10g/onlinelog/group_3.259.749756971 thread=1 sequence=27
archive log filename=+DG_FRA/db10g/onlinelog/group_1.257.749756963 thread=1 sequence=28
media recovery complete, elapsed time: 00:00:02
Finished recover at 29-APR-11
RMAN> alter database open resetlogs;
database opened
RMAN>See I don't need level 0 backup to restore level 1.
Thanks,
Levi Pereira

Hi Gokhan,
Thank you for point this.
After spending a time studying about this I find out this:
Your expanation apply only in Oracle 10gR1/R2.
Because there is differences between RMAN Version 10gR1/R2 and 11gR1/R2 about Incremental Level 1 and this confuse me.
Oracle 10gR1/R2 run only one backup incremental level 1 even if level 0 not exists .
Oracle 11gR1/R2 run two backups incremental if level 0 not exists. i.e level 0 first and after that level 1.
Oracle 10gR2
If no level 0 backup is available, then the behavior depends upon the compatibility mode setting. If compatibility is >=10.0.0, RMAN copies all blocks changed since the file was created, and stores the results as a level 1 backup. In other words, the SCN at the time the incremental backup is taken is the file creation SCN.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm
Thats means wich RMAN run level 0 with name level 1. (i.e: Only one Backup) This is confuse.
Oracle 11gR1
If no level 0 backup is available in either the current or parent incarnation, then the behavior varies with the compatibility mode setting. If compatibility is >=10.0.0, RMAN copies all blocks that have been changed since the file was created. Otherwise, RMAN behaves as it did in previous releases, by generating a level 0 backup.
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmcncpt.htm#BRADV89500
Oracle 11gR2
If no level 0 backup is available in either the current or parent incarnation, then the behavior varies with the compatibility mode setting. If compatibility is >=10.0.0, RMAN copies all blocks that have been changed since the file was created. Otherwise, RMAN generates a level 0 backup.
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV89500
Thats means wich RMAN run (automatically) level 0 first after finish level 0 backup RMAN run level 1 backup (i.e Two Backups). This seems right.
Regards,
Levi Pereira

What is the right TAG for incremental level 1 backup?

We have a sunday level 0 backup like this:
run {
backup as compressed backupset
filesperset 1
     incremental level 0 database
     tag='LEVEL_0_BACKUP'
     include current controlfile
     plus archivelog delete input;
SQL 'alter database backup controlfile to trace';
And Monday to Saturday incremental level 1 backup as this:
run {
backup as compressed backupset
     incremental level 1 database
     tag='LEVEL_1_BACKUP'
     include current controlfile
     plus archivelog delete input;
SQL 'alter database backup controlfile to trace';
Those scripts existed a while ago. I wonder if level 1 tag should be same as level 0 so they can all combined together?
Please kindly advice.

849425 wrote:
Thanks for all your response.
What I think is with block change tracking enabled, is that the incremental should roll into the level 0 full backup?
What makes you think that? Block change tracking simply allows rman to avoid having to scan every block to see if it needs to be backed up.
I've never heard of an incremental (level 1) "rolling into" a level 0.
Recovery starts with restoring the files from a level 0. Followed by restoring individual blocks from the Level 1. Followed by applying changes from the archived redo. Followed by (if necessary) applying changes from the online redo.
As stated earlier, tags are just user-defined labels. Use them however seems appropriate -- after fully understanding what they are and what they are not. User-specified tags are not even required. I'd be cautious about changing them in an already defined and running system.

Backup incremental level 0 cumulative database

On RMAN Level 0 backup when I say cumulative like below what the difference that command make;
backup filesperset 1 format '<%d_%s:%t:%p:%f>.df' incremental level 0 cumulative database;Edited by: Sivaprasad S on Sep 1, 2012 12:42 AM
Edited by: Sivaprasad S on Sep 1, 2012 12:44 AM

In a cumulative level 1 backup, RMAN backs up all blocks used since the most recent level 0 incremental backup in either the current or parent incarnation. Cumulative incremental backups reduce the work needed for a restore by ensuring that you only need one incremental backup from any particular level. Cumulative backups require more space and time than differential backups because they duplicate the work done by previous backups at the same level.

Larger backups for cumulative incremental level 1 backups

I am noticing some strange behaviour for backup of data files in the RMAN cumulative incremental level 1 backup for certain days. I would explain that with an elaboration- the cumulative backup sizes are around 2GB, 19GB, 19GB, 1GB for the dates of 10th Dec, 5th Dec, 3rd Dec and 28th Nov respectively.
Can there be so much difference between the values of backup size for the RMAN cumulative incremental level 1 backup as they are fluctuating from 19GB->1GB?
I hope, my question is clear.
Please revert with the reply to my query.
Regards

975148 wrote:
Thanks for your reply. Level 0 backup happened twice between 5th Dec and 10th Dec. I guess, a block which has changed multiple times would be backed up once with all the changes done in a backup on a particular day. The same changes should get reflected in the subsequent level 0 backup.
Regards
Yes, obviously any backup (of any kind, of any product) is only capable of backing up the state of things as they exist at the time of the backup.
The recoverability of "intermediate" states (say a given block was modified 5 times between backups, the next backup only gets the 5th state of the block) is done by applying redo - archived or online, as is needed.
So to make an example to replicate what you report
Day 1 - backup level 0
- block # 1 modified
Day 2 - backup level 1 - backs up Block #1 - backup size 8k
- block # 1 modified
- block # 2 modified
- block # 1 modified
- block # 3 modified
- block # 1 modified
- block # 4 modified
Day 3 - backup level 1 - backs up Blocks 1,2,3,4 - backup size 32k
- block # 5 modified
- block # 2 modified
- block # 7 modified
- block # 3 modified
- block # 6 modified
- block # 4 modified
Day 4 - backup level 1 - backs up Blocks 1,2,3,4,5,6,7 - backup size 56k
- block # 5 modified
Day 4 - backup level 1 - backs up Blocks 1,2,3,4,5,6,7 - backup size 56k
Day 6 - backup level 0 - all blocks - size ???
- block # 3 modified
Day 7 - backup level 1 - backs up block 3 - backup size 8 k

Block Media Recovery and RMAN Incremental Level 1 backup

Hi
I have read somewhere that Block Media Recovery will not work if a database is backed up using rman incremental 1. Is this true, and if so is there a work around?
I cannot seem to find this in oralce's documentation.
Regards
Me

Hi,
1) is Full Backup = Incremental level 0 backup?
Yes
2) When oralce say BMR does not work with incremental, will it work in the case I put forward. becuase Im doing an incremental 0...
But does you have the Archive logs available.. ?? If yes then it will Support.
3) Im my case will BMR work...that is use Incr level 0 on Sunday and then use archive logs for mon, tues etc
Yes, I believe.
@Hemanth .. am I right.. ?? Wait for your inputs...
- Pavan Kumar N

If RMAN incremental level-1 backup fails...

Hi there,
I have a question. If the RMAN incremental level-1 backup fails, will the next level-1 backup attempt take backup of all changes since last successful level-0 OR level-1 backup?
Best regards

Hi,
I have a question. If the RMAN incremental level-1 backup fails, will the next level-1 backup attempt take backup of all changes since last successful level-0 OR level-1 backup?
Check the V$BACKUP_SET dictionary to confirm whether the last backup has been touched by data dictionary. If the failed incremental backup is picked up then the previous incremental backup will be required in case of the next DIFFERENTIAL INCREMENTAL LEVEL 1 backup.
But to be on safe side , it is recommended you take a LEVEL 01 CUMILATIVE INCREMENTAL backup from Level 0 till date. So that the recovery process can go through even if the previous backup is not valid.
Thanks &
Best Regards

RMAN Backup Incremental levels

hi experts,
This is a 10g database running in archivelog mode.
This is the backup scheme I'm currently using:
backup database plus archivelog; (runs once per day)
backup incremental level 1 database; this runs every 3 hours
All the incrementals I make are level 1.
** Would I be able to restore, if I have no Level 0 incremental? **
Thanks, John

user629010 wrote:
Thanks for the replies.
So I should make a level 0 backup immediately after the whole backup (backup database;) is that correct?
No its not correct as level 0 is actually the whole backup only. This is the point which includes everything and from hereonly, you start your next batch of incremental backups. You can throw away the last backups done if you have taken a level 0 backup as it covers everything and is a complete backup.
HTH
Aman....

Difference between backup incremental level 0 Vs incremental level 1?

I am getting confuse. I have 2 commands:
-- Weekly full backup --
backup incremental level 0 database plus archivelog delete all input;
-- Daily backup --
backup incremental level 1 cumulative database plus archvielog delete all inputs;
What is the different if I put "level 1" in the weekly full backup and "level 0" in daily backup?
FAN

Its not much tricky read the doc
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1005.htm#sthref242What you are not getting everything is written there.
Khurram

Incrementally updated backup and EMC NMDA

Hello Everyone,
I'm kind of a newbie in setting up networker module for oracle, to backup database to tape. We use the oracle's suggested backup strategy to backup DB to Disk first using the incrementally updated backups with recovery set to 3 days (RECOVER COPY OF DATABASE WITH TAG ... UNTIL TIME 'SYSDATE-3') , which helps us to recover DB to any point in time using the backup files in disks vs. going to tape. After backup to disk, we backup recovery area to tape nightly. However, we do want to maintain backup Retention Policy of 1 month. Couple of questions,
1. If i set RP to recovery window of 31 days in RMAN, then backups don't obsolete at all. this forces me to set RP in networker and they don't recommend setting RP in both RMAN and networker. how is this done generally to obsolete backups from tape as well as rman (catalog in CF) with above strategy. perhaps in this case i should set RP in netwoker and set RP in RMAN to none and rely on crosscheck and delete expired commands to sync with RNAM catalog.
2. Wondering if nightly backup of recovery area to tape is going to take incremental from previous day and NOT full backup. The reason i ask is, i do not want the tape to do full backup of FRA every day cause full backup datafiles change once in 3 days based on the until time set. is there an option do set in networker to do incremental only or that's the default.
Thanks in Advance!
11gR2, 4 Node RAC, Linux, NMDA 1.1, Networker 7.6 sp1

Loic wrote:
You do a full backup of the FRA on tape ?No, I do a full backup of the database on tape. Using RMAN together with Veritas NetBackup.
I mean if you use incremental updated backup it'll not work on tape... Because the level 0 backup that will be updated with the backup of the day after will be on tape and will not be updated.The incrementally updated backup is in the FRA only, on disk (both the image copy and the following backup sets that are used for recovery of the image copy). Never gets written to tape or updated on tape.
Why don't you use then normal incremental backup ? That will have no problem with the tape backup even if level0, or level1,2 becomes reclaimable... ?I think I do :-)
Maybe:
To keep that you can put the redundancy to 2 out of 1 copy. Like this even with one copy on disk and tape it'll say keep the 2 copies.
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;I'll think about that.

INCREMENTAL MERGE BACKUP & RECOVERY

INCREMENTAL MERGE BACKUP & RECOVERY
=====================================
1) 개요
RMAN을 이용하여 database의 Image copy를 Backup하고 그 Backup에 retention policy만큼의 Incremental Backup을 적용하여서 복구의 시간을 단축한 Backup의 방법입니다.
즉 retention policy에 설정되어있는 시간 전의 최후의 시간까지 Image Copy를 보장하는 방법이며 Disk Space는 Incremental Backup만 사용하는 방법보다는 Image Copy를 사용하는 것임으로 많이 소요됩니다.
물론 Backup & Recovery 정책에 따라서 Retention Policy를 Recovery Window나 Redundancy 2이상으로 설정할 수 있으나, Incremental Merge Backup & Recovery의 장점을 극대화 하기 위해서는 Redundancy 1 (Default)로 설정하는 것을 권해드립니다.
2) 장점
- Recovery 시에 최근 Incremental Backup의 정보들이 적용이 되어있기 때문에 최소한의 시간으로 Recovery 작업을 진행하실 수 있습니다. 물론 장점을 극대화 하시기 위해서는 Retention Policy를 redundancy 1로 설정해 주시길 권해드립니다.
- Datafile들의 Destination을 Backup된 Image Copy가 있는 곳으로 Switch 하여 Restore하는 시간을 단축하셔서 Recovery를 진행하실 수도 있으나 Recovery 후의 관리의 용이성을 위해 부득히한 경우를 재외하고는 권장하지 않습니다.
3) Syntax
- Backup
RMAN> BACKUP INCREMENTAL LEVEL 1
FOR RECOVER OF COPY
WITH TAG WEEKLY DATABASE;
위 명령어를 사용하시면 WEEKLY라는 Tag로 생성된 Copy가 없을 시에는 Image Copy를 Weekly라는 Tag로 구분하여 Backup을 받게 됩니다.
* 여기서 Copy라 함은 FOR RECOVER OF COPY라는 구문을 사용하여서 만든 Image Copy를 뜻합니다.
RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY;
위 명령어를 사용하시면 현재 받았던 Incremental Backup을 Weekly라는 Tag를 가지고 있는 Database Copy에 적용을 하게 됩니다.
RMAN> Delete Obsolete;
위 명령어를 사용하시면 현재의 Image Copy에 적용된 Incremental Backup을 재외한 나머지 Incremental Backup들이 Delete됩니다.
-Recovery
RMAN> switch database to copy;
문제가 발생하셨을 때 위 명령어를 사용하시면 모든 datafile의 pointer들은 image backup copy를 바라보게 됨으로 Restore의 시간을 절약할 수 있습니다.
4) Retention Policy에 따른 Syntax 변화
* 기본적으로 INCREMENTAL MERGE BACKUP & RECOVERY의 장점인 Recovery 시간을 극대화 하기 위해서는 Retention Policy를 redundancy 1(Default)로 설정하시는 것을 권장해드립니다.
하지만 User가 Backup & Recovery 계획을 변경하여 retention policy를 recovery window 또는 redundancy 1 이상으로 설정해 주시면 Obsolete한 Backupset을 Delete하는 부분과 Backupset을 적용시키는 부분을 수정해 주셔야합니다.
- Recovery Window of 2
Recovery Window를 2일로 설정해 놓으시면 Backup시에는 똑같은 Syntax를 사용하실 수 있으나 Recover copy of database 명령어는 아래와 같이 바뀌어야 합니다.
RMAN> BACKUP INCREMENTAL LEVEL 1
FOR RECOVER OF COPY
WITH TAG WEEKLY DATABASE;
RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY until time 'sysdate-2';
왜냐하면 retention policy에 마춰서 image copy도 2일전의 상태로 보관되어야하며 그에 따라서 2일동안의 Backupset들도 보관되어야하기 때문입니다. 만약 until time을 사용하지 않으시면 incremental backup들이 obsolete 상태로 안변하게 됩니다.
- Redundancy 2 이상
Redundancy 2이상으로 설정해 주시면 2개 이상의 Tag를 보관하는 효과로서 역시 예상대로 Obsolete로 안 변하는 현상이 발생됩니다.
DAY 1)
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
-위와 같이 실행하시면 한개의 Database Copy (Tag DAILY)가 생성됩니다.
DAY 2)
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
-위와 같이 실행하시면 한개의 Database Copy (Tag WEEKLY)와 한개의 Backupset (Tag DAILY)가 생성됩니다.
DAY 3)
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG MONTHLY DATABASE;
-위와 같이 실행하시면 한개의 Database Copy (Tag MONTHLY)와 두개의 Backupset (Tag DAILY, Tag WEEKLY)가 생성됩니다.
DAY 4)
RMAN> Delete Obsolete;
- 위와 같이 실행하시면 DAILY Tag와 관련된 부분이 Delete 됩니다. (최신 2개의 Tag관련 Backup만 보관)
RMAN> Delete Obsolete redundancy 1
- 위와 같이 실행하시면 DAYLY Tag와 WEEKLY Tag 관련된 부분이 Delete 됩니다. (Redundancy 1로 설정한 것과 똑같은 효과)
Reference:
Article-ID: Note 351455.1
Title: Oracle Suggested Strategy & Backup Retention
Article-ID: Note 303861.1
Title: Incrementally Updated Backup In 10G
글 수정:
hunlee

I would always include an archivelog backup:
... with tag 'fullbackup’ database plus archivelog delete all input;
And at the end:
delete obsolete noprompt;
That delete incrmental backups already applied to the basic image copies.
Your configuration allows only limited point in time recoveries. As soon as an incremental backup is applied to the image copies, you cannot go back in time. To change this you can add a 'until time' clause, for example:
recover
copy of database
with tag 'fullbackup until time 'sysdate-11';
This creates a recovery window of 10 days, only image copies older than 10 days will be changed.
Werner

Incremental Level n and Incremental Level n Cumulative

Hello,
Working on Oracle 10.2.0.3.0 on AIX 5.2. Taking backup through scripts using recovery catalog.
(Incremental level 0 cumulative)
RMAN> run {execute script cuml_level_0; }
executing script: cuml_level_0
Starting backup at 18-DEC-07
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=146 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=14 recid=13 stamp=641645002
channel ORA_DISK_1: starting piece 1 at 18-DEC-07
channel ORA_DISK_1: finished piece 1 at 18-DEC-07
piece handle=/dbbkup/06j3teel_1_1 tag=TAG20071218T104332 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
Finished backup at 18-DEC-07
Starting backup at 18-DEC-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental level 0 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=/dbprod5/BACKUPTEST/BACKUPTEST/system01.dbf
input datafile fno=00003 name=/dbprod5/BACKUPTEST/BACKUPTEST/sysaux01.dbf
input datafile fno=00005 name=/dbprod5/BACKUPTEST/BACKUPTEST/example01.dbf
input datafile fno=00002 name=/dbprod5/BACKUPTEST/BACKUPTEST/undotbs01.dbf
input datafile fno=00004 name=/dbprod5/BACKUPTEST/BACKUPTEST/users01.dbf
channel ORA_DISK_1: starting piece 1 at 18-DEC-07
channel ORA_DISK_1: finished piece 1 at 18-DEC-07
piece handle=/flash_recovery/BACKUPTEST/backupset/2007_12_18/o1_mf_nnnd0_TAG200712
18T104351_3pgqjy4b_.bkp tag=TAG20071218T104351 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
Finished backup at 18-DEC-07
Starting backup at 18-DEC-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=15 recid=14 stamp=641645163
channel ORA_DISK_1: starting piece 1 at 18-DEC-07
channel ORA_DISK_1: finished piece 1 at 18-DEC-07
piece handle=/dbbkup/08j3tejt_1_1 tag=TAG20071218T104620 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 18-DEC-07
Starting Control File and SPFILE Autobackup at 18-DEC-07
piece handle=/flash_recovery/BACKUPTEST/autobackup/2007_12_18/o1_mf_s_641645187_3p
gqoo2m_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 18-DEC-07(Incremental level 0 backup)
RMAN> run {execute script incr_level_0;}
executing script: incr_level_0
Starting backup at 18-DEC-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=14 recid=13 stamp=641645002
input archive log thread=1 sequence=15 recid=14 stamp=641645163
input archive log thread=1 sequence=16 recid=15 stamp=641645676
channel ORA_DISK_1: starting piece 1 at 18-DEC-07
channel ORA_DISK_1: finished piece 1 at 18-DEC-07
piece handle=/dbbkup/0aj3tf3h_1_1 tag=TAG20071218T105440 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:08
Finished backup at 18-DEC-07
Starting backup at 18-DEC-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental level 0 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=/dbprod5/BACKUPTEST/BACKUPTEST/system01.dbf
input datafile fno=00003 name=/dbprod5/BACKUPTEST/BACKUPTEST/sysaux01.dbf
input datafile fno=00005 name=/dbprod5/BACKUPTEST/BACKUPTEST/example01.dbf
input datafile fno=00002 name=/dbprod5/BACKUPTEST/BACKUPTEST/undotbs01.dbf
input datafile fno=00004 name=/dbprod5/BACKUPTEST/BACKUPTEST/users01.dbf
channel ORA_DISK_1: starting piece 1 at 18-DEC-07
channel ORA_DISK_1: finished piece 1 at 18-DEC-07
piece handle=/flash_recovery/BACKUPTEST/backupset/2007_12_18/o1_mf_nnnd0_TAG200712
18T105449_3pgr5d2l_.bkp tag=TAG20071218T105449 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:58
Finished backup at 18-DEC-07
Starting backup at 18-DEC-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=17 recid=16 stamp=641645812
channel ORA_DISK_1: starting piece 1 at 18-DEC-07
channel ORA_DISK_1: finished piece 1 at 18-DEC-07
piece handle=/dbbkup/0cj3tf7r_1_1 tag=TAG20071218T105659 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 18-DEC-07
Starting Control File and SPFILE Autobackup at 18-DEC-07
piece handle=/flash_recovery/BACKUPTEST/autobackup/2007_12_18/o1_mf_s_641645826_3p
gr9m7x_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 18-DEC-07There are certain differences. Any comments.
Thank you,
Adith

I think you are taking backup with backup plus archive log,archive log backup does the
following steps chronologically
1. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.
2. Runs BACKUP ARCHIVELOG ALL. Note that if backup
   optimization is enabled, then RMAN skips logs that it
   has already backed up to the specified device.
3. Backs up the rest of the files specified in BACKUP
   command.
4. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command again
   cuase right now it will Backs up any remaining
   archived logsgenerated during the backup.
SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     83
Next log sequence to archive   85
Current log sequence           85
You can see next log sequence to be archived is 85
RMAN> backup database plus archivelog
2> ;
Starting backup at 26-DEC-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=85 recid=89 stamp=642354039
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
F_ANNNN_TAG20071226T154039_3Q4CX955_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 26-DEC-07
Starting backup at 26-DEC-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_NNNDF_TAG20071226T154044_3Q4CXG9X_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:58
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_NCSNF_TAG20071226T154044_3Q4CZ8GR_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 26-DEC-07
Starting backup at 26-DEC-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=86 recid=90 stamp=642354108
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_ANNNN_TAG20071226T154148_3Q4CZFVO_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 26-DEC-07
SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     85
Next log sequence to archive   87
Current log sequence           87
RMAN> backup database plus archivelog
2> ;
Starting backup at 26-DEC-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=85 recid=89 stamp=642354039
input archive log thread=1 sequence=86 recid=90 stamp=642354108
input archive log thread=1 sequence=87 recid=91 stamp=642354774
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
F_ANNNN_TAG20071226T155255_3Q4DNBSM_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 26-DEC-07
Starting backup at 26-DEC-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
F_NNNDF_TAG20071226T155302_3Q4DNJ28_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
F_NCSNF_TAG20071226T155302_3Q4DOYL6_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 26-DEC-07
Starting backup at 26-DEC-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=88 recid=92 stamp=642354835
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_M
F_ANNNN_TAG20071226T155355_3Q4DP4SQ_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 26-DEC-07
RMAN>
RMAN> show backup optimization
2> ;
RMAN configuration parameters are:
CONFIGURE BACKUP OPTIMIZATION OFF; # default
RMAN> configure backup optimization on
2> ;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     87
Next log sequence to archive   89
Current log sequence           89
RMAN> backup database plus archivelog
2> ;
Starting backup at 26-DEC-07
current log archived
using channel ORA_DISK_1
skipping archive log file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\ARCHIVELOG\2007_12_26\O1_MF_1_85_3Q4CX5XS_.ARC; already backed up 2 time(s)
skipping archive log file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\ARCHIVELOG\2007_12_26\O1_MF_1_86_3Q4CZCZ1_.ARC; already backed up 2 time(s)
skipping archive log file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\ARCHIVELOG\2007_12_26\O1_MF_1_87_3Q4DN5MZ_.ARC; already backed up 1 time(s)
skipping archive log file C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\ARCHIVELOG\2007_12_26\O1_MF_1_88_3Q4DP351_.ARC; already backed up 1 time(s)
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=89 recid=93 stamp=642355243
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_ANNNN_TAG20071226T160049_3Q4F3GYM_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:09
Finished backup at 26-DEC-07
Starting backup at 26-DEC-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE10G\ORACLE\ORADATA\ORCL1\ORCL1\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_NNNDF_TAG20071226T160111_3Q4F3ZXF_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_NCSNF_TAG20071226T160111_3Q4F69NO_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:06
Finished backup at 26-DEC-07
Starting backup at 26-DEC-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=90 recid=94 stamp=642355360
channel ORA_DISK_1: starting piece 1 at 26-DEC-07
channel ORA_DISK_1: finished piece 1 at 26-DEC-07
piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\ORCL1\ORCL1\BACKUPSET\2007_12_26\O1_MF_ANNNN_TAG20071226T160240_3Q4F6L09_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 26-DEC-07
RMAN>Khurram

Rman incremental level 1 merge with level 0

from my reading of the rman backup document, it seems the merger incremental level 1to level 0 for recover only apply to merge with image copy, not the backupset. Is that true? However, such backup scheme will create a huge backup image copy, almost fill up my assigned backup depository directory. Is the following script works as merging with level 0 ?
{backup as compressed backupset incremental level 1 for recover of tag 'bk$LEVEL0' database;}
It run without error and created a very small incr file size, but not sure it has the same meaning of "for recover of copy" as in other document.

If that is true, why we need to create an incremental level 0 backupset as the base for recover? I have one compressed backupset level 0 at beginning, then incremental level 1 for recover. with the "recover of copy with tag", it seems to create a redundant full backup. Also Iam confused, The "recover of copy with tag" is actually an image copy of the full backupset or the image copy of the original database.
My script as for full backup at beginning
{ backup as compressed backupset incremental level 0 cumulative device type disk tag 'Baanbk$LEVEL0' database; }
then incremental
{ backup as compressed backupset incremental level 1 for recover of tag 'Baanbk$LEVEL0' database; }
Should I modify the full backupset script?

Differential Incremental Backup or Incrementally Updated Backup?

DB Version:11g
DB Size:450Gb
DB type: OLTP (storing retail warehouse transactions)
To implement a proper backup strategy, we are currently weighing the Pros and Cons of Differential Incremental Backup and Incrementally Updated Backup.
I understand that , for Incrementally Updated Backup , the level 0 backup must be stored in FRA. We don't want to configure FRA as of now.
Which backup strategy would you choose for a similair environment?

I don't think that 11g RMAN level 0 backup need to use FRA: can you provide us the link to Oracle doc ?
When designing your backup strategy you need to define:
RTO: recovery time objective
RPO: recovery point objective.
See http://download.oracle.com/docs/cd/B19306_01/server.102/b14210/hadesign.htm
To meet a low RTO objective, you may need to use incrementally updated backup because it should be faster to recover from incrementally updated backup compared to differential incremental backup.

Incremental level backup

Similar Messages

Maybe you are looking for