Rman backup level 0 doubt

Hi guys,
I have a doubt regarding Rman.
When I do a Level 0 backup (backup incremental level 0 database) it put in the file the empty blocks or
it saves only the used blocks in my database ?
I know the incremental backups (level 1 and 2) gets only the new blocks.
and I would like to know if rman files can be compressed during the process.
Thanks,
Felipe

Which is the version of its database?
If he will be 10g, sees the documentations.
RMAN Incremental Backups:
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#BRBSC133
Binary Compression of Backup Sets:
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#RCMRF107

Similar Messages

How to identify rman backup level?

Hi,
I am using rman catalog for rman backup. how to identify rman backup level from catalog.
Thanks,

By doing the obvious and consulting the online documentation at http://tahiti.oracle.com
You will notice the list backup command output has a level column and this is also present in rc_backupset and/or rc_backuppiece.
Sybrand Bakker
Senior Oracle DBA

Rman backup level 0 and then cumulative

Hi All,
I have a system that had a level 0 backup done last year and since then the following has taken place
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA\$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA\$OEM_LEVEL_0' database;
In the event of recovery, how will RMAN handle this. I am sure that the orignal level 0 is not now on disk.
best regards
Alan

This is an incrementally updated backup. The first time the scripts runs, recover copy ... does nothing and backup incremental level 1 ... creates image copies (not a backupset) of the datafiles. That can be seen as level 0 base backup and you should still have these image copies,
The second time, recover copy ... again does anything (because no incremental backup exists at this time), but backup incremental level 1 ... now creates its first incremental backup.
From now on (third,fourth and so on time) the process does always the same:
recover copy ... applies the incremental backup previously created to the image copies,
backup incremental level 1 ... performs the next incremental backup.
That seems to be the 'Oracle suggested' backup script generated by EM. Archivelogs should be backed up, too.
Werner

Oracle 9i Rman backup script !!

hi,
We are taking rman backup level 0. While making this backup the backup size is very big i.e. let's suppose if DB size is some 100GB then backup size would be somewhere around 60-70 GB. I need to know , does anybody having any script which compresses the backup sets after they get generated during the backup i.e. lets suppose 10 backup sets get generated, what I need to know is when RMAN is generating lets say 2 backup can we compress 1st backupset and so on like when 3rd backup set is getting generated we compress the 2nd backupset and so on till 10th backup set.
Let me know if anybody needs more information on this...I know it's a typical requirement :o))

hello Hamir,
what operating system are you working on
after the backup you could call a routine in unix to gzip file_name
or in windows to use winzip.
however in 9i to restore the database you would then need to unzip the files first.
what possibility do you have to upgrade to 10g, this has the ability to automatically compress the backup set from within RMAN.
rgds
alan

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

Rman backup full then level 0 and level 1 Weekly

Please share your thoughts of backups.
Friday -> Take a full rman backup
Saturday -> Take a level 0 rman backup -> If recovery needed restore full and apply level 0 ?
Sunday -> Take a level 1 rman backup -> If recovery needed restore full and apply incremental 1 ?
Monday -> Take a level 2 rman backup -> If recover needed restore full and apply incremental 1 ?
Tuesday -> Take a level 1 rman backup -> If recover needed restore full and apply incremental 2 ?
Wednesday -> Take a level 2 rman backup -> If recovery needed restore full and apply incremental 1 ?
Thursday -> Take a level 1 rman backup -> If recovery need restore full and apply incremental 2 ?
Thanks

Please note that Full and level 0 backs are same...
Sunday -> Take a level 0 rman backup
Monday -> Take a level 1 rman backup
Tuesday -> Take a level 1 rman backup
Wednesday -> Take a level 2 rman backup
Thursday -> Take a level 1 rman backup
Friday-> Take a level 1 rman backup
Saturday -> Take a level 1 rman backup
Taking level 2 in the middle of the week, so that in case of any recovery you need ao apply changes since the last level 0, 1 or 2

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 0 level backup failed while releasing channels at end.

In RMAN 0 level backup, when it's about to finish, reports an error as releasing channels. It backed up about 98% datafiles.
Is this backup is usable. As we can not affort to take backup again as it's a big terabyte databse.
Please suggest.
Thanks in advance.
Aj.

