Level 0 backup

Hi,
Can some body please explain what is Level 0, Level 1, Level 2, Level 3 backups ?
Thanks

You really only need to be concerned with Level 0 & Level 1 for 10g. Check Multilevel Incremental Backups.
In releases prior to 10g, you may want to review Multilevel Incremental Backups.

Similar Messages

Full (Level 0) backup to local/NFS disk

I am new to SAP's BR*Tools, and need advice in configuring it to use RMAN.
1. My backups are to be written to a staging area on our SAN.
2. What specific parameters do I need to configure in the initSID.sap file to achive Full (Level 0) backup to local/NFS disk - preferably using RMAN?
3. I have successfully performed a Full (Level 0) backup without RMAN to local disk. Also, I have successfully done an incremental (Level 1) backup using BRTools with RMAN. I want to get BRTools + RMAN based Full (Level 0) backup to local/NFS disk.
--VJ

You need to set the values for the following.
tape_address
archive_copy_dir
tape_size =
backup_mode =
backup_dev_type =
backup_type =
backup_root_dir
volume_archive
volume_backup
tape_pos_cmd
Cheers
Shaji

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.

How to config the levels of backup for partioned cache?

hi all,
As coherence's document says, "Partitioned caches can be configured with as many levels of backup as desired, or zero if desired. Most installations use one backup copy (two copies total). ", could you pls. tell how? Great thanks!
thanks,
michael

Hi Michael,
there are several reasons on why it is usually recommended to have at least 3 nodes:
1. When a single node fails, Coherence after a short time (after the rebalance of the cluster completes) gets itself into a state which again is capable of surviving a single error (data is still backed up at least once). If there is only two nodes, and only one of them remains, this is obviously not possible.
2. Some of Coherence's protocols for determining what should happen after a cluster node becomes inaccessible behave differently when there are at least 3 nodes (majority wins), whereas when 2 nodes can't communicate with each other, none of them can determine which is faulty.
As for backup count:
Total memory consumption without overhead in the cluster is roughly (1+backupcount)*dataset-size + 1 * index-size.
I believe backup count larger than the number of nodes does not have any additional effect, each node will store only a single copy of the data.
BR,
Robert

Full Backups, Level 0 Backups, and Archived Logs

We have an active Oracle server and a standby Oracle server. We keep the standby database up to date with a cron script. The script tells the active database to do 'alter system switch logfile;'. We then rsync the archived logs to our standby server and have rman apply them.
This works everyday except Monday (of course!) and it only recently started failing on Mondays. The only change was that our Sunday backups used to be 'Full' backups but are now 'level 0' backups. Ever since that change, the first attempt to apply the archived logs to the standby server after the level 0 is taken on the active server gives us something like this:
ORA-00308: cannot open archived log
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.arc'
ORA-27037: unable to obtain file status
Of course, the file is not there and doesn't exist on the active server either. And of course, the nightly level1 backups fo not give us problems applying archived logs to the standby database the rest of the week.
The only way I know to recover from this is to apply the level 0 backup or take a new level 0 and apply it. After that, all subsequent archive logs just work. Any idea why changing from Full to Level 0 would break this? The Oracle docs insist that a Level 0 is identical to a Full except that level 1s can reference them as parents. This simply cannot be true based on what I'm seeing! I really want to keep the level 0 backups in play if possible. Level 1 cumulatives wont be useful without them.

Here are the RMAN settings:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/102/dbs/snapcf_ORCL.f'; # default
I'm not sure how changing ARCHIVELOG BACKUP COPIES would help. Can you give me a little more information about how that setting comes into play in this situation?
I actually don't want an archive deletion policy here. We have this done in script three days after the needed archive logs have been applied. Is it possible that the we're deleting archivelogs too soon? Would we ever need to reach back in time to previously applied archive logs to apply new ones?
The %u does resolve, but this message isn't showing it. Here is that same log entry plus a few previous entries that show it does resolve.
ORA-00279: change 1284618956 generated at 04/13/2012 15:30:05 needed for thread
1
ORA-00289: suggestion :
/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60518_%u_.arc
ORA-00280: change 1284618956 for thread 1 is in sequence #60518
ORA-00278: log file
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_13/o1_mf_1_60517_7rjzox
0l_.arc' no longer needed for this recovery
ORA-00279: change 1284618958 generated at 04/13/2012 15:30:05 needed for thread
1
ORA-00289: suggestion :
/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.arc
ORA-00280: change 1284618958 for thread 1 is in sequence #60519
ORA-00278: log file
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_13/o1_mf_1_60518_7rjzox
0x_.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.ar
c'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

RMAN Level 1 backup affects

O/S: Windows Server 2003
DB: Oracle 11gR2
We are in the midst of a production load process. Noticed that the level 2 backup from last night failed. Want to take a level 1 backup as soon as possible.
How will a level 1 backup affect a live system if it would done 'now' -- i.e., in the midst of a production load process?
Cheers!

The RMAN backup would not affect anything you do directly (assuming it is a hot backup). It will, however, consume quite a bit of disk and network IO, which in turn could slow most DB sessions/processes that require disk/network IO.
Iordan Iotzov
http://iiotzov.wordpress.com/

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

