Incremental backup in 10g

Hi,
I am using RMAN 10.2.0.3.0
and target db 10.2.0.3.0
in nocatalaog mode
I have scheduled the level 0 backup weekly and level 1 backup daily as below.
Saturday
run
show all;
backup incremental level 0 database;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup archivelog all;
report obsolete;
delete obsolete;
restore validate database;
restore validate controlfile;
exit
Sunday-Friday
run
show all;
backup incremental level 1 database;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup archivelog all;
report obsolete;
delete obsolete;
restore validate database;
restore validate controlfile;
exit
Saturday the incr level 0 was done without any issues, but next day while running level1 it should take the level0(Saturday) as base, but here it shows that '*no parent copy or data file found* ' and it again takes the full backup.
Please let me know if I did anything wrong. Also my retention policy is set to RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS and my controlfile_record_keep_time is 7.
Please help me
Thanks,
Priya
Edited by: Priya on Sep 22, 2010 6:12 AM

Log of Incremental Level 0
Recovery Manager: Release 10.2.0.3.0 - Production on Mon Sep 20 12:07:45 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: FUJIVDB (DBID=639859515)
RMAN> run
2> {
3> show all;
4> backup incremental level 0 database;
5> sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
6> backup archivelog all;
7> report obsolete;
8> delete obsolete;
9> restore validate database;
10> restore validate controlfile;
11>
12> }
13> exit
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\Backups\Controlfile\cf_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'C:\Backups\datafile\ora_df%t_s%s_s%p';
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 'C:\ORACLE\ORA102\DATABASE\SNCFFUJIVDB_%F%.ORA';
Starting backup at 20-SEP-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=323 devtype=DISK
channel ORA_DISK_1: starting incremental level 0 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=C:\ORACLE\ORADATA\FUJIVDB\SYSAUX01.DBF
input datafile fno=00004 name=C:\ORACLE\ORADATA\FUJIVDB\UNDO02.DBF
input datafile fno=00002 name=C:\ORACLE\ORADATA\FUJIVDB\UNDO01.DBF
input datafile fno=00001 name=C:\ORACLE\ORADATA\FUJIVDB\SYSTEM01.DBF
input datafile fno=00006 name=C:\ORACLE\ORADATA\FUJIVDB\USER01.DBF
input datafile fno=00011 name=C:\ORACLE\ORADATA\FUJIVDB\INDX01.DBF
input datafile fno=00007 name=C:\ORACLE\ORADATA\FUJIVDB\USER11.DBF
input datafile fno=00008 name=C:\ORACLE\ORADATA\FUJIVDB\USER12.DBF
input datafile fno=00009 name=C:\ORACLE\ORADATA\FUJIVDB\USER13.DBF
input datafile fno=00010 name=C:\ORACLE\ORADATA\FUJIVDB\USER14.DBF
input datafile fno=00012 name=C:\ORACLE\ORADATA\FUJIVDB\INDX11.DBF
input datafile fno=00013 name=C:\ORACLE\ORADATA\FUJIVDB\INDX12.DBF
input datafile fno=00014 name=C:\ORACLE\ORADATA\FUJIVDB\INDX13.DBF
input datafile fno=00015 name=C:\ORACLE\ORADATA\FUJIVDB\INDX14.DBF
input datafile fno=00005 name=C:\ORACLE\ORADATA\FUJIVDB\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 20-SEP-10
channel ORA_DISK_1: finished piece 1 at 20-SEP-10
piece handle=C:\BACKUPS\DATAFILE\ORA_DF730210069_S31_S1 tag=TAG20100920T120749 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:06
Finished backup at 20-SEP-10
Starting Control File and SPFILE Autobackup at 20-SEP-10
piece handle=C:\BACKUPS\CONTROLFILE\CF_C-639859515-20100920-00 comment=NONE
Finished Control File and SPFILE Autobackup at 20-SEP-10
sql statement: ALTER SYSTEM ARCHIVE LOG CURRENT
Starting backup at 20-SEP-10
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=1 recid=9 stamp=729858731
input archive log thread=1 sequence=2 recid=10 stamp=729887062
input archive log thread=1 sequence=3 recid=11 stamp=729953114
input archive log thread=1 sequence=4 recid=12 stamp=729973634
input archive log thread=1 sequence=5 recid=13 stamp=729973634
input archive log thread=1 sequence=6 recid=14 stamp=730015209
input archive log thread=1 sequence=7 recid=15 stamp=730058416
input archive log thread=1 sequence=8 recid=16 stamp=730058416
input archive log thread=1 sequence=9 recid=17 stamp=730144816
input archive log thread=1 sequence=10 recid=18 stamp=730144816
input archive log thread=1 sequence=11 recid=19 stamp=730210042
input archive log thread=1 sequence=12 recid=20 stamp=730210200
input archive log thread=1 sequence=13 recid=21 stamp=730210201
channel ORA_DISK_1: starting piece 1 at 20-SEP-10
channel ORA_DISK_1: finished piece 1 at 20-SEP-10
piece handle=C:\BACKUPS\DATAFILE\ORA_DF730210201_S33_S1 tag=TAG20100920T121001 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:17
Finished backup at 20-SEP-10
Starting Control File and SPFILE Autobackup at 20-SEP-10
piece handle=C:\BACKUPS\CONTROLFILE\CF_C-639859515-20100920-01 comment=NONE
Finished Control File and SPFILE Autobackup at 20-SEP-10
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 8 days
no obsolete backups found
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 8 days
using channel ORA_DISK_1
no obsolete backups found
Starting restore at 20-SEP-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting validation of datafile backupset
channel ORA_DISK_1: reading from backup piece C:\BACKUPS\DATAFILE\ORA_DF729786183_S13_S1
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\BACKUPS\DATAFILE\ORA_DF729786183_S13_S1 tag=TAG20100915T142303
channel ORA_DISK_1: validation complete, elapsed time: 00:00:25
Finished restore at 20-SEP-10
Starting restore at 20-SEP-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting validation of datafile backupset
channel ORA_DISK_1: reading from backup piece C:\BACKUPS\CONTROLFILE\CF_C-639859515-20100920-01
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\BACKUPS\CONTROLFILE\CF_C-639859515-20100920-01 tag=TAG20100920T121018
channel ORA_DISK_1: validation complete, elapsed time: 00:00:03
Finished restore at 20-SEP-10
Recovery Manager complete.
Next day Log Of Incremental Level 1
Recovery Manager: Release 10.2.0.3.0 - Production on Tue Sep 21 17:58:00 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: FUJIVDB (DBID=639859515)
RMAN> run
2> {
3> show all;
4> backup incremental level 1 database;
5> sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
6> backup archivelog all;
7> report obsolete;
8> delete obsolete;
9> restore validate database;
10> restore validate controlfile;
11> }
12> exit
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\Backups\Controlfile\cf_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'C:\Backups\datafile\ora_df%t_s%s_s%p';
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 'C:\ORACLE\ORA102\DATABASE\SNCFFUJIVDB_%F%.ORA';
Starting backup at 21-SEP-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=321 devtype=DISK
no parent backup or copy of datafile 3 found
no parent backup or copy of datafile 4 found
no parent backup or copy of datafile 2 found
no parent backup or copy of datafile 1 found
no parent backup or copy of datafile 6 found
no parent backup or copy of datafile 11 found
no parent backup or copy of datafile 7 found
no parent backup or copy of datafile 8 found
no parent backup or copy of datafile 9 found
no parent backup or copy of datafile 10 found
no parent backup or copy of datafile 12 found
no parent backup or copy of datafile 13 found
no parent backup or copy of datafile 14 found
no parent backup or copy of datafile 15 found
no parent backup or copy of datafile 5 found
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=C:\ORACLE\ORADATA\FUJIVDB\SYSAUX01.DBF
input datafile fno=00004 name=C:\ORACLE\ORADATA\FUJIVDB\UNDO02.DBF
input datafile fno=00002 name=C:\ORACLE\ORADATA\FUJIVDB\UNDO01.DBF
input datafile fno=00001 name=C:\ORACLE\ORADATA\FUJIVDB\SYSTEM01.DBF
input datafile fno=00006 name=C:\ORACLE\ORADATA\FUJIVDB\USER01.DBF
input datafile fno=00011 name=C:\ORACLE\ORADATA\FUJIVDB\INDX01.DBF
input datafile fno=00007 name=C:\ORACLE\ORADATA\FUJIVDB\USER11.DBF
input datafile fno=00008 name=C:\ORACLE\ORADATA\FUJIVDB\USER12.DBF
input datafile fno=00009 name=C:\ORACLE\ORADATA\FUJIVDB\USER13.DBF
input datafile fno=00010 name=C:\ORACLE\ORADATA\FUJIVDB\USER14.DBF
input datafile fno=00012 name=C:\ORACLE\ORADATA\FUJIVDB\INDX11.DBF
input datafile fno=00013 name=C:\ORACLE\ORADATA\FUJIVDB\INDX12.DBF
input datafile fno=00014 name=C:\ORACLE\ORADATA\FUJIVDB\INDX13.DBF
input datafile fno=00015 name=C:\ORACLE\ORADATA\FUJIVDB\INDX14.DBF
input datafile fno=00005 name=C:\ORACLE\ORADATA\FUJIVDB\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 21-SEP-10
channel ORA_DISK_1: finished piece 1 at 21-SEP-10
piece handle=C:\BACKUPS\DATAFILE\ORA_DF730317484_S56_S1 tag=TAG20100921T175803 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:06
Finished backup at 21-SEP-10
Starting Control File and SPFILE Autobackup at 21-SEP-10
piece handle=C:\BACKUPS\CONTROLFILE\CF_C-639859515-20100921-06 comment=NONE
Finished Control File and SPFILE Autobackup at 21-SEP-10
sql statement: ALTER SYSTEM ARCHIVE LOG CURRENT
Starting backup at 21-SEP-10
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=1 recid=9 stamp=729858731
input archive log thread=1 sequence=2 recid=10 stamp=729887062
input archive log thread=1 sequence=3 recid=11 stamp=729953114
input archive log thread=1 sequence=4 recid=12 stamp=729973634
input archive log thread=1 sequence=5 recid=13 stamp=729973634
input archive log thread=1 sequence=6 recid=14 stamp=730015209
input archive log thread=1 sequence=7 recid=15 stamp=730058416
input archive log thread=1 sequence=8 recid=16 stamp=730058416
input archive log thread=1 sequence=9 recid=17 stamp=730144816
input archive log thread=1 sequence=10 recid=18 stamp=730144816
input archive log thread=1 sequence=11 recid=19 stamp=730210042
input archive log thread=1 sequence=12 recid=20 stamp=730210200
input archive log thread=1 sequence=13 recid=21 stamp=730210201
input archive log thread=1 sequence=14 recid=22 stamp=730210443
input archive log thread=1 sequence=15 recid=23 stamp=730210444
input archive log thread=1 sequence=16 recid=24 stamp=730231219
input archive log thread=1 sequence=17 recid=25 stamp=730231220
input archive log thread=1 sequence=18 recid=26 stamp=730261837
input archive log thread=1 sequence=19 recid=27 stamp=730299124
input archive log thread=1 sequence=20 recid=28 stamp=730299125
input archive log thread=1 sequence=21 recid=29 stamp=730299448
input archive log thread=1 sequence=22 recid=30 stamp=730299459
input archive log thread=1 sequence=23 recid=31 stamp=730299531
input archive log thread=1 sequence=24 recid=32 stamp=730299531
input archive log thread=1 sequence=25 recid=33 stamp=730317616
input archive log thread=1 sequence=26 recid=34 stamp=730317616
channel ORA_DISK_1: starting piece 1 at 21-SEP-10
channel ORA_DISK_1: finished piece 1 at 21-SEP-10
piece handle=C:\BACKUPS\DATAFILE\ORA_DF730317617_S58_S1 tag=TAG20100921T180016 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:18
Finished backup at 21-SEP-10
Starting Control File and SPFILE Autobackup at 21-SEP-10
piece handle=C:\BACKUPS\CONTROLFILE\CF_C-639859515-20100921-07 comment=NONE
Finished Control File and SPFILE Autobackup at 21-SEP-10
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 8 days
no obsolete backups found
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 8 days
using channel ORA_DISK_1
no obsolete backups found
Starting restore at 21-SEP-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting validation of datafile backupset
channel ORA_DISK_1: reading from backup piece C:\BACKUPS\DATAFILE\ORA_DF729786183_S13_S1
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\BACKUPS\DATAFILE\ORA_DF729786183_S13_S1 tag=TAG20100915T142303
channel ORA_DISK_1: validation complete, elapsed time: 00:00:26
Finished restore at 21-SEP-10
Starting restore at 21-SEP-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting validation of datafile backupset
channel ORA_DISK_1: reading from backup piece C:\BACKUPS\CONTROLFILE\CF_C-639859515-20100921-07
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\BACKUPS\CONTROLFILE\CF_C-639859515-20100921-07 tag=TAG20100921T180035
channel ORA_DISK_1: validation complete, elapsed time: 00:00:02
Finished restore at 21-SEP-10
Recovery Manager complete.