Do you have release stmts in the script
From 9i onwards oracle Release the channels automatically upon backing up, so you can remove the release channel lines if you have and try it

RMAN - Schema level backup ??

We have a production system in which one schema is getting bigger day by day(40GB).
We want this schema in our development instnaces once in a week atleast.As export for this is taking time we want to go for rman setup for faster process.
1)Will rman backup speed up the process ?
2)Is there any way we can take the rman backup for a schema and not for the whole database.
3)If yes what are the steps for this setup and steps to use this in the develpment database?
Production is on hp-ux and dev on windows.

1)Will rman backup speed up the process ?It depends. If they will be backuped only 40Gb, will be relatively fast.
2)Is there any way we can take the rman backup for a schema and not for the whole database.Schema No, but if the schema objects is in a single tablespace one, can be make the tablespace backup
3)If yes what are the steps for this setup and steps to use this in the develpment database?Follow the steps to backup the tablespace.

RMAN Backup Doubt...

Hi all,
I have set up RMAN Backup in my system which takes daily full backup as it is Standara Edition 9i.
My db size is 35GB.
As is see in the backup folder that there are three backup files each of 35GB.
I don't know why there are three peices.
I have given my RMAN Configuration below:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'H:\OCTO backup\%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT 'H:\OCTO backup\OCTO_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'H:\OCTO backup\SNCFOCTO.ORA';
Can Anybody explain me how come it take Three 35GB files. and why.
Thanks in Advance....
Elango

