Configuring Incremental Backup

Hi there
I am designing RMAN backup
- I want to use Repository Catalog
- I want to take level zero backup every saturday night
- I want to take level 1 incremental backup everyday night, except sunday
- and I want jobs to be scheduled and I prefer not to use EM.
- I want to check for logical and physical corruptions before taking the backup
Q1. what is the place of archive log in incremental backup
Q2. should I include the archive log in level 0, in level 1 or in both
Q3. so can any one provide me with a sort of template scripts to help me start with
I know there are wide resources but I wanted a seed to build up on.
I appreciate any help
Thanks

Firstly - you cannot backup archive logs at level 0 or 1. When you think about it archive logs don't change once they are created so why would you ever back them up with incremental level 1 besides there is no option to do this.
You can say however "backup incremental level 0 database include current controlfile spfile plus archivelog;" in one statement.
"You can delete the archive logs once incremental backup is complete. It is done automatically by using delete obsolete command."
Depends if that's what you want to achieve - I personally prefer to backup archive logs at least 3 times before deleting them (BACKED UP 3 TIMES) and also on seperate tapes. The balance is between available disk space for archive logs and requirements of the client. You would hate to compromise recoverability because of a few lost archive logs all backed up on one corrupted or lost tape.
You should also "sql 'alter system archive log current';" before the backup command to capture maximum data changes.

Similar Messages

ACS Incremental backup not configured

Hi All,
I have upgraded to ACS 5.5 patch 6, but having strange issues.
Though the incremental backup is configured, it is sending an alert as "Incremental backup is not configured. Configuring incremental backup is necessary to make the database purge successful. This will help to avoid disk space issues. View database Size is 13.68GB and size it occupies on the harddisk is 13.65GB."
I checked under the purge and incremental history, it has done the incremental backup.
I received another alert "Configure Remote Repository under Purge Configuration which is used to take a backup of data before purge" and check it is accessible from CLI #show repository xxxxx.
Has anyone gotten these issues before??
I have configured all these on Primary.
Thanks

Warning Alarm to wait 90 min between incremental backup and Purge time
CSCtx20928
Description
From the ACS 5.x user guides , it is documented that If you enable incremental backup, data is purged daily at 4:00 a.m. at the local time zone where the ACS instance that runs the View process is located.
However, you cannot concurrently run an incremental backup, full backup, and data purge. If any of these jobs are running, you must wait for a period of 90 minutes before you can begin the next job.
If the Incremental Backup schedule is configured within the 90 minutes of Data Purge time, there is no warning thrown on the GUI against this config.In this case, we get Warning Alarms which don't indicate the right status to have wait period of 90 minutes before you can begin the next job.
The Warning Alarms which are shown are incorrect like:
Incremental Backup Not Configured: Incremental backup is not configured. Configuring incremental backup is necessary to make the database purge successful. This will help to avoid disk space issues. View database Size is 0.23GB and size it occupies on the harddisk is 0.23GB.
Purge Configuration Repository not configured: Configure Remote Repository under Purge Configuration which is used to take a backup of data before purge.
Workaround:
As data is purged daily at 4:00 a.m. at the local time zone where the ACS instance that runs the View process is located,configure Incremental Backup schedule at 90 min time gap between Data Purge time.

Incremental Backups are Cumulative Vs Differential??

Dear all,
The followings are Weekly Full Backup and Daily Backup scripts:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
allocate channel ch1 type disk format '/u02/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 0 database plus archivelog delete all input;backup current controlfile;
backup spfile;
release channel ch1;
Daily Backup:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
allocate channel ch1 type disk format '/u02/db/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 1 cumulative database plus archivelog delete all input;delete noprompt obsolete;
delete noprompt archivelog all backed up 2 times to disk;
backup current controlfile;
backup spfile;
release channel ch1;
I will do the full backup on Sunday and daily backup on Mon to Sat.
Scenario 1:
Incremental Backups are cumulative, I need of sunday full backup and tuesday daily backup to restore the database if crash on wednesday.
Scenario 2:
Incremental Backups are differential, then I need of sunday full backup and all incremental backups until crash.
I am wondering which scenario (1 or 2) is for my scripts that I post on above? Because I have different answer from others.
Best Regards,
Amy

Your scripts are following the scenario 1. Incremental backups are by default
differential. Since you are using the keywork CUMULATIVE, it's the 1 scenario.
What made you doubtfull? Scripts are straight forward.......

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,

What are the steps applying incremental backups to standby database 11g