Similar Messages

Optimized incremental backup in 10g

Hi,
I study the http://www.oracle.com/technology/products/database/oracle10g/pdf/twp_general_10gdb_product_family.pdf and i have one question about it...
In "Incremental backup" feature/option there is a note :"SE/XE no optimized incremental backup".
What are the features of "optimized incremental backup"...????
Thanks......
Sim

I believe that is referring to block change tracking. That allows Oracle to track which blocks have actually changed since the last backup, so RMAN can just read the tracking file and backup those blocks rather than examining each block to see whether it has changed.
Justin

9i to 10g Incremental Backup

I have an Oracle 9i database which I need to do incremental backup into my 10g database in the different server. What is the best way to do this?
any help would be greatly appreciated

I'm not sure I understand what you're after.
"Backup" generally means a physical backup-- RMAN or user managed backups. But that doesn't sound like what you're after. You don't restore physical backups into another database and the restored backup will always be the same Oracle version as the source database.
"Backup" might also refer to a logical backup taken via export (classic or DataPump). But you cannot (functionally and practically) generate an incremental export. You could import an export generated from a 9i database into a 10g database.
Perhaps you mean "replication" rather than "backup". If that is the case, can you explain the business problem you're trying to solve? There are a variety of ways to replicate data from one database to another-- Streams, materialized views, CDC, DataGuard, etc.-- depending on the problem you're trying to solve.
Justin