Level 0 backup coming up as DB INCR in v$rman_backup_job_details view

Version ===> 10.2.0.4.0
I've run a LEVEL 0 backup for my DB for the first time. But when i query
SQL> select status, input_type From v$rman_backup_job_details order by start_Time descIt is showing
STATUS INPUT_TYPE
COMPLETED DB INCRShouldn't input_type come up as
DB FULLwhen i do a LEVEL 0 backup?

Does file name format actually matter?
I had clearly given
level 0in my command, which is
run
backup as compressed backupset incremental level 0 database tag 'full' plus archivelog delete all input;
}

RMAN level 0 backup

Is an RMAN level 0 backup consistent (database in MOUNT code), or inconsistent (database is open)?
-Chuck

PLease copy here the entire error stack. RMAN never gives just a sngle line error message. Its a series of error messages and looking all of them would be helpful to say something useful.
As Nayab asked, please post the db version as well.
HTH
Aman....

RMAN Level 0 Backup ORA-27072: File I/O error ... Input/output error

Hi, All -
I am receiving the following error messages while running a level 0 backup. Please assist!
====================================================================================================
RMAN-03009: failure of backup command on d1 channel at 11/17/2008 01:08:34
ORA-19502: write error on file "/NEW_backups/backups/admin/CCPROD/bkups/CCPROD.5313.1.670986008.DB", blockno 82945 (blocksize=8192)
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
RMAN-03009: failure of backup command on d2 channel at 11/17/2008 01:08:34
ORA-19502: write error on file "/NEW_backups/backups/admin/CCPROD/bkups/CCPROD.5314.1.670986008.DB", blockno 84609 (blocksize=8192)
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 84609
Additional information: -1
channel d2 disabled, job failed on it will be run on another channel
released channel: d1
released channel: d2
released channel: d3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on d3 channel at 11/17/2008 01:08:34
ORA-19502: write error on file "/NEW_backups/backups/admin/CCPROD/bkups/CCPROD.5315.1.670986008.DB", blockno 98433 (blocksize=8192)
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 98433
Additional information: -1

Since it is a <b>write</b> error, I'd look at permissions on the target directory, and available disk space on the target file system.

RMAN level 0 backup with bigfile tablespaces

We noticed that our rman backup process for PROD database is not working properly.
PROD is a 8 TB size database having two bigfile tablespaces each having more than 2 TB datafile.
PROD is a 11gR1 (11.1.0.7) RAC database with ASM storage.
We are taking weekly incremental level 0 backup for entire database and level 1 backup every day.
As per v$session_longops, the approx completion time for the two tablespaces is 5 days.
We can use "SECTION SIZE" parameter to take rman backup for bigfile tablespaces and exclude them from the level 0 backup.
However, in this case our level 0 backup wont include the two bigfile tablespaces and the daily level 1 backup will not include them.
Will you pls advise us on how to take backup in this scenario.
we have only 4TB of LUN allocated for backup and have to keep 7 days of backup on disk.
Thanks in advance !
DR

We can use "SECTION SIZE" parameter to take rman backup for bigfile tablespaces and exclude them from the level 0 backup.
How do you think that the backup will be useful if you exclude some files from level 0 or base backup? You will find difficulties or you can't restore the database in case of disaster.
Yes you can use section size parameter for paralleled big file tablespace backup.
Check below for explanation and example.
Backing Up the Database: Advanced Topics
http://www.oracle-base.com/articles/11g/rman-enhancements-11gr1.php#multisection_backups
You can use the below note for your case which will be of help.
Reducing RMAN backup time for unevenly sized tablespaces &laquo; Oracle DBA &#8211; A lifelong learning experie…
Thank you!!

RMAN level 2 backup in Oracle 10gR2

Does RMAN in 10gR2 can only do level 0 and level 1 incremental backups now there is nothing called level 2 anymore, at least that's what the doc says.
But I took level 0 after the upgrade on sunday and today morning the RMAN script as per schedule took a level 2 backup without any error. Does this mean RMAN still supports level 2 backups.
Is my level 2 backup reliable or do I have to take another Level 0 just to be on the safe side, please advice.
-Ramki
---Duplicate post, I didn't realize that there was an exclusive RMAN group and I posted in the database general group----------

The level 2 were used until the version 9i. In the version 10g is only used options 0 and 1, as documentation.
The option 0 is used for full backups (base line), and option 1 is used for incremental backups [differential (default) or cumulative].
But the level 2 is used for compatibility with old versions and it doesn't have to generate errors.

Restore from level 0 backup

when i restore the db. Rman is looking for the backup piece which was not part of level 0 backup.
ORA-19870: error reading backup piece /prd/backup/gbl/PS/l0/PS_qlm6nudf_1_1
ORA-19505: failed to identify file "/prd/backup/gbl/PS/l0/PS_qlm6nudf_1_1"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
when i checked the log file for level 0 backup this backup piece was not created during the level 0.
Can someone help me.