Hi All,
I have built 11g none ASM standby database from ASM RAC Database. Now I want to apply incremental backup to the standby database from primary but not sure how to do it. I tried following and I had an error “ORA-01103: database name 'ins-prim' in control file is not 'ins-sec'”
1- I have configured standby database with RMAN backup.
2- After finishing installation, I took a incremental backup from primary server(ins-prim) and moved incremental backup and control file to the standby (ins-sec) database
3- I stared standby database nomount mode
4- restore controlfile from “incremental backup location in standby database”
5- alter database mount; and got this error
“ORA-01103: database name 'ins-prim' in control file is not 'ins-sec'”
What are the steps applying incremental backups to standby database with 11g?
Thank you

I build the database from backup and changed from ASM to none ASM and changed location of data files and logfiles. I think this changes makes the standby database as logical one.
You can a have a physical standby with different locations for everything (redo/controlfiles/datafiles), ASM and no ASM etc. I have a such a configuration in production (10gR2)
I build the database from backup
Are you sure you have a standby ? Ins-sec receives the archivelog files from the primary ? How did you proceed to build this database ? I suspect you don't have a standby at all ! If you have duplicated the database ins-sec and ins-pri are independent databases and you won't be able to apply an incremental backup (your script was not correct but it is another story)

Restore Tablespace incremental backup is not work as after reimage oracle

TheTablespace incremental backup Restore is not work as after reimage the oracle database or restore tablespace in standby machine(another machine) is not working .its working in the same machine without reimage .after reimage not working please clarify me ,
I need the solution as soon as please reply as soon as .
Commnads used:
This is the step is followed but i am getting backup or control file not found error.Its works i the application server is not reimaged ;
please give your valuable suggestion .
Product Used:oracle 11g in linux environmnet
1)Before taking backup get SCN number for restore.
Command applied: Select current_scn from v$database;
2)running Full backup of database
Command applied:
configure controlfile autobackup on;
backup database plus archivelog;
CROSSCHECK BACKUP;
exit;
3)Running level 0 incremental backup
Before taking backup get SCN number for restore.
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 TAG ='WEEKLY' TABLESPACE TEST;
exit;
3) Running level 1 incremental backup
Before taking backup get SCN number for restore.
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 TAG ='DAILY' TABLESPACE TEST;
4)Before Restore(TSPITR) following procedure are applied under sysdba privilege
Command applied:
SQL 'exec dbms_backup_restore.manageauxinstance ('TSPITR',1)';
5)TSPITR Restore command
Command applied:
run
RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
SQL 'ALTER TABLESPACE TEST ONLINE';
please calrfiy my following question:
1. After reimage(reinstall oracle database with application ).The aboove scenario is not working
2. After fullbackup what are the files needs to copy from (opt/oraclle/base/flash_recovery_area/dbname/) to repository because daily cleanup script will keep the data as sysdate -1 .
For fullbacckup we are currently copying entire (flash_recovery_area/dbname) database folder to repoistory.
3. after incremental backup what are the files needs to copy from (opt/oraclle/base/flash_recovery_area/dbname/..) to repository because daily cleanup script will keep the data as sysdate -1
For incremenatl backup currently we are copying (flash_recovery_area/dbname/backupset/<currentdate> and flash_recovery_area/dbname/autobackup/<currentdate>) folder to repoistory.
4.During restore we are copy entire things from repository to flash_recovery_area finaly apply the above mentioned restore command.
Tabelspace incremenatl restore is possible after reimage application server(fresh database)/another server with same database(standby machine) ....?
If we missing something in backup side please clarify me how to retore the tablespace incremental / level 0 tablespacae after reinstallion of server/another standby server.
Any information please let me know .I need the solution as soon as please reply as soon as .

Try the Recovery Manager (RMAN) instead. This forum is for feedback about the 11g XE Beta.

Production server Incremental Backup is restoring in Testing server

Dear All,
Currently our Production database is running in windows 2003 server , Oracle version is 10.2.0.4.0
Now my question is daily incremental backup of production server will be restored in testing server (same configuration in production server
and testing server ) how can i achieve this .....
Regards,
S.Arun

Hi Oradba,
Thanks for your response. I went through the link and we need this only for testing purpose and not for reporting.
We need to take incremental backup and restore it in testing server. Is it possible to do this without RMAN.(Due to some Business reasons)
Thanks & Regards,
S.Arun

Configuring Rman backups from Enterprise Manager GC.