Folks,
I have Pasted the LIST BACKUP; output below.
Spooling started in log file: C:\Documents and Settings\dbProfessionals_PM\Desktop\dbpros\listbackp.txt
Recovery Manager: Release 9.2.0.7.0 - Production
RMAN>
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
4211 Full 2M DISK 00:00:02 19-SEP-10
BP Key: 4211 Status: EXPIRED Tag:
Piece Name: H:\RMAN BACKUP\C-3843188258-20100919-00
SPFILE Included: Modification time: 14-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
4212 Full 33G DISK 02:55:10 20-SEP-10
BP Key: 4212 Status: AVAILABLE Tag: TAG20100919T220053
Piece Name: H:\RMAN BACKUP\AARCWIVSAP10238_DISPATCH_4JLOAM4M_1_1
List of Datafiles in backup set 4212
File LV Type Ckp SCN Ckp Time Name
1 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\SYSTEM01.DBF
2 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS01.DBF
3 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DRSYS01.DBF
4 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\INDX01.DBF
5 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\TOOLS01.DBF
6 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\USERS01.DBF
7 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\XDB01.DBF
8 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0101.DBF
9 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\CIMIDX0101.DBF
10 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0101.DBF
11 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\DISIDX0101.DBF
12 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DRVDATA0101.DBF
13 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\DRVIDX0101.DBF
14 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0101.DBF
15 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0101.DBF
16 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\FINANCEDATA0101.DBF
17 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0101.DBF
18 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\TADBADATA0101.DBF
19 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0101.DBF
20 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0101.DBF
21 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\ARCHIDX0101.DBF
22 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0101.DBF
23 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHSTAG0101.DBF
24 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\DOMIDX0101.DBF
25 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\STAGIDX0101.DBF
26 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\USERS02.DBF
27 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0102.DBF
28 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0102.DBF
29 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0102.DBF
30 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\XDB02.DBF
31 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\FINNANCEDATA102.DBF
32 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0102.DBF
33 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\CIMDX0102.DBF
34 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0102.DBF
35 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0102.DBF
36 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS02.DBF
37 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0102.DBF
38 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0103.DBF
39 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0102.DBF
40 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ASHLEYDATA0101.DBF
41 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0101.DBF
42 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0102.DBF
43 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\ODM01.DBF
44 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\SPADATA0101.DBF
45 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\SPADATA0102.DBF
46 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\COMDATA0101.DBF
47 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0104.DBF
48 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\JOURNALSDATA0101.DBF
49 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\SQLORACLEDATA0101.DBF
50 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DATAWHSEDATA0101.DBF
51 Full 6665107783 19-SEP-10 J:\ORADATA\DISPATCH\DB2ORACLE_01.DBF
52 Full 6665107783 19-SEP-10 F:\ORADATA\DISPATCH\DISDATA0105.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
4213 Full 2M DISK 00:00:01 20-SEP-10
BP Key: 4213 Status: AVAILABLE Tag:
Piece Name: H:\RMAN BACKUP\C-3843188258-20100920-00
SPFILE Included: Modification time: 14-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
4214 Full 33G DISK 01:30:10 20-SEP-10
BP Key: 4214 Status: AVAILABLE Tag: TAG20100920T101831
Piece Name: H:\RMAN BACKUP\AARCWIVSAP10238_DISPATCH_4MLOC1BN_1_1
List of Datafiles in backup set 4214
File LV Type Ckp SCN Ckp Time Name
1 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\SYSTEM01.DBF
2 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS01.DBF
3 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DRSYS01.DBF
4 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\INDX01.DBF
5 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\TOOLS01.DBF
6 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\USERS01.DBF
7 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\XDB01.DBF
8 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0101.DBF
9 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\CIMIDX0101.DBF
10 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0101.DBF
11 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\DISIDX0101.DBF
12 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DRVDATA0101.DBF
13 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\DRVIDX0101.DBF
14 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0101.DBF
15 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0101.DBF
16 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\FINANCEDATA0101.DBF
17 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0101.DBF
18 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\TADBADATA0101.DBF
19 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0101.DBF
20 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0101.DBF
21 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\ARCHIDX0101.DBF
22 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0101.DBF
23 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHSTAG0101.DBF
24 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\DOMIDX0101.DBF
25 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\STAGIDX0101.DBF
26 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\USERS02.DBF
27 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0102.DBF
28 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0102.DBF
29 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0102.DBF
30 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\XDB02.DBF
31 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\FINNANCEDATA102.DBF
32 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0102.DBF
33 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\CIMDX0102.DBF
34 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0102.DBF
35 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0102.DBF
36 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS02.DBF
37 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0102.DBF
38 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0103.DBF
39 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0102.DBF
40 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ASHLEYDATA0101.DBF
41 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0101.DBF
42 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0102.DBF
43 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\ODM01.DBF
44 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\SPADATA0101.DBF
45 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\SPADATA0102.DBF
46 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\COMDATA0101.DBF
47 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0104.DBF
48 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\JOURNALSDATA0101.DBF
49 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\SQLORACLEDATA0101.DBF
50 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DATAWHSEDATA0101.DBF
51 Full 6665136736 20-SEP-10 J:\ORADATA\DISPATCH\DB2ORACLE_01.DBF
52 Full 6665136736 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0105.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
4215 Full 2M DISK 00:00:01 20-SEP-10
BP Key: 4215 Status: AVAILABLE Tag:
Piece Name: H:\RMAN BACKUP\C-3843188258-20100920-01
SPFILE Included: Modification time: 14-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
4216 Full 33G DISK 02:33:19 21-SEP-10
BP Key: 4216 Status: AVAILABLE Tag: TAG20100920T220137
Piece Name: H:\RMAN BACKUP\AARCWIVSAP10238_DISPATCH_4OLODAI1_1_1
List of Datafiles in backup set 4216
File LV Type Ckp SCN Ckp Time Name
1 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\SYSTEM01.DBF
2 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS01.DBF
3 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DRSYS01.DBF
4 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\INDX01.DBF
5 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\TOOLS01.DBF
6 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\USERS01.DBF
7 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\XDB01.DBF
8 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0101.DBF
9 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\CIMIDX0101.DBF
10 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0101.DBF
11 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\DISIDX0101.DBF
12 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DRVDATA0101.DBF
13 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\DRVIDX0101.DBF
14 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0101.DBF
15 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0101.DBF
16 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\FINANCEDATA0101.DBF
17 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0101.DBF
18 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\TADBADATA0101.DBF
19 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0101.DBF
20 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0101.DBF
21 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\ARCHIDX0101.DBF
22 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0101.DBF
23 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHSTAG0101.DBF
24 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\DOMIDX0101.DBF
25 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\STAGIDX0101.DBF
26 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\USERS02.DBF
27 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDATA0102.DBF
28 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ARCHDOM0102.DBF
29 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\FINANCEIDX0102.DBF
30 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\XDB02.DBF
31 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\FINNANCEDATA102.DBF
32 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0102.DBF
33 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\CIMDX0102.DBF
34 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\EDIIDX0102.DBF
35 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\EDIDATA0102.DBF
36 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\UNDOTBS02.DBF
37 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\TATEMPDATA0102.DBF
38 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0103.DBF
39 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\CIMDATA0102.DBF
40 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ASHLEYDATA0101.DBF
41 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0101.DBF
42 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\LCOMDATA0102.DBF
43 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\ODM01.DBF
44 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\SPADATA0101.DBF
45 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\SPADATA0102.DBF
46 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\COMDATA0101.DBF
47 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0104.DBF
48 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\JOURNALSDATA0101.DBF
49 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\SQLORACLEDATA0101.DBF
50 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DATAWHSEDATA0101.DBF
51 Full 6665164293 20-SEP-10 J:\ORADATA\DISPATCH\DB2ORACLE_01.DBF
52 Full 6665164293 20-SEP-10 F:\ORADATA\DISPATCH\DISDATA0105.DBF
BS Key Type LV Size Device Type Elapsed Time Completion Time
4217 Full 2M DISK 00:00:01 21-SEP-10
BP Key: 4217 Status: AVAILABLE Tag:
Piece Name: H:\RMAN BACKUP\C-3843188258-20100921-00
SPFILE Included: Modification time: 14-SEP-10
RMAN>
Elango
Elango