Need help on incremental backup

Hi,
I am running a rman backup using 10g DBCONSOLE. I selected level 0 backup and it's running. this is the command.
>>
backup incremental level 0 cumulative device type disk filesperset = 5 tag 'BACKUP_DHAVA.SOS.S_081507014538' database;
>>
my question is when should run my level 1 backup?? can i run every week level 1backup and run level 0 back every 4 week?
if i want to recover in what order should i recover??
thanks

can i run every week level 1backup and run level 0 back every 4 week?There's no fix rule. But I would do a level 0 backup more frequently, let's say once a week. And a level 1 backup the other days. Otherwise a restore/recovery could run very long.
if i want to recover in what order should i recover??You don't have to care about this, RMAN knows which backups are needed in which order. Restore process starts always with a level 0 backup, afterwards it reads all needed level 1 backups and the following recover process applies the archivelogs.
Werner

About incremental backup

Dear Friends ,
We have a ORacle 10g database server which is 24x7 hours running . We take everyday RMAN full backup ,now we want to run "Incremental rman backup" 6 days in a week and "Full Backup" rest of the week . But in oracle article we read that
"RMAN can only create incremental backups of datafiles, not of archived redo log files or other files."
(source: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup001.htm#BRBSC131)
In this moment I think , archivelog is very important for database recovery and it is necessary to take archivelog backup regularly .Now if we want to run Incremental backup then I think I cannot take "archivelog" backup using following script :
run
allocate channel t1 type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
sql "alter system switch logfile";
backup incremental level 1 database plus archivelog;
Give me some idea plz ... ...what should I need to ?

Sorry Hemant ,
Accroding to ur advice , I run the script following way :
run
allocate channel t1 type disk;
backup incremental level 1 database;
sql "alter system switch logfile";
backup archivelog;
But I got the following ERROR :
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "all, from, high, like, logseq, low, scn, sequence, time, until"
RMAN-01007: at line 6 column 18 file: standard input
RMAN>
But when I use the following script , it shows no error :
run
allocate channel t1 type disk;
sql "alter system switch logfile";
backup incremental level 1 database plus archivelog;
I think here database is backup only using LEVEL 1 , but archivelog is backed up full . Here is the output :
RMAN> run
2> {
3> allocate channel t1 type disk;
4> sql "alter system switch logfile";
5> backup incremental level 1 database plus archivelog;
6> }
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: sid=159 devtype=DISK
sql statement: alter system switch logfile
Starting backup at 29-JUL-08
current log archived
channel t1: starting archive log backupset
channel t1: specifying archive log(s) in backup set
input archive log thread=1 sequence=2 recid=1 stamp=661354070
input archive log thread=1 sequence=3 recid=2 stamp=661354123
input archive log thread=1 sequence=4 recid=3 stamp=661354895
input archive log thread=1 sequence=5 recid=4 stamp=661354935
input archive log thread=1 sequence=6 recid=5 stamp=661355047
input archive log thread=1 sequence=7 recid=6 stamp=661355050
input archive log thread=1 sequence=8 recid=7 stamp=661355072
input archive log thread=1 sequence=9 recid=8 stamp=661355327
channel t1: starting piece 1 at 29-JUL-08
channel t1: finished piece 1 at 29-JUL-08
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_07_29\O1_MF_ANNNN_TAG20080729T143725_48
channel t1: backup set complete, elapsed time: 00:00:06
Finished backup at 29-JUL-08
Starting backup at 29-JUL-08
channel t1: starting incremental level 1 datafile backupset
channel t1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF
channel t1: starting piece 1 at 29-JUL-08
channel t1: finished piece 1 at 29-JUL-08
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_07_29\O1_MF_NNND1_TAG20080729T143732_48
channel t1: backup set complete, elapsed time: 00:00:15
Finished backup at 29-JUL-08
Starting backup at 29-JUL-08
current log archived
channel t1: starting archive log backupset
channel t1: specifying archive log(s) in backup set
input archive log thread=1 sequence=33 recid=32 stamp=661358270
channel t1: starting piece 1 at 29-JUL-08
channel t1: finished piece 1 at 29-JUL-08
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_07_29\O1_MF_ANNNN_TAG20080729T143751_48
channel t1: backup set complete, elapsed time: 00:00:02
Finished backup at 29-JUL-08
Starting Control File and SPFILE Autobackup at 29-JUL-08
piece handle=D:\RMAN_BACK\CFC-2444681464-20080729-0C comment=NONE
Finished Control File and SPFILE Autobackup at 29-JUL-08
released channel: t1
RMAN>
what u think , am i right ?

RMAN: Increment backup very slow

Hi All,
We have Datawarehouse database having size around 7TB. Increment backup performance is extremely poor it is taking approx 14hrs to complete the process. We have also enabled block change tracking but failed to meet target.
Below mentioned DB info & RMAN configuration parameters:
DB: 11.1.0.6
OS: Linux 2.6.18-128.el5 x86_64
System has 16 processor when more than two process per CPU i.e. 32
CONFIGURE RETENTION POLICY TO REDUNDANCY 5;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/d01copy/control_bkp/autobackup_control_file%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 13 BACKUP TYPE TO COMPRESSED BACKUPSET;
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 COMPRESSION ALGORITHM 'BZIP2';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.1.0/dbs/snapcf_PRODDB.f'; # default
Thanks in advance.

Thnaks for reply.
Have you configured Compressed backups?
--> Yes. with below command.
RMAN> backup as compressed backupset incremental level 1 tag=$v_tag database;
Have you allocated channels ?
--> Yes.
allocate channel backup_disk1 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk2 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk3 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk4 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk5 type disk format '$v_bdest/%U' maxpiecesize 10G;
What is the Large pool size configured? try to increase.
--> large_pool_size=1073741824
Is backup to DISK or TAPE? mentioned in script?
--> Backup goes to DISK only.
How is DISK performance?
--> How can we calculate DISK performance on LINUX?
Regards,

Incremental BACKUP to resolve large gap in Data Guard

Hi, all,
We run into a situation that standby database was shutdown for a long time and had a large gap between the primary and standby. I am interested in the idea to use incremental backup from primary db to resolve the gap. Does anyone know the procedure to do the work? Our environment is Oracle 10g RAC R2 on both primary and standby, ASM. Any suggestions are highly appreciated. Thanks in advance

Check Using RMAN Incremental Backups to Roll Forward a Physical Standby Database.

Level 1 incremental backup taking larger space

Hi All,
Yesterday i had level 1 incremental backup. Backup completed successfully but its size was as equal as Full Backup.
What could me the possible reason for that ?
Environmnt is Oracle 10g R2 2 Node RAC on windows.

Hi,
you can enable block change tracking and see the results.
ORACLE 10G BLOCK CHANGE TRACKING INSIDE OUT (Doc ID 1528510.1)
Thanks,
Renu

Is Fast Incremental Backups possible on standby databases for 10.2.0.5?

Hi,
Can anyone help to clarify if it is possible to have Fast Incremental Backups on 10.2.0.5 standby . The information in MOS (Doc ID 262853.1) stated:
Note : Fast Incremental Backups were not possible on standby databases till 10g
but from 11g Fast Incremental Backups are available on standby databases also.
It sounds ambiguous.
Thanks
Jun

The answer is No, due bug 6130588.
Is Block Change Tracking Enabled On Physical Standby Supported By Rman (Doc ID 468576.1)

Oracle incremental backup too slow

Hello All,
Oracle 9.2.0.7
Windows 2003 server
Database size around 200 GB.
Daily archive generation may be around 40. Archive log size 200 MB.
We have implemented the below backup strategy
1. weekly once full incremental level 0 backup(differential).
2. Daily incremental level 1 backup(differential).
Daily incremental backup size will be around 1 GB.
Now we are facing a problem because of the incremental backup. The incremental backup is taking more than 1 hour time to complete. So we are not able to run it in the production time.its a 24/7 production database.
Please advice how to reduce the incremental backup time ?
Is there any options like what we have in 10g Block change tracking. please advice..
TIA,

ORCLDB wrote:
Hello All,
Oracle 9.2.0.7
Windows 2003 server
Database size around 200 GB.
Daily archive generation may be around 40. Archive log size 200 MB.
We have implemented the below backup strategy
1. weekly once full incremental level 0 backup(differential).
2. Daily incremental level 1 backup(differential).
Daily incremental backup size will be around 1 GB.
Now we are facing a problem because of the incremental backup. The incremental backup is taking more than 1 hour time to complete. So we are not able to run it in the production time.its a 24/7 production database.
Please advice how to reduce the incremental backup time ?
Is there any options like what we have in 10g Block change tracking. please advice..
TIA,Please refer to documentation:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmtunin.htm#CACJCBDB

Incremental backup information

hi,
i am using oracle 10g database enterprise edition release 2 in linux rhel 5. i have taken a some incremental backups. now i need to look at the information about the incremental backup? i wanted to know what all the incremental backups that will be used for complete recovery. where can i view those informations?? plz tell me.
thanks in advance.

793097 wrote:
hi,
i am using oracle 10g database enterprise edition release 2 in linux rhel 5. i have taken a some incremental backups. now i need to look at the information about the incremental backup? i wanted to know what all the incremental backups that will be used for complete recovery. where can i view those informations?? plz tell me.
thanks in advance.Use LIST BACKUP command
Kamran Agayev A.
Oracle ACE
My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/

Rman backup for 10g compresses?

Background Info:
10g production databases. 10.2.0
RedHat 4, 64 bit Linux
Use RMAN to backup to local, then backup software copies files to tape.
10 databases, DB size from 10gb - 200gb
Currently I perform: 2 * level 0 and 5 * level 2 per week.I have been using my 9i RMAN scripts (after doing many tests).
Right now I am thinking of using 10g feature 'Compressed Files'.
Does anyone know of any issues / side affect using this feature?
Same question for 'Block change feature', is it advisable to use on prod databases?
~
Many thanks for any response.

Compression saves disk space, but you have to pay for it. Statement from Oracle:
There is some CPU overhead associated with compressing backup sets. If the database being backed up is running at or near its maximum load, you may find the overhead from using AS COMPRESSED BACKUPSET unacceptable. In most other circumstances, compressing backupsets saves enough disk space to be worth the CPU overhead.
Block change feature is useful, if you plan to use incremental backups. It makes such backups faster, because RMAN knows in advance which blocks were changed and which not.
Werner

Restoring Incremental Backup using Netbackup

Hi,
Need your help. We have a backup of our Oracle 10g Database(one full backup and one incremental backup). The full backup (level0) is done by Netbackup and the incremental backup is done by local rman.
Now we want to restore the database. I have modified the script of Netbackup to restore the controlfile of incremental backup and allocate 2 channels for tape and disk. Our incremental backup resides in disk. Is the script we used below correct?
RUN {
ALLOCATE CHANNEL ch00 TYPE DISK;
send 'NB_ORA_CLIENT=prod01, NB_ORA_SERV=NAS';
RESTORE CONTROLFILE FROM '/rman/backup/incremental/ctl_PROD_c-86955024-20101221-
03';
ALTER DATABASE MOUNT;
RELEASE CHANNEL ch00;
RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE DISK;
send 'NB_ORA_CLIENT=prod01, NB_ORA_SERV=NAS';
#SET UNTIL SEQUENCE 138730 thread 1;
RESTORE DATABASE;
RECOVER DATABASE;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
thanks,
Benjo

Hi benjo,
You cannot allocate two types of channels at the same time so you should try a three step approach.
(Every time create a new connection to the target.)
Restore controlfile
No need for:
send 'NB_ORA_CLIENT=prod01, NB_ORA_SERV=NAS';exit
Restore database from tape.
remove from your second run block
ALLOCATE CHANNEL ch01 TYPE DISK;
RECOVER DATABASE;
RELEASE CHANNEL ch01;exit
Than create a recover command with disk channels
basicly remove the tape channel and restore commands from your second run block and add
alter database open resetlogs;Regards,
Tycho

Incremental Backup Levels

Hello Everybody.
I want to know the description of all 0-4 levels of incremental backups. Anybody please tell me in details.
Thanks and Regards

ora-boy
Questions like this have version specific answers. Almost all questions have.
It is useless and silly to post any question without any version information.
Here's why
In 8i and 9i: incremental levels are between 0 and 3. There is nothing to explain,
1>0, 2>1, 3>2. That's all.
In 10g there is only 0 and 1. The higher levels have been removed.
Please stop asking questions without version information, assuming people keep track of your version (which we don't) or will summarize it for all available versions (which we won't )
Sybrand Bakker
Senior Oracle DBA

Question about using an incremental backup to update a standby

We have a 2TB Oracle 10g database with a standby and the application that uses it is about to be updated. We're using cumulative incremental backups with block change tracking to back it up with weekly level 0 backups. The application upgrade will be making a lot of changes (several hundred GB) and we have stop the standby during the upgrade process as a quick way to get back (we don't have the space for a flashback recovery) in the event that there are issues with the upgrade. We can just let the archivelogs back up and get them over to the standby and applied once they decide they like the upgrade but, it looks like it would be simpler and perhaps quicker to use an incremental backup to update the standby. I probably won't but, If we do that, it looks like we can turn off archivelogs in the primary and not deal with them at all. I've never tried this but, I do have some questions.
Does it make sense to take this approach?
If we were to turn off archivelogs in the primary, would that have any effect on block change tracking? I don't see why it would but, had to ask. Of course, we would turn archivelogs back on and take a level 1 backup after the upgrade.
Thanks in advance for the education.

Funny you should mention that rolling upgrade, I'm actually planning to do that in another environment. My testing says it works pretty well and I'll be able to move a 400GB database to new hardware and upgrade it to 11g with very little downtime. However, in this case, the database is not being upgraded. The application is. It's just that, as part of that upgrade, there are a lot of updates and I'd just as soon not deal with the archivelogs for that. Here's what I was thinking about:
Set logs shipping to defer in the primary.
Stop log apply in the standby.
Turn off archivelogs in the primary.
Do the application update.
If they like the results, turn archivelogs back on in the primary.
Take an rman incremental backup from scn in the primary.
Apply the incremental backup to the standby.
Start log log apply in the standby.
Start log shipping in the primary.
The process for getting and using the incremental is described here:
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#BGBCEBJG
This isn't your regular incremental backup.
So, am I the only crazy one? Has anyone else tried this?

Incremental backup in 10g

Similar Messages

Maybe you are looking for