Greetings,
I am having a difficult time understanding how OEM GC 11g interacts with RMAN and am hoping someone can clarify a couple of things for me. Hopefully I am asking meaningful questions. I can make it work but am unclear as to how it is working.
1) For a particular instance under Availability -> Backup/Recovery -> Setting -> Backup Settings I configure my backup settings for RMAN. Is that analogous to issuing the CONFIGURE command from within RMAN?
2) For a particular instance under Availability -> Backup/Recovery -> Manage -> Schedule Backup There are two choices: Oracle Suggested Backup and Customized backup.
Does each of those choices use the settings defined when I configured backup settings?
Looking at the script generated by the Oracle Suggested Backup it appears that it is a very basic backup. What does it do about archive maintenance after backup.
Thanks
Bill Wagman

Hi,
to answer the questions:
1.) yes, these settings reflect the RMAN configuration settings and are used for the backup jobs that are configured via Grid Control
2.) we are using gric control to configure our backup jobs - we never used the Oracle suggested backups, they seemed to be too simple and less flexible. We preferred to build customized backups. They are easy to configure (some screens to clck through) and provides more flexibility. As an example you can decide to backup archive logs also and to delete then from disk afterwards. Also you can distinguish between full or incremental backups. I think it is uasbel and flexible enough for basic backup strategies.
Regards

ACS incremental backup is OFF