BS Key Type LV Size Device Type Elapsed Time Completion Time
916495 Full 16.27M DISK 00:00:00 08-MAR-11
BP Key: 916500 Status: AVAILABLE Compressed: NO Tag: TAG20110308T032426
Piece Name: /usr/oracle5/product/102/db_2/dbs/c-4151495469-20110308-01
Control File Included: Ckp SCN: 7881567856 Ckp time: 08-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
916496 Full 16.23M DISK 00:00:00 08-MAR-11
BP Key: 916501 Status: AVAILABLE Compressed: NO Tag: TAG20110308T043310
Piece Name: /usr/oracle5/product/102/db_2/dbs/c-4151495469-20110308-02
Control File Included: Ckp SCN: 7881694311 Ckp time: 08-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
916540 Full 16.27M DISK 00:00:02 08-MAR-11
BP Key: 916542 Status: AVAILABLE Compressed: NO Tag: TAG20110308T194211
Piece Name: /usr/oracle5/product/102/db_2/dbs/c-4151495469-20110308-03
Control File Included: Ckp SCN: 7891125389 Ckp time: 08-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
916589 Incr 0 2.10G DISK 00:27:22 08-MAR-11
BP Key: 916604 Status: AVAILABLE Compressed: YES Tag: TAG20110308T202933
Piece Name: /prd/psftp/backup/gbl/PSFTPRD5/l0/PSFTPRD5_qqm6o33m_1_1
Control File Included: Ckp SCN: 7891368730 Ckp time: 08-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
916811 Full 16.27M DISK 00:00:01 08-MAR-11
BP Key: 916828 Status: AVAILABLE Compressed: NO Tag: TAG20110308T230712
Piece Name: /usr/oracle5/product/102/db_2/dbs/c-4151495469-20110308-04
Control File Included: Ckp SCN: 7891377652 Ckp time: 08-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
916894 Incr 0 2.10G DISK 00:42:40 09-MAR-11
BP Key: 916909 Status: AVAILABLE Compressed: YES Tag: TAG20110308T231614
Piece Name: /prd/psftp/backup/gbl/PSFTPRD5/l0/PSFTPRD5_r8m6ob9h_1_1
Control File Included: Ckp SCN: 7891385135 Ckp time: 09-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
917116 Full 16.27M DISK 00:00:02 09-MAR-11
BP Key: 917133 Status: AVAILABLE Compressed: NO Tag: TAG20110309T015832
Piece Name: /usr/oracle5/product/102/db_2/dbs/c-4151495469-20110309-00
Control File Included: Ckp SCN: 7891521048 Ckp time: 09-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
917165 Full 16.23M DISK 00:00:01 09-MAR-11
BP Key: 917168 Status: AVAILABLE Compressed: NO Tag: TAG20110309T015853
Piece Name: /prd/psftp/backup/gbl/PSFTPRD5/l0/PSFTPRD5_rhm6ohmt_1_1
Control File Included: Ckp SCN: 7891521353 Ckp time: 09-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
917212 Full 16.27M DISK 00:00:01 09-MAR-11
BP Key: 917215 Status: AVAILABLE Compressed: NO Tag: TAG20110309T020141
Piece Name: /usr/oracle5/product/102/db_2/dbs/c-4151495469-20110309-01
Control File Included: Ckp SCN: 7891523572 Ckp time: 09-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
918243 Full 16.27M DISK 00:00:02 09-MAR-11
BP Key: 918246 Status: AVAILABLE Compressed: NO Tag: TAG20110309T101033
Piece Name: /usr/oracle5/product/102/db_2/dbs/c-4151495469-20110309-02
Control File Included: Ckp SCN: 7896226983 Ckp time: 09-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
918291 Incr 0 6.04G DISK 02:03:01 09-MAR-11
BP Key: 918306 Status: AVAILABLE Compressed: YES Tag: TAG20110309T195035
Piece Name: /prd/psftp/backup/gbl/PSFTPRD5/l0/PSFTPRD5_rqm6qgge_1_1
Control File Included: Ckp SCN: 7901246144 Ckp time: 09-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
918521 Full 16.27M DISK 00:00:01 09-MAR-11
BP Key: 918538 Status: AVAILABLE Compressed: NO Tag: TAG20110309T231653
Piece Name: /usr/oracle5/product/102/db_2/dbs/c-4151495469-20110309-03
Control File Included: Ckp SCN: 7901622494 Ckp time: 09-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
918570 Full 16.23M DISK 00:00:01 09-MAR-11
BP Key: 918573 Status: AVAILABLE Compressed: NO Tag: TAG20110309T231726
Piece Name: /prd/psftp/backup/gbl/PSFTPRD5/l0/PSFTPRD5_s6m6qsk6_1_1
Control File Included: Ckp SCN: 7901622869 Ckp time: 09-MAR-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
918737 Full 16.27M DISK 00:00:00 10-MAR-11
BP Key: 918762 Status: AVAILABLE Compressed: NO Tag: TAG20110310T001017
Piece Name: /usr/oracle5/product/102/db_2/dbs/c-4151495469-20110310-00
Control File Included: Ckp SCN: 7901666457 Ckp time: 10-MAR-11

Level 0 backup

Similar Messages

Maybe you are looking for