RMAN Backup policy

Hi,
I have few basic doubts in RMAN backup policy
1 . Is that possible to set Retention policy to recovery window in minutes??
2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
Regards,
007

1 What does the documentation of your unknown version of RMAN say? Does it states minutes are possible? If so, why are you asking rhetorical questions? (questions for which you already know the answer)
2 Rman only considers level 0 backups to determine whether a backup is obsolete, as you can't restore from an incremental backup.
Setting up a backup scheme for 4 days with a recovery window of 3 days wouldn't make any backup obsolete.
Sybrand Bakker
Senior Oracle DBA

RMAN Backup from windows to Linux

Hi,
I am having Windows 2003 server Oracle 10.2
and I have RHEL5 and Oracle 10.2
I have taken a RMAN Oracle Database Backup from windows..
I have installed oracle software on RHEL5 and now i need to restore this backup to the Linux
it is possible to restore it? if possible can any one let me know the process?
Regards,
Vijayaraghavan K

I have another doubt
I took RMAN full DB Backup - it comes around 2.5 G (performed on time 9.00 A.M morning)
When i perform differential incremental backup it comes around 2.6 G (performed on time 9.45 A.M )
Why it is coming like this.. The backup should happen only for the changed blocks alone?? i.e it should come around 10 Mb or 20 Mb?? Why is like this? or my understanding of differential backup is wrong?
I issued the below commands for Full DB Backup and Incremental Backup...
FULL DB backup at 9.00 A.M
RMAN> BACKUP INCREMENTAL LEVEL 0 DATABASE;
Differentail Backup a 9.45 A.M
RMAN> BACKUP INCREMENTAL LEVEL 1 DATABASE;
Regards,
Vijayaraghavan K

Setting up new dbname/sid while creating oracle db from rman backups in 11g