Dear Team,
Incremental backup settings is changing to OFF state and getting below error message in the logs ACS . Please find the attachement.
""""" Aug 31 2014 04:01:21 com.cisco.nm.acs.view.common.incrbackup.IncrBackupJob.execute(IncrBackupJob.java:166) ERROR DefaultQuartzScheduler_Worker-5 Acs.MGMT.ACS
VIEW Incremental Backup: exception java.lang.NullPointerException
        at com.cisco.nm.acs.view.common.incrbackup.IncrBackupUtil.sendSystemAlert(IncrBackupUtil.java:1690)
        at com.cisco.nm.acs.view.common.incrbackup.IncrBackupImpl.executeBackup(IncrBackupImpl.java:457)
        at com.cisco.nm.acs.view.common.incrbackup.IncrBackupJob.execute(IncrBackupJob.java:125)
Sep 01 2014 22:08:21 com.cisco.nm.acs.view.common.incrbackup.XMLExceptionListener.exceptionThrown(XMLExceptionListener.java:44) FATAL DefaultQuartzScheduler_
Worker-9 Acs.MGMT.ACSVIEW Premature end of file.
        at com.cisco.nm.acs.view.common.incrbackup.IncrBackupUtil.getCatalogFromFile(IncrBackupUtil.java:1447)
        at com.cisco.nm.acs.view.common.incrbackup.IncrBackupImpl.executeBackup(IncrBackupImpl.java:286)
        at com.cisco.nm.acs.view.common.incrbackup.IncrBackupJob.execute(IncrBackupJob.java:125)
Sep 01 2014 22:08:21 com.cisco.nm.acs.view.common.incrbackup.IncrBackupImpl.executeBackup(IncrBackupImpl.java:446) ERROR DefaultQuartzScheduler_Worker-9 Acs.
MGMT.ACSVIEW Backup failed: null
Sep 01 2014 22:08:21 com.cisco.nm.acs.view.common.incrbackup.IncrBackupJob.execute(IncrBackupJob.java:166) ERROR DefaultQuartzScheduler_Worker-9 Acs.MGMT.ACS
VIEW Incremental Backup: exception java.lang.NullPointerException
        at com.cisco.nm.acs.view.common.incrbackup.IncrBackupUtil.sendSystemAlert(IncrBackupUtil.java:1690)
        at com.cisco.nm.acs.view.common.incrbackup.IncrBackupImpl.executeBackup(IncrBackupImpl.java:453)
        at com.cisco.nm.acs.view.common.incrbackup.IncrBackupJob.execute(IncrBackupJob.java:125)

Hi Muthuraj,
Can you please try reconfiguring incremental backup. I think as per the logic , the incremental backup is forced to OFF mode when an error is encountered during any of the previous incremental backups. If you are still seeing the same error after re-configuring , I would suggest you to check this issue with TAC , as it is something related to the data that is being backed up.
Thanks

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.

Backup HyperV VMs - incremental backup

Hello,
We are using Windows Server Backup to backup some HyperV VMs. Can we create an incremental backup schedule for VMs? Every night a full backup is being taken.
DPM is not an option in our environment.
Best regards
Kostas
Kostas Backas-Systemgraph Technologies

Hi Kostas,
Sorry for the delay.
After the first full backup is created, you can configure Windows Server Backup to automatically run incremental backups by saving only the data that has changed since the last backup. Even if you choose to always perform full backups, your backup will take
less time than it did in earlier versions of Windows.
For more detailed information, you could refer to the article below:
Optimizing Backup and Server Performance
http://technet.microsoft.com/en-us/library/dd759145.aspx
If you restore a whole VM, you will have to restore a full backup of it.
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Differential Incremental Backup or Incrementally Updated Backup?

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

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

Incremental Backup keep skipping saving pst files

Hi,
Client company uses MS-outlook 2007 and pst files are saved on windows esssentilas 2012 R2 server(ex: h:\outlook\outlook.pst) for backup purposes. We use incremental backup on the server. For some reason the initial full backup runs fine, but
the subsequent backups keep on skipping backing up the pst files as if they were unchanged. The pst files are changed daily and the outlook program is closed before the backup. I used so far Synctoy and backup assist and both do the same .
Thanks for your help

Hi,
Since it's Incremental Backup, I suggest you make sure the .pst file has actually been "modified".
What I mean is, Incremental Backup may consider the file as modified based on the modified time. If the .pst file's last modified timestamp hasn't been changed, the Incremental Backup will consider the file has not been changed and will skip the backup.
By the way, also a reminder, we don't recommend network share hosting of .pst as it always brings unexpected issues.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

BRU incremental Backup Questions/Help

Hello Ladies and Gents,
I'm in desperate need of some help. I purchased Bru Le 1.3.0 about 2 weeks ago and going to use it for the clients Backup Strategy for over 2TB of data.
I used retrospect in the past but retro has been giving them major issues and has been unreliable; therefore the reason to switch to Bru.
Configuration: Xserve/XRAID backing up to Two sets of Lacie Drives 2x 1.8TB striped together = one single 3.6TB drive. One 3.6TB is daily and the Second is a weekly Off-site.
Let me preface this with the understanding that I'm not super savvy with Command-line....
The Goal is to Create incremental daily backup!
I started by creating a Full Backup compression level 1, now I'm trying to change that to an Incremental Backup - But when I try to select the base (which I thought would be the Full Backup I created) - I get an Error "Incorrect Base Definition" -- Which means I did this Wrong.
How do I Correctly create a proper Base Definition for an Incremental Backup?
Thanks
david
XServe - XRAID Mac OS X (10.4.10) Bru LE - 1.3.0
G5 Mac OS X (10.4.10)

Have you run a backup of the datafiles already?
Looking the documentation it says the following:
When using these commands, there must already exist an image copy of every datafile specified in the command. If there are multiple copies of a datafile, the latest one is used. RMAN issues an error if image copies of every datafile in the database or tablespace do not exist.From what you're saying this looks like the case with your backups.
I suggest running a backup of the current datafiles, then running a backup copy and querying RMAN to check the copy exists.
RMAN> List backup;Documenation Link: http://download.oracle.com/docs/cd/B13789_01/server.101/b10734/rcmconc1.htm
Edited by: Kerri_Robberts on Aug 12, 2011 3:58 PM

I am trying to restore my catalog having previously done a back up to an external hard drive and subsequently an incremental backup. I am using Photoshop Elements 11 and the only option given in the restore procedure is to open a .tly file.

I have done this but now the restore function is asking for yet another file, which i assume to be the original back up, but that is the only .tly file since the only other relevant file appears to be called catalog.buc but that is just not visible when using the restore function? How do I continue from here with this restoration of my catalog?

Martin_Had a écrit:
Thank you Andaleeb. I appear to have an old backup of a year ago, and a more recent full back up plus an incremental backup.
Regrettably I don't really understand what is going on because firstly the restore does not complete its cycle so I cannot see what that backup file contains and secondly all I have read would suggest that the .tly file is the full backup and the catalog.buc file is the incremental backup. For the present, the catalog shows the photos for 2014 which makes me think I might have backed from the old back up file.
I am minded to create another catalog and try again.
Any views on what I can do?
A backup (full or incremental) is a folder, not a file. It contains renamed pictures file copies as well a copies of the files and subfolders of the original catalog. The catalog.buc is a renamed copy of the database of your original catalog while the backup.tly. That backup.tly file contains the information to restore the renamed pictures where you decide, the original location or a new custom one. You can't do anything with the backup yourself, only the restore process can do the job if it finds the backup.tly file. In the case of an incremental backup, you have to tell the restore process where to find the incremental backup folder; it finds the backup.tly file in that folder and finds what is to restore there; then it asks you for the previous backup folder (in your case the full backup); you then browse to that full backup folder so that the restore process can find find the backup.tly there; the restore then deals with the rest of the files to restore.

Configuring Incremental Backup

Similar Messages

Maybe you are looking for