RMAN via OEM: Skipping days with incremental backups
Hello,
I've searched the forums and browsed much of the documentation on OTN but have not found the answer to my question. I am using RMAN (through Oracle Enterprise Manager) to schedule backups. I want to get full database backups on Fridays and incrementals Monday through Thursday. I would like to have the backups running at 11 PM each night. I have scheduled the full database backups to occur every Friday. The problem is I cannot schedule the incrementals to skip Fridays, Saturdays and Sundays. I don't want incrementals on Friday since the full database backup will be running. No transactions are occurring on Saturday or Sunday so there is no need to backup on those days either.
Thank you for any help,
Paul Lohr
You have had issues with FileID 74 earlier
[RMAN] problem with registering database
DATAFILE RECOVER STATUS
and now with FileID 75 ?
Bring in Oracle Support. Log an SR. Ask for ACS onsite. Don't use forums.oracle.com for such issues.
Hemant K Chitale
Edited by: Hemant K Chitale on Feb 11, 2011 10:49 AM
Similar Messages
-
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
Hi,
DB:9.2.0.8
OS: AIX 5.3
I am restoring DB with until time(12/06/2012) for needed tablespaces.
I restored the 12th date controlfile ,which is backed up with archivedlogs. I also have one more controlfile which backed up with full DB..
Restore of tablespaces are completed..
When recovery is going , failed with following error..
allocated channel: c7
channel c7: sid=22 devtype=SBT_TAPE
channel c7: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
allocated channel: c8
channel c8: sid=21 devtype=SBT_TAPE
channel c8: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
executing command: SET until clause
Starting recover at 23-06-2012 02:00:15
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
released channel: c6
released channel: c7
released channel: c8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/23/2012 03:36:57
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
RMAN>
Restore Script:
connect target /
connect catalog rmanc/recom@lgn_rmanc
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
allocate channel c9 type 'SBT_TAPE';
allocate channel c10 type 'SBT_TAPE';
allocate channel c11 type 'SBT_TAPE';
allocate channel c12 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
release channel c9;
release channel c10;
release channel c11;
release channel c12;
Recover Script:
connect catalog rmanc/recom@lgn_rmanc
connect target /
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
recover tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
Any suggestion in this is helpful to me..
Thanks in advance,Hello;
I read your post and here's the thoughts that came to mind : ( my largest concern is you might restore something that damages your current system )
1. So you want to restore the whole DB back to 12/06/2012 to get some tablespaces from then right?
2. Are you restoring to a different system?
3. How did you start the database ( NOMOUNT, MOUNT )
4. If you are restoring the whole DB back to 12/06/2012 how did you restore the control file?
5. Your command shows :
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
COMMENT : Generally I use recover tablespace for point in time recovery and use an auxilary destination.
Meaning I don't use restore at all, in fact using restore may cause an issue.
SUMMARY : I don't see how this will work as is.
It seems you want data from five tablespaces from about six months ago including the SYSTEM tablespace.
This is an Incomplete Recovery. I believe I would rethink this completely.
Give the time that has past I would consider restoring the whole database to a different server where cannot damage anything.
Once this is done I would decide how to get the data I need.
Or I would check for a daily export file and recover the tablespace data that way.
So you have some good details on your question but it seems the plan is either missing something or you need to add a few more details.
Example
I'm recovering old tablespaces into a test system.
Here's how I'm not damaging my current production system.
I don't have an export from that date.
So take a step back and either rethink or give a few more details on how this is safe.
Best Regards
mseberg -
RMAN-06067: RECOVER DATABASE required with a backup or created control file
Hi,
Oracle version :10.2.04
I recovered control files
RMAN> restore controlfile to '/oracle/ora10gr4/dbs/nis.ctl';
Starting restore at 21-AUG-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: restoring control file
output filename=/oracle/ora10gr4/dbs/nis.ctl
channel ORA_DISK_1: reading from backup piece /data_idx1/ORAMIG/OMIGTEST/cfc-260103938-20120821-03
channel ORA_DISK_1: restored backup piece 1
piece handle=/data_idx1/ORAMIG/OMIGTEST/cfc-260103938-20120821-03 tag=TAG20120821T152259
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
Finished restore at 21-AUG-12after this i got the below error when i tried to open DB.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1:
'/data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf'So i tried the following.
RMAN> restore datafile '/data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf';
Starting restore at 21-AUG-12
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 /data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf
channel ORA_DISK_1: reading from backup piece /data_idx1/ORAMIG/OMIGTEST29_1_791910787
channel ORA_DISK_1: restored backup piece 1
piece handle=/data_idx1/ORAMIG/OMIGTEST29_1_791910787 tag=TAG20120821T151306
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 21-AUG-12
RMAN> recover datafile '/data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf';
Starting recover at 21-AUG-12
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/21/2012 16:21:45
RMAN-06067: RECOVER DATABASE required with a backup or created control fileCan anyone pls help me with this error?
ThanksHi,
Try this command after restore control file.
RMAN> restore database;
RMAN> recover database;
RMAN> alter database open resetlogs;Paste here result, if you are get error.
Regards
Mahir M. Quluzade
www.mahir-quluzade.com -
Apply problem after sync with incremental backup
Hello all,
I have primary as rac with 4 nodes and one physical (all have asm)
I made incremental backup to re-sync my primary with physical standby and when i tried to start DG process the shiping is working but apply not workin : check please :
THREAD#,Last Standby Seq Received
1,29598
2,22308
3,27230
4,21868
THREAD#,Last Standby Seq Applied
1,28634
2,21227
3,25780
4,21104
when i run apply command i see in alert log file this :
Media Recovery Waiting for thread 4 sequence 1
Fetching gap sequence in thread 4, gap sequence 1-100
Tue Apr 07 12:06:49 2015
FAL[client]: Failed to request gap sequence
GAP - thread 4 sequence 1-100
DBID 1722434320 branch 849356882
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that's sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
the system searching for gab started with seq 1 in node 4 !!!!
how can i deal with that please ??Thanks Stefan , kindly find below the output for both primary and standby :
1- select NAME,RESETLOGS_CHANGE#, CHECKPOINT_CHANGE#,CONTROLFILE_CHANGE#,CURRENT_SCN,RECOVERY_TARGET_INCARNATION# from v$database
Primary :
ORACLE,925702,3231069178,3231935937,3231937322,2
Standby :
ORACLE,925702,3096376393,3096507373,3096507372,2
2- list incarnation
Primary :
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ORACLE 1722434320 PARENT 1 24-AUG-13
2 2 ORACLE 1722434320 CURRENT 925702 04-JUN-14
Standby:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ORACLE 1722434320 PARENT 1 24-AUG-13
2 2 ORACLE 1722434320 CURRENT 925702 04-JUN-14
3- select FILE#,RESETLOGS_CHANGE#,RESETLOGS_TIME, CHECKPOINT_CHANGE#,CHECKPOINT_TIME from v$datafile_header;
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
1 925702 04-JUN-14 3231779881 08-APR-15
2 925702 04-JUN-14 3231779881 08-APR-15
3 925702 04-JUN-14 3231779881 08-APR-15
4 925702 04-JUN-14 3231779881 08-APR-15
5 925702 04-JUN-14 3231779881 08-APR-15
6 925702 04-JUN-14 3231779881 08-APR-15
7 925702 04-JUN-14 3231779881 08-APR-15
8 925702 04-JUN-14 3231779881 08-APR-15
9 925702 04-JUN-14 3231779881 08-APR-15
10 925702 04-JUN-14 3231779881 08-APR-15
11 925702 04-JUN-14 3231779881 08-APR-15
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
12 925702 04-JUN-14 3231779881 08-APR-15
13 925702 04-JUN-14 3231779881 08-APR-15
14 925702 04-JUN-14 3231779881 08-APR-15
15 925702 04-JUN-14 3231779881 08-APR-15
16 925702 04-JUN-14 3231779881 08-APR-15
17 925702 04-JUN-14 3231779881 08-APR-15
18 925702 04-JUN-14 3231779881 08-APR-15
19 925702 04-JUN-14 3231779881 08-APR-15
20 925702 04-JUN-14 3231779881 08-APR-15
21 925702 04-JUN-14 3231779881 08-APR-15
22 925702 04-JUN-14 3231779881 08-APR-15
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
23 925702 04-JUN-14 3231779881 08-APR-15
24 925702 04-JUN-14 3231779881 08-APR-15
25 925702 04-JUN-14 3231779881 08-APR-15
26 925702 04-JUN-14 3231779881 08-APR-15
27 925702 04-JUN-14 3231779881 08-APR-15
28 925702 04-JUN-14 3231779881 08-APR-15
29 925702 04-JUN-14 3231779881 08-APR-15
29 rows selected.
Standby:
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
1 925702 04-JUN-14 3065328471 25-MAR-15
2 925702 04-JUN-14 3065328464 25-MAR-15
3 925702 04-JUN-14 3065328464 25-MAR-15
4 925702 04-JUN-14 3065328461 25-MAR-15
5 925702 04-JUN-14 3065328471 25-MAR-15
6 925702 04-JUN-14 3065328471 25-MAR-15
7 925702 04-JUN-14 3065328461 25-MAR-15
8 925702 04-JUN-14 3065328471 25-MAR-15
9 925702 04-JUN-14 1016743 04-JUN-14
10 925702 04-JUN-14 1020278 04-JUN-14
11 925702 04-JUN-14 1020681 04-JUN-14
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
12 925702 04-JUN-14 1021083 04-JUN-14
13 925702 04-JUN-14 1021086 04-JUN-14
14 925702 04-JUN-14 1021877 04-JUN-14
15 925702 04-JUN-14 1021880 04-JUN-14
16 925702 04-JUN-14 1021883 04-JUN-14
17 925702 04-JUN-14 1021886 04-JUN-14
18 925702 04-JUN-14 1031089 04-JUN-14
19 925702 04-JUN-14 1031555 04-JUN-14
20 925702 04-JUN-14 1032064 04-JUN-14
21 925702 04-JUN-14 1032525 04-JUN-14
22 925702 04-JUN-14 1032922 04-JUN-14
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
23 925702 04-JUN-14 1033338 04-JUN-14
24 925702 04-JUN-14 1033731 04-JUN-14
25 925702 04-JUN-14 1034126 04-JUN-14
26 925702 04-JUN-14 90283375 09-JUL-14
27 925702 04-JUN-14 90291448 09-JUL-14
28 925702 04-JUN-14 3065328471 25-MAR-15
29 925702 04-JUN-14 3065328461 25-MAR-15
29 rows selected.
4- select name,CHECKPOINT_CHANGE#,CHECKPOINT_TIME, UNRECOVERABLE_CHANGE# ,UNRECOVERABLE_TIME from v$datafile
Prmairy :
NAME
CHECKPOINT_CHANGE#
CHECKPOINT_TIME
UNRECOVERABLE_CHANGE#
UNRECOVERABLE_TIME
+ASM_ORADATA/oracle/datafile/system.274.849356797
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/sysaux.260.849356797
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs1.263.849356799
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/users.269.849356799
3232100160
04/08/2015 10:07:12
404,796,458
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/example.272.849356895
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs2.262.849357043
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs3.261.849357043
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs4.267.849357045
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/asd01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/dev01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/feed01.dbf
3232100160
04/08/2015 10:07:12
404,790,786
08/25/2014 22:36:42
+ASM_ORADATA/oracle/datafile/indx01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/indx02.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website02.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website03.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website04.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/users01.dbf
3232100160
04/08/2015 10:07:12
404,796,505
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users02.dbf
3232100160
04/08/2015 10:07:12
404,796,502
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users03.dbf
3232100160
04/08/2015 10:07:12
404,796,499
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users04.dbf
3232100160
04/08/2015 10:07:12
404,796,496
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users05.dbf
3232100160
04/08/2015 10:07:12
404,796,493
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users06.dbf
3232100160
04/08/2015 10:07:12
404,796,490
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users07.dbf
3232100160
04/08/2015 10:07:12
404,796,487
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users08.dbf
3232100160
04/08/2015 10:07:12
404,796,505
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/feed02.dbf
3232100160
04/08/2015 10:07:12
134,340,010
07/16/2014 22:06:21
+ASM_ORADATA/oracle/datafile/indx03.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/system_2_01
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/catalog01
3232100160
04/08/2015 10:07:12
0
Standby :
NAME
CHECKPOINT_CHANGE#
CHECKPOINT_TIME
UNRECOVERABLE_CHANGE#
UNRECOVERABLE_TIME
+DATA/oracledrs/datafile/system.3248.875795981
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/sysaux.3244.875796111
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/undotbs1.3249.875796547
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/users.3255.875796621
3096432811
03/30/2015 07:55:20
404,796,458
08/25/2014 22:36:50
+DATA/oracledrs/datafile/example.3258.875796817
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/undotbs2.3256.875796823
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/undotbs3.3253.875796869
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/undotbs4.3247.875797223
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/asd01.dbf
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/dev01.dbf
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/feed01.dbf
3096432813
03/30/2015 07:55:21
404,790,786
08/25/2014 22:36:42
+DATA/oracledrs/datafile/indx01.dbf
3096432803
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/indx02.dbf
3096432803
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/website01.dbf
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/website02.dbf
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/website03.dbf
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/website04.dbf
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/users01.dbf
3096432811
03/30/2015 07:55:20
404,796,505
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users02.dbf
3096432803
03/30/2015 07:55:20
404,796,502
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users03.dbf
3096432803
03/30/2015 07:55:20
404,796,499
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users04.dbf
3096432814
03/30/2015 07:55:21
404,796,496
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users05.dbf
3096432813
03/30/2015 07:55:21
404,796,493
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users06.dbf
3096432803
03/30/2015 07:55:20
404,796,490
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users07.dbf
3096432811
03/30/2015 07:55:20
404,796,487
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users08.dbf
3096432814
03/30/2015 07:55:21
404,796,505
08/25/2014 22:36:50
+DATA/oracledrs/datafile/feed02.dbf
3096432813
03/30/2015 07:55:21
134,340,010
07/16/2014 22:06:21
+DATA/oracledrs/datafile/indx03.dbf
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/system_2_01
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/catalog.288.873258217
3096432811
03/30/2015 07:55:20
0
Thanks in advance, -
Restore using incremental backup with noarchivelog mode
Hello experts,
We are running SAP on Oracle databse(IN NOARCHIVELOG MODE) for which we are having full offline backup on every sunday and post which incremental backups on rest of the days. We have scenario to do restore db to the state till last friday's incremental backup.
Please let us know the procedure for restoring till that point. If possible using brtools utility(which is SAP specific).
Thank You
Regards,
VenkateshwarIf you do not want to read the whole doc This is the snippet for you.
Recovering a NOARCHIVELOG Database with Incremental Backups
Restoring a database running in NOARCHIVELOG mode is similar to restoring a database in ARCHIVELOG mode. The main differences are:
Only consistent backups can be used in restoring a database in NOARCHIVELOG mode.
Media recovery is not possible because no archived redo logs exist.
You can perform limited recovery of changes to a database running in NOARCHIVELOG mode by applying incremental backups. The incremental backups must be consistent, like all backups of a database run in NOARCHIVELOG mode, so you cannot make backups of the database when it is open.
When you are recovering a NOARCHIVELOG database, specify the NOREDO option on the RECOVER command to indicate that RMAN should not attempt to apply archived redo logs. Otherwise, RMAN returns an error.
To recover a NOARCHIVELOG database with incremental backups:
After connecting to the target database and the recovery catalog, place the database in a mounted state:
STARTUP FORCE MOUNT
Restore and recover the database.
For example, you can perform incomplete recovery with the following commands:
RESTORE DATABASE
FROM TAG "consistent_whole_backup";
RECOVER DATABASE NOREDO;
Open the database with the RESETLOGS option.
For example, enter the following command:
ALTER DATABASE OPEN RESETLOGS; -
How to restore using increment backup after full backup restore in RMAN?
Hi All,
We have a files of full backup of database after turning on the Archive log.
And after that, daily incremental backup is taken.
Now, i want to restore the the database into a new machine using both files of full and incremental backups. Can anybody give me script for restore of full backup and after that restore of incremental backup?
Thanks,
Praveen.Praveen,
>>
In my case, i have 2 sets of backups. One is full backup and other is incremental backup. In order to keep the restored database upto date, i need to restore the full backup and then restore incremental backup. Now, i got any idea how to restore using full backup. My doubt is how to update the restored database with incremental backup also?
>>
Restore always looks for level 0 backup, not the incremental backups.
Incremental backups comes in picture during recovery.
During Recovery, Oracle looks for incremental backups, if exists, it will do the recovery with the incremental backups, if no incremental backups available, then, it will look for archived logs.
Therefore, incremental backups never used during restore, they are used only during the recovery.
Jaffar -
Hi,
I am trying to backup the dev and uat database to FRA using RMAN incremental backup option. The script is
# ~~~~~ start RMAN cold backup ~~~~~ #
rman target / nocatalog log=${LOG_FILE} <<EOF
run {
crosscheck backup;
crosscheck archivelog all;
delete noprompt expired backup;
delete noprompt obsolete;
delete noprompt expired archivelog all;
recover copy of database tag "img_cpy_incr_bkp" until time 'SYSDATE-2';
BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG "img_cpy_incr_bkp" DATABASE;
exit;
EOF
Ok so from what I understand is that with this stratergy,
on day one RMAN will not find any level 0 bkp so it will do a full backup.
day 1, incremental backup
day 2, incremental backup again
day 3, incremental backup will be merged to level 0 bckp and day 0 bkp will be useless.
day 4, incremental backup will be merged to day 1 backup making day 1 backup as level 0.
day 5, incremental backup will be merged to day 2 backup making day 2 backup as level 0.
day 6, incremental backup will be merged to day 3 backup making day 3 backup as level 0.
Is that correct >>?? if so, then should I rerun the level 0 backup again on sunday ??? or should I keep on running this scrip.Hi Dalji,
The size of the db is about 7 GB. I ran the script so as this is for the first time, should RMAN not do a level 0 backup ?? The following is the output of the script '
Starting backup at 28-SEP-07
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
channel ORA_DISK_1: starting incremental level 1 datafile backupset channel ORA_DISK_1: specifying datafile(s) in backupset input datafile fno=00006 name=/u05/oradata/jerry1/jerry1_data_002.dbf
input datafile fno=00001 name=/u05/oradata/jerry1/system01.dbf
input datafile fno=00008 name=/u05/oradata/jerry1/jerry1_indx_002.dbf
channel ORA_DISK_1: starting piece 1 at 28-SEP-07
channel ORA_DISK_2: starting incremental level 1 datafile backupset channel ORA_DISK_2: specifying datafile(s) in backupset input datafile fno=00009 name=/u05/oradata/jerry1/jerry1_data_003.dbf
input datafile fno=00002 name=/u05/oradata/jerry1/undotbs01.dbf
input datafile fno=00007 name=/u05/oradata/jerry1/jerry1_indx_001.dbf
channel ORA_DISK_2: starting piece 1 at 28-SEP-07
channel ORA_DISK_3: starting incremental level 1 datafile backupset channel ORA_DISK_3: specifying datafile(s) in backupset input datafile fno=00005 name=/u05/oradata/jerry1/jerry1_data_001.dbf
input datafile fno=00003 name=/u05/oradata/jerry1/sysaux01.dbf
input datafile fno=00004 name=/u05/oradata/jerry1/users01.dbf
channel ORA_DISK_3: starting piece 1 at 28-SEP-07
channel ORA_DISK_1: finished piece 1 at 28-SEP-07
piece handle=/u04/flash_recovery_area/jerry1/backupset/2007_09_28/o1_mf_nnnd1_TAG20070928T150923_3hs348dw_.bkp tag=TAG20070928T150923 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:02:46 channel ORA_DISK_2: finished piece 1 at 28-SEP-07 piece handle=/u04/flash_recovery_area/jerry1/backupset/2007_09_28/o1_mf_nnnd1_TAG20070928T150923_3hs348t0_.bkp tag=TAG20070928T150923 comment=NONE channel ORA_DISK_2: backup set complete, elapsed time: 00:02:46 channel ORA_DISK_3: finished piece 1 at 28-SEP-07 piece handle=/u04/flash_recovery_area/jerry1/backupset/2007_09_28/o1_mf_nnnd1_TAG20070928T150923_3hs34khn_.bkp tag=TAG20070928T150923 comment=NONE channel ORA_DISK_3: backup set complete, elapsed time: 00:02:45 Finished backup at 28-SEP-07
Starting Control File and SPFILE Autobackup at 28-SEP-07
piece handle=/u04/flash_recovery_area/jerry1/autobackup/2007_09_28/o1_mf_s_634489931_3hs39f2n_.bkp comment=NONE Finished Control File and SPFILE Autobackup at 28-SEP-07
When I chech FRA, the
87M backupset
11M block_change_tracking
7.2M autobackup
1K onlinelog
1K datafile
1K archivelog
$ cd backupset
$ cd 2007_09_28
$ ls
39M Sep 28 15:12 o1_mf_nnnd1_TAG20070928T150923_3hs34khn_.bkp
39M Sep 28 15:12 o1_mf_nnnd1_TAG20070928T150923_3hs348t0_.bkp
9.5M Sep 28 15:12 o1_mf_nnnd1_TAG20070928T150923_3hs348dw_.bkp
The whole backupset folder is only 87M. should it not be about 7G ???? -
Restore incremental backup with rman
Dear Friends
can u tell me how to restore an incremental backup with rman? i backup my rman with statement below :
1. backup full database format '/oracle/PRD/sapbackup/%U';
the results was :
-rw-r----- 1 oraprd dba 19006996480 Jun 10 12:08 0ojiit4n_1_1
-rw-r----- 1 oraprd dba 12746752 Jun 10 12:08 0pjiiu6b_1_1
2. after that i do incremental backup :
backup incremental level 1 cumulative database format '/oracle/PRD/sapbackup/%U';
the results was :
-rw-r----- 1 oraprd dba 173400064 Jun 10 13:44 0ujij2k0_1_1
-rw-r----- 1 oraprd dba 12746752 Jun 10 13:44 0vjij3qc_1_1
what statement i need to run for restore the incremental backup?run{
ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
RESTORE DATABASE;
RECOVER DATABASE;
The above command will restore your database from the last good RMAN backup. Your last backup is incremental level backup as you posted. The above command will fullfill your requirements -
RMAN Recovery Window 7 days setting - shows no obsolete backups
Hi All. Quick question about RMAN retention policy....
I have the current backup strategy:
Full backup (0) -> Sunday
Incremental backup (1) -> Monday - Saturday
Archive log backups -> every hour
This is a new database I just started taking backups on last month. (1st full backup was run October 4th)
I currently have not deleted any of them.
The old RMAN RETENTION POLICY was set to REDUNDANCY = 1
REPORT OBSOLETE lists all of them up to the last full which ran this past Sunday (Nov 1st)
I just switched the RMAN RETENTION POLICY to RECOVERY WINDOW of 7 DAYS
REPORT OBSOLETE lists no backups obsolete...
Shouldn't I see all the backups prior to a week ago or does it only take affect for backups run under the new policy?
Any help/replies are apprecitaed.
ThanksRan crosscheck with no problems:
Crosschecked 200 objects
But still same results for:
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
no obsolete backups found
Am I missing something here? Or like I mentioned is this expected behaviour because all of my other backups were run with REDUNDANCY = 1 retention policy?
Thanks -
RMAN backup with smallest backup size
Oralce 11g2 on Redhat 5. The diskspace is our tightest resource, and we want to an incremental backup with level0 on Sunday and level 1 every week days and Saturday. I am to use the comamnds to do the job--Sunday
backup incremental level 0 tag 'level_0' database plus archivelog;
--Other days
backup incremental level 1 database plus archivelog delete all input;I do not think this is the best practice nor produce smallest backup files.
What are you comments and opinions. ThanksPavan, Thank you for reply. Here are the info requested
what is size of DB ??
~250GB, including UNDO and TEMP. It is a dev database and not very big. But we have total 800GB disk space. After setting some housekeeoing folders, and allow some space for data growth, it leaves 180GB for flash_recovery_area.
what would be max size of archive logs generated per day ??
Variable from less than 1 GB to 12 GB
Are you taking backups to tape or Disk ??
Disk. In the 180GB flash_recovery_area, Current backup size is 152GB. If a backup fails to delete obsolete files, the next backup will fill the flash_recovery_area.
Provide the Rman configuration information ??
RMAN> show all;
RMAN configuration parameters for database with db_unique_name TDEV2 are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 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 MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_tdev2.f'; # default -
Rman optimization conflicting with obsolete backups?
Hello,
Suppose I have the following configuration.
I have a partitioned table with each (month-)partition on a different tablespace. I need to keep 10yrs of data. Switch a tablespace with e.g. April2008 data to read-only.
Rman set REDUNDANCY 1 and OPTIMIZATION ON.
Now redundancy 1 should keep only 1 backup of each file wouldn't it?
I do a backup database: it backups every file.
I do a backup database again: it backups every file again.
I do a backup database third time: it says "skipping file n allready backed up 2 times".
Now I do a report obsolete: it marks one of the backups op my file with April2008 data as obsolete.
After performing a delete obsolete, it is gone.
Next day I do a backup database: it backups every file again, so I have two!! backups of file n.
I would like to have only 1 and just 1 backup of the file, and it should never be backed up anymore. The redundancy cannot be set to zero.
How to deal with this?I think we disagree on this. I can make a single-partition rman backup if:
It is on it's own tablespace, on it's own datafile. No problem with that. It is only the redundancy-problem I have.
Even if I configure redundancy to 1, it makes two backups, and one of these is obsolete. This obsolete gets deleted in a 'delete obsolete' action, and a new obsolete will be created with the next backup.
How would you backup the database with 120 partitions as I described above? Each day a full backup?? -
Incremental backup and recover with UNTIL SCN options.
Hi there
My question is just about internal RMAN mecanisms.
Suppose i've cumulative method for backup with RMAN.
Reference backup provided by Level 0 (by night)
after that i've file001.arc, file002.arc during day
Baclup cumulative Level 1 (by night)
after that i've file003.arc, file004.arc, file005.arc during day
Baclup cumulative Level 1 (by night)
after that i've file006.arc, file007.arc, file008.arc, file009.arc, file010.arc, file011.arc during day
Baclup cumulative Level 1 (by night)
after that i've file012.arc, file013.arc during day
Baclup cumulative Level 1 (by night)
Suppose we need to recover with UNTIL SCN ... (incident can be identied by SCN #nnnnn, suppose SCN near of file008.arc).
Is Rman use benefits of incremental, or in this case (need to recover before particular SCN) systematically start with Reference backup (Created by Incremental Level 0) and then file001.arc, file002.arc ....
Platform:Oracle 10g
Regards
DenYou recover using backup controlfile when you have lost the controlfile - should be obvious.
You recover until cancel when, for example, you want to manually see the archive logs being applied and decide when to stop recovering (maybe you have lost the archive log backups and want it to stop when you don't have any more left to apply). -
Restoring the DB with Online and incremental backup's
Dear Experts,
We are planning for a backup strategy on our Production system as below using BRTOOLS with RMAN - " Weekly Full Online Backup and Incremental backup on the remaining days'
We need to test this before implementing it on Production system, could someone please help me with the step-step procedure/documentation for restoring the DB using "an online backup, incremental backup's and redo logs " and prerequisites if any??
Many Thanks !!
Regards,
SriHi Sri,
please have a look at the following
http://help.sap.com/saphelp_nw70/helpdata/en/0d/d3077b4a0c11d182b80000e829fbfe/content.htm
https://help.sap.com/saphelp_nwmobile711/helpdata/en/47/18cb034de863efe10000000a114a6b/content.htm
Best Regards
Marius -
RMAN weekly full backup and daily incremental backup script.
Hallo! I would like to implement an Oracle 10g database backup policy where every Sunday night at 10 pm, a hot full compressed database backup is done, for every other day i.e. Monday to Saturday, a daily incremental compressed backup is done also at 10 pm.
If anyone as an RMAN script that can perform such a backup, please provide me with it.
Thanks.4joey1 wrote:
Hallo! I would like to implement an Oracle 10g database backup policy where every Sunday night at 10 pm, a hot full compressed database backup is done, for every other day i.e. Monday to Saturday, a daily incremental compressed backup is done also at 10 pm.
If anyone as an RMAN script that can perform such a backup, please provide me with it.
Thanks.I would suggest you to try it by your own
Use DBMS_SCHEDULER or cron job (I hope you're using Linux) to create a schedule which invokes rman script to take backup you want
Try it and we'll help you
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime"
Kamran Agayev A.
Oracle ACE
My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/ -
Hi,
I am re-posting a question from the following page here as I have the same problem now and I can't seem to find the answer even though the question has been marked as solved: http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/daff108b-effa-4dad-807a-d604345975dd
Below is a copy of the question:
I have 2 backup drives, (Backup Drive 1 and Backup Drive 2)
Lets assume I have never performed a backup, so Day 1 is the first backup of the server.
Backup Drive 1 connected on Day 1 it performs a FULL Backup - this is expected.
Backup Drive 1 connected on Day 2 it performs an INCREMENTAL Backup - this is expected.
Backup Drive 2 connected on Day 3 it performs a FULL Backup - this is expected.
Backup Drive 1 connected on Day 4 it performs a FULL Backup - WHY? my understanding is that is should perform an Incremental Backup from Day 2
Backup Drive 2 connected on Day 5 it performs a FULL Backup - again why is it not performing an Incremental Backup from Day 3?
This means that in normal operation (Backup Drives alternate every day) We are performing FULL Backups everyday. In a few months this wont be an acceptable backup strategy; it will take too long.
I've used 'Configure Performance Settings' in the Windows Server Backup mmc to specify 'Always perform incremental backup' - it makes no difference.
If I look at the Backup Drive Disk Usage details it confuses me even more. It may be performing Full Backups everyday but it's definitely not storing Full Backup copies on the Backup Drives.
It seems to be that even when a Full Backup is performed, only the deltas are written to the Backup Drive so even though it takes longer it has the same effect as an incremental (so why doesn't it just perform an incremental?)
I don't understand Microsoft's use of Full and Incremental, it seems obtuse to provide a choice that appears to have no effect on the actual data written to the Backup Drive.
My real-world experience is at odds with that statements made in
The Official SBS Blog it states "every backup is incremental from a storage point of view" as well as "Because the wizard schedules differential-based backups' (nowhere in the Backup mmc have I seen any reference or options for differential),
"Backup runs quickly" and "...works the same for multiple disk rotation." (This is simply not the case with a 2-disk rotation. It runs a lengthy FULL Backup every time.)
The backup has been configured using SBS Console, runs once a day at 16:00. 2 Backup Drives, alternating daily.
Can anyone clarify Windows Backup operation for me?
I'd appreciate any feedback at all, thanks.Optimizing Backup and Server Performance
(Windows Server 2008 R2)
http://technet.microsoft.com/en-us/library/dd759145.aspx
Even if you choose the option to create incremental backups, Windows Server Backup will create a full backup once every 14 days, or after 14 incremental backup operations, to reduce the risk from disk corruptions.
Of course, this is for R2.
Merv Porter [SBS-MVP]
============================
"Merv Porter [SBS-MVP]" wrote in message
news:a1ca618e-ad66-4770-8c39-21285a08f671...
Interesting post...
WBAdmin to remote backup server
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/764fe9a4-960e-4e90-b8fb-8e7581752a9d#520f38fe-149c-4424-9c0b-54695297e919
In Windows Server 2008, there are several reasons which may cause the backup to be full instead of incremental
1. Backup on the target is deleted/not present.
2. Source volume snapshot is deleted, from which the last backup was taken.
3. 7 days have passed or 6 incremental backups have happened since the last full backup.
4. Churn on the backup source is high (more than 50%)
Abhinav Mathur[MSFT] Microsoft
Merv Porter [SBS-MVP]
============================
"Les Connor [SBS-MVP]" wrote in message
news:0053cd83-75d1-4dbc-8182-ae67cadf4780...
I believe it's how backup is designed, as I see the same thing. Why it works
the way it does is another story though, I don't know the answer to that.
Les Connor [SBS MVP]
"Kurni" wrote in message
news:[email protected]...
> Hi Les,
>
> Thank you for your reply.
>
> Are you saying that that's how the backup is designed? What I (and the
> original poster of the question) have in mind is actually different (each
> disk should have their own base backup).
>
> Quoting from the original question:
>
> Backup Drive 1 connected on Day 1 it performs a FULL Backup - this is
> expected.
> Backup Drive 1 connected on Day 2 it performs an INCREMENTAL Backup - this
> is expected.
> Backup Drive 2 connected on Day 3 it performs a FULL Backup - this is
> expected.
> Backup Drive 1 connected on Day 4 it performs a FULL Backup - WHY? my
> understanding is that is should perform an Incremental Backup from Day 2
> Backup Drive 2 connected on Day 5 it performs a FULL Backup - again why is
> it not performing an Incremental Backup from Day 3 ?
> Please let me know if I actually misunderstand how windows server backup
> work.
>
MVP - SBS
Maybe you are looking for
-
How to create a custom home screen icon for your website and where to upload it
I created a joomla 3 site used Icon Slate to size icon but know where to upload the icons. Right now when a user goes to "Add to Home Screen" It just uses a copy of the page they are on.
-
Can you use a external hard drive to keep all your iTunes info on it
Can you use a external hard drive to keep all your iTunes info on it
-
When Nokia C3 Touch and Type will launch in India
Hi, I'm eager to buy Nokia C3 Touch and Type model. In website it says coming soon. I want to know when it will launch in India, particularly in Bangalore(Karnataka).And also suggest me my choice is right or that model have any defect. Thanks in
-
I have updated my iphone with the current software but it is showing you need to connect to of itunes to activate your phone, when i did that it is continuously showing an error.please help me to get through. Kindly Activate my phone.
-
Photosmart c4780 will not print in color
Brand new to forums... I am using a MacBook Pro, OS 10.6.8. I recently bought a used photosmart c4780. The owner said it only prints black. When I set everything up, it wouldn't print at all, as the black ink was depleted. I replaced the black cartr