Hi all,
I have rman backups and need to create another database from rman backups with different name... but it is unsuccessful..
created instance with new db...
running create new db connecting rman auxiliary sys/password@newdb
run {
SET NEWNAME FOR DATAFILE 1 TO 'F:\app\HOME\oradata\clonedb1\SYSTEM01.DBF';
SET NEWNAME FOR DATAFILE 2 TO 'F:\app\HOME\oradata\clonedb1\SYSAUX01.DBF';
SET NEWNAME FOR DATAFILE 3 TO 'F:\app\HOME\oradata\clonedb1\UNDOTBS01.DBF';
SET NEWNAME FOR DATAFILE 4 TO 'F:\app\HOME\oradata\clonedb1\USERS01.DBF';
SET NEWNAME FOR DATAFILE 5 TO 'F:\app\HOME\oradata\clonedb1\EXAMPLE01.DBF';
SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';
DUPLICATE DATABASE TO clonedb
pfile 'D:\TESTDELETE\initclonedb1.ora'
BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'
LOGFILE GROUP 1 ('F:\APP\HOME\ORADATA\ORCL\REDO01.LOG') SIZE 60M REUSE,
GROUP 2 ('F:\APP\HOME\ORADATA\ORCL\REDO02.LOG.rdo') SIZE 60M REUSE,
GROUP 3 ('F:\APP\HOME\ORADATA\ORCL\REDO03.LOG') SIZE 60M REUSE;
Error it shown is in rman backup creation is as follows
<part>>
sql statement: alter system set db_name = ''ORCL'' comment= ''Modified by RMAN
duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area 640286720 bytes
Fixed Size 1376492 bytes
Variable Size 314576660 bytes
Database Buffers 318767104 bytes
Redo Buffers 5566464 bytes
Starting restore at 20-DEC-11
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=133 device type=DISK
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:07
output file name=F:\APP\HOME\ORADATA\CLONEDB1\CONTROL01.CTL
output file name=F:\APP\HOME\FLASH_RECOVERY_AREA\CLONEDB1\CONTROL02.CTL
Finished restore at 20-DEC-11
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/20/2011 07:07:11
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01102: cannot mount databa
se in EXCLUSIVE mode
RMAN> EXIT
how can i prevent rman setting db_name=orcl which is already exists in the db.. i need to create db from rman backups with different dbname...
whould someone help me out, how can i create database from another database rman backups with different dbname/sid on same host..
My pfile has new db_name , but while db creation rman setting to db_name to source dbname.. it should be new db name that i want create with new db name...
is there any RMAN command to specify new DB name it should set while running
sql statement: alter system set db_name = newdbname -- as part rman script execution...
it appears to be i should not touch the soruce db.. i have access to only source db rman backups and need to create another db with different dbname/sid.. please do help...

When you performing RMAN duplicate why you making your script so complicated?
Your instance name and DB name can be different, But what is the contents in your pfile "D:\TESTDELETE\initclonedb1.ora" ? please do post
Have you started any other services related to ORACLE? check in start --> run --> services.msc any other active oracles services, Make sure you have clonedb1.
Startup in nomount
check the connectivity to target server.
SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';Why you mentioning SET NEWNAME FOR DATAFILE ? You have option of db_file_name_convert/log_file_name_convert in case if your file system different in Target & auxiliary.
BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'When you have backup in same location why you are mentioning this clause?
First run duplicate from auxiliary server as
rman target sys/*****@prod auxiliary /
RMAN> duplicate target database to "db_name";
Am not sure what you are trying to do. is it 11gR1 or 11gR2?
You have option of duplicate from active database without having backup also..
here some links please check it.
http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmdupdb.htm#BGBFDJHB
RMAN 11GR2 : DUPLICATE WITHOUT CONNECTING TO TARGET DATABASE [ID 874352.1]
knowledgespring
     Newbie
Handle:      knowledgespring
Status Level:      Newbie (10)
Registered:      Dec 26, 2007
Total Posts:      243
Total Questions:      77 (75 unresolved)
So sad that forum was able to help only in two answers out of your 77 questions :(
Edited by: CKPT on Dec 21, 2011 5:12 PM

NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES

제품 : RMAN
작성날짜 : 2004-05-20
NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES
=======================================================
오라클 9i RMAN 에서는 백업을 보다 효율적으로 할 수 있는 기능을 보강 했다.
지금 소개할 "Retention Policies" 기능을 통해서 보다 효율적인 RMAN 백업
전략을 세울 수 있다.
1. 백업 화일 최적화 방법 (Backup File Optimization)
백업 화일 최적화란 백업에 소요되는 공간을 최소화 하는 전략이다. RMAN
백업시에 같은 정보 (dbid, checkpoint, and resetlogs data 등등) 를 가지고 있는
화일이 이미 존재하는 백업 셋 내부에 있는지 체크하게 된다. 만일 같은 화일이
이미 백업 되어 있다면 BACK UP 명령은 해당 화일에 대해서는 백업을 하지 않게
된다.
이때 같은 화일이라고 판단하는 기준은 다음과 같다.
* Datafile: 같은 DBID, checkpoint SCN, resetlogs SCN 과 time. 데이타 화일은
반드시정상적으로 offline 되었거나, read-only 이거나, 또는 정상적 으로 close
되어야 함.
* Archived redo log: 같은 thread, sequence number, 그리고 같은 Resetlogs
SCN 과 time.
* Backup Set: 같은 Backup Set recid 와 stamp.
RMAN 이 백업을 수행하다가 위와 같은 조건의 화일이 이미 존재함을 확인하면
이것은 건너뛰게 될 화일의 대상이다. 하지만 이때 바로 Skip 을 결정하지 않고
정해진 Retention Policies 를 조사 한후에 Skip 여부를 결정 하게 된다.
만일 백업 명령에 DELETE INPUT option 이 사용되면 RMAN 은 백업이 Skip
되어도 화일을 지우게 된다.
RMAN 은 모든 화일에 대한 백업이 Skip 되어도 에러메시지나 경고를 보내지
않는다.
그러나 만일 데이터 화일에 대한 백업이 recovery policy window 보다 오래
된 것 이면 RMAN 은 새로운 백업 화일을 만들기 위해서 화일을 백업 하게 된다.
Note:
자체적인 expirations policy 를 가지고 있는 media manager 를 사용할 경우에는
이런 백업 최적화 정책을 사용하는 것에 신중을 기해야 한다.
백업 최적화 를 사용하기 위해서는 CONFIGURE 명령을 사용한다. CONFIGURE
명령은 명령 수행 이후에 이루어지는 모든 백업에 대해 적용이 된다.
예:
CONFIGURE BACKUP OPTIMIZATION ON; # default 는 OFF
2. Backup Optimization에 Retention Policies 적용 하기
Retention Policy 로 백업 최적화를 조절 할 수 있다. 그러나 retention policy를
사용하지 않기 위해서는 'CONFIGURE RETENTION POLICY TO NONE' 을
이용해서 명시적으로 retention policy를 사용하지 않는다고 해야 한다. 디폴트로
REDUNDANCY = 1 이 적용 된다.
a. Recovery Window 를 이용한 Backup Optimization
만일 백업 최적화가 enable 되어 있고 Recovery Window 가 retention policy
적용을 위해서 셋업 되어 있으면 RMAN 은 항상 가장 최근의 백업이 Recovery
Window 보다 오래된 데이터 화일을 백업한다.
예를 들면 다음과 같은 조건에서
o Today is February 21.
o The recovery window is 7 days.
o The most recent backup of tablespace tbs2 to tape is January 3.
o Tablespace tbs2 is read-only.
2월 21일에 tbs2 테이블 스페이스를 테이프로 백업을 하라는 명령을 내리면,
RMAN 은 이 화일이 1월3일 이후에 변경 사항이 없는데도 불구 하고 백업을 하게
된다. 이로써 RMAN 은 최근 7일 동안에 최소한 한번의 백업이 있어야 된다는
조건을 지키게 된다.
이러한 작동 방식은 media manager 가 오래된 테잎을 제거 해도 되도록 한다.
그렇지 않다면, media manager 는 1월 3일의 백업을 무한정 가지고 있게 된다.
2월 21일에 tbs2 테이블 스페이스의 보다 최근의 백업을 만듦으로 써, RMAN 은
media manager 가 1월 3일에 백업 했던 테입을 지워도 되도록 한다.
b. Redundancy 를 이용한 Backup Optimization
Retention policy 로 Redundancy 를 채택 한 경우에 RMAN 은 Redundancy
에 1을 더한 갯수를 초과하는 오프라인 또는 읽기 전용 화일의 백업을 건너뛴다.
이때 'CONFIGURE RETENTION POLICY TO REDUNDANCY n' 명령어로
Redundancy의 갯수를 정한다.
아래와 같은 백업 최적화 명령을 내린 경우를 예로 든다:
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
아카이브 테이블스페이스를 한번도 백업을 받은적이 없고 다음의 작업을 1주일
동안 한다고 하자.
Day Action Result Redundant Backup
Monday Take tablespace archive offline clean.
Tuesday Run BACKUP DATABASE. The archive tablespace is backed up.
Wednesday Run BACKUP DATABASE. The archive tablespace is backed up.
Thursday Run BACKUP DATABASE. The archive tablespace is backed up. Tuesday backup.
Friday Run BACKUP DATABASE. n/a Tuesday backup.
Saturday Run BACKUP DATABASE. n/a Tuesday backup.
Sunday Run DELETE OBSOLETE. The Tuesday backup is deleted.
Monday Run BACKUP DATABASE. The archive tablespace is backed up. Wednesday backup.
화요일, 수요일, 그리고 목요일의 백업은 아카이브 테이블 스페이스를 복사 해서
3개의 백업이 반드시 존재 해야 한다는 조건을 충촉 시킨다. (1+Redundancy)
금요일과 토요일에는 백업 최적화 조건에 의해서 아카이브 테이블 스페이스를
복사하지 않게 된다.
RMAN 은 일요일에는 유효기간이 지난 백업 화일을 지우게 된다. 따라서 화요일에
만든 백업은 삭제 된다. 월요일의 전체 백업은 3개의 백업이 존재 해야 한다는 조건
때문에 아카이브 테이블 스페이스를 또 다시 백업하게 된다. 이런 방식으로 백업
사이클이 진행 된다.
3. RETENTION POLICY NONE vs. DEFAULT
주의 사항:
'CONFIGURE RETENTION POLICY TO NONE' 과 'CONFIGURE RETENTION
POLICY TO DEFAULT' 는 그 의미가 같지 않다. 전자는 RETENTION POLICY
자체가 존재 하지 않는다는 의미 이며 백업은 expire 되지 않으며 'DELETE
OBSOLETE' 명령은 사용 할 수 없게 된다. 후자는 디폴트 RETENTION POLICY
(REDUNDANCY 1) 를 사용하게 된다는 의미 이다.
'DELETE OBSOLETE' 명령은 RETENTION POLICY 기준으로 expire 된 백업을
제거 하라는 명령이다.
보다 자세한 내용은 Oracle9i Recovery Manager User's Guide and
Reference의 Backup Optimization 부분을 참고 하시기 바랍니다.
--------------THE END----------------------------------------------

Hi,
Backup optimisation = +- do not copy empty space.
So, when you issue your BACKUP statement, it backs up the datafile. dot. nothing more.
In order to achieve what you're testing, look into TFM for BACKUP INCREMENTAL LEVEL x .
Regards,
Yoann.

Need Advice on RMAN backup script

Hi;
Can any one advice if any error or guide to make RMAN backup proper :
Backup Policy are:
1.     0 level backup
2.     current log file is arvhived before backing up
3.     backup whole database (datafiles)
4.     backup separate control file
5.     backup is done on disk
6.     control file auto backup ON
7.     only 7 days archive log are need to be preserve ; old need to be deleted
### one time paramters seting
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
### Command for weekly 0 level backup
run {
allocate channel c1 type disk;
sql 'alter system archive log current';
backup incremental level 0 tag = weekly_database format 'o:\rman\backup\full_weekly_%d_%s_%p_%t'(database);
release channel c1;
configure controlfile autobackup format for device type disk to 'o:\rman\backup\auto_ctrl_weekly_%f';
allocate channel c1 type disk;
backup tag = weekly_arch archivelog until time 'sysdate-7' format 'o:\rman\backup\archive_weekly_%d_%s_%p_%t';
delete archivelog until time 'sysdate-7';
release channel c1;
Regards
Smith

Dear Pierre F.;
Actually, I just added in my backup plan to have daily backup through RMAN, instead of COLD backup.
I have planned to take cold backup once a week. here is the side of data:
*** datafile 410
*** size of database : 86 GM
*** relog files size : 250MB
*** daily archive logs are : 250MB * 4(number of files) = 1GM aprox.
yes, time constraint is there; just because of the size of database. and we r going for 24/7
Is this script going to run only one per week ?
Ans: no I this was level 0 backup; i will take level 1 incremental backup with same script daily too.
Do you have any other RMAN script ?
ANS: no, I will modify same script for incremental.
after local copy of backup all backup files (RMAN) will be copy over network to backup server or we can install LTO tape device to copy directly from database server.
kindly advise me I am new in RMAN.
regards;
SMITH

Rman backup level 0 doubt

Similar Messages

Maybe you are looking for