We are trying to restore a database on the different server using RAM incremental level 0 and 1 backups. We have weekly Incremental level 0 backups along with incremental backups on daily basis. During recovery of Incremental level 0 backup, RMAN is expecting/looking for Incremental Level 0 backup of prior week as well. Is this the usual process for RMAN to look for prior level 0 backup though we need to restore from the current level 0 backup and roll forward by a week with subsequent Level 1 backup.?
We intend to restore from the Level 0 of 1/16 and roll forward with daily incrementals till 1/22. RMAN is expecting level 0 backupsets from 1/9 backup as well and keep failing since those backups are not available. quick inputs since we are in middle of recovery and trying to resolve if this is even doable.
Can you take an incremental backup level 1 or level 0 without archivelogs?
syntax would bebackup as compressed backupset cummulative level 1 database.
The reason I ask is because when I run backup as compressed backupset cummulative level 1 database plus archivelogs # it runs fine, but when I run backup as compressed backupset cummulative level 1 database it just hangs.
I am tryign to run a split onlike full backup from the os useign the sap command which is linked to rman..Command that i am useing is ...
brbackup -u / -c force -t online_split -m full -p initBR1_onlinefull.sap
The backup goes thru but i get this erro on the end...
BR0522I 57 of 57 files/save sets processed by RMAN BR0280I BRBACKUP time stamp: 2011-01-26 12.23.26 BR0505I Full database backup (level 0) using RMAN successful BR0280I BRBACKUP time stamp: 2011-01-26 12.23.28
[code]...
Copyright (c) 1982, 2007, Oracle. All rights reserved.
I have main database Server which is located on Server A, now I have to take the RMAN Backup of Server A and then shift the complete database on new Server B.
I am confused whether to use Backup command with AS COPY option or take the backup as backup sets. Which are the best option that I can use for the RMAN Backup.
I've a little question : Is it possible to use RMMAN to backup 2 tables incrementally ? I don't want to backup all the database but only these 2 tables.
I use kill -9 <pid> and kill the job and then i check ps -ef | grep rman and get no process of RMAN but when i login into Enterprise Manager and click on performance tab so i see the graph of RMAN (yellow in colour) which is still continue and means the RMAN backup is in progress , then i checked the top consumer page so there i see backup incr datafile(SYS$USERS)(26.8%), so i want to down this RMAN backup.i also used the this query to check the RMAN job running or not
select * from V$SESSION where MODULE like 'rman%'; it came up with no rows
7 of days ago Full backup has been taken to disk due to issues with tape devices.3 days ago tape devices have been fixed and we switched to CommVault managed tape backups. CommVault calls RMAN with following command:
These backups done successfully.Then archivelog backup taken similar way.But when I issue RESTORE DATABASE PREVIEW SUMMARY; RMAN starts with Full backup set, though newer Incremental Level 0 ones are available.Why it does not use these newer ones?
n my last post I asked abt the issues that I was facing while restoring the full backup of RMAN on a new server. I mentioned the steps as well, Now my Question is what If I want to restore the incremental backup on the new server?
What all steps do I have to follow after restoring the zero level backup on a new server.
I am using the following query to determine if my rman backup succeeded for failed. I look for "COMPLETED WITH ERRORS"
col input_type format a10 col bck_hrs format 99.9 heading "Run|Time" col status format a21 col end_dt format a20 heading "End|Time" col mbytes_per_sec format 9,999 heading "Output|Rate|MB/sec"
[code]...
output ======
End Run Output Rate INPUT_TYPE STATUS Time Time Size GB MB/sec ---------- --------------------- -------------------- ----- ---------- ------ ARCHIVELOG COMPLETED 2011-12-24 06:03:54 .5 189.4 106 DB INCR COMPLETED 2011-12-24 05:33:05 9.3 3,392.6 103 ARCHIVELOG COMPLETED 2011-12-23 10:12:27 .2 73.3 105
I know that the DB INCR is an INCR 0 backup but is there some way query I can join with my example above to tell me this is INCR 0 or FULL BKUP?
I was thinking maybe setting "COMMAND_ID" some text like INCR 0 or INCR 1 or FULL BKUP. Does that sound feasible
2nd Incremental #1 Files updates between the 1st and 2nd - Monday 3rd Incremental #2 Files updates between the 2nd and 3rd - Tuesday 4th Incremental #3 Files updates between the 3rd and 4th - Wednesday 5th Incremental #4 Files updates between the 4th and 5th - Thrusday 6th Incremental #6 Files updates between the 5th and 6th - Friday 7th Incremental #7 Files updates between the 6th and 7th - Saturday 8th Full Backup #8 Files updates from 1st,2nd to 7th - Sunday 9th Incremental #9 Files updates between the 8th and 9th _ Monday 10th Incremental #10Files updates between the 9th and 10th - Tuesday 11th Incremental #11 Files updates between the 10th and 11th - Wednesday 12th Incremental #12 Files updates between the 11th and 12th - Thrusday 13th Incremental #13 Files updates between the 12th and 13th - Friday 14th Incremental #14 Files updates between the 13th and 14th - Saturday 15th Full Backup CRASHES - NOT COMPLETED - Sunday
I would need to restore now from #8 ( full backup ) and #9 to #14 ( incremental backup )
Tell me the "restore command" to achieve the output?
I have problem on using "delete obsolete" in RMAN.
First, let describe my backup configuration.
1. Full backup every Monday (17-Oct, 10-Oct, 3-Oct, 26-Sep) 2. Incremental backup for other days 3. Enable autobackup of control file 4. Backup archive log every day 5. RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS 6. Execute "Delete obsolete" every day 7. control file is used instead of catalog
The results observed: 1. Backup of control files older than 30 days will be deleted 2. Backup of archive log files older than 30 days will be deleted. 3. Backup of datafiles older than ~14 days but before 30 days are also DELETED.
In my example, the backup of datafiles created at 26-Sep is deleted at 16-Oct.
I tried "restore database validate until time "sysdate-22"" at 17-Oct. And RMAN reported "datafile xx will be created automatically during restore operation". It seems that RMAN failed to do restoration up to 22 days ago. The retention policy I set seems not effective on datafile backups.
I checked view v$backup_set and the "Keep" is "No" and "Keep until" is empty.
The only thing I can think of, is the settings of "CONTROL_FILE_RECORD_KEEP_TIME". It is marked "7" in the Oracle, which is less than the retention. But I suppose this only causes the backup not deleted, but NOT be deleted earlier.
I am trying to create my database on a new server using rman incremental hot backups.
I have already restored and recovered my level 0 database on new server, but i am not able to restore/recover the level 1 backup on the new server. I have transported level 1 backup irom the old server to the new one. Do i need to recover lvl 1 bkp only or restore it also.
I have 2 seperate rman backup one backup is of only datafile ,spfile and controlfile which i am able to restore and recover without any problem say bkp1 taken at 10 am
other set of backup is of only archive log files of same day but later time than datafile backup say bkp2 taken at 8pm...if i restore and recover bkp1 and try to restore bkp2 it gives error datafile exist (possibly due to fact both backup have control file)
if i just restore bkp1 and try to restore bkp2 so that i can do one recover at time it gives error datafile permission issue (possibly due to fact both backup have control file)
I want to restore database upto 8pm time how can i use both bkp1 and bkp2 to do it(restore datafiles and apply all archive logs on it)
I run DLY cold backups including controlfile & archivelogs and keep 3 gens of backups and archivelogs to 3 days also. What is the correct procedure to restore back to an old cold backup. Database is backed up Mon,Tue,Wed on Thur we require to bring database back to Tuesday DLY security.
I have tried: startup mount restore database from tag 'DLYTUE' recover database
( this just rolls forward on all archive logs once it restores datafiles, not getting to point to alter database open resetlogs.)
Next tried to :
recover database archivelog tag 'DLYTUE' ( same outcome )
What is the correct rman procedure including should I remove old archive logs from working OS directory ? Also need to know once I restore back and open database to TUE security how do you tidy up the archive logs and dumps which are no longer require i.e. : weds..
I have read about using the set until time option but how to I get absolute time from when cold backup completed if this is the correct procedure.
While connecting to target database from stand database. I am getting below error.
calhost dbs]$ sqlplus system/oracle@proddb
SQL*Plus: Release 10.2.0.1.0 - Production on Sat Jun 22 00:18:10 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options
SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options [standdb@localhost dbs]$ rman target system/oracle@proddb auxiliary system/oracle@standdb
Recovery Manager: Release 10.2.0.1.0 - Production on Sat Jun 22 00:18:22 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
i have read from documentation but getting some error.
in last
E:Documents and SettingsAdministrator>rman Recovery Manager: Release 11.2.0.2.0 - Production on Sun Sep 30 03:03:09 2012 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. RMAN> connect auxiliary sys/12 connected to auxiliary database: XE (not mounted) RMAN> RMAN> DUPLICATE DATABASE TO xe
[code]...
Backup-Based Duplication Without a Target and a Recovery Catalog Connection?
I have a doubt regarding the process the RMAN follows for restore and recovery of the database.
My Level 0 full backup completes on Saturdays at around 11 am after taking 8 hours (It starts at 3am).On Sunday, I ask RMAN to restore (on a different box) till Saturday 11:30 am.Then, after the restore is successful, I recover it till 11:45 am.
The recovery also goes fine and Iam able to clone to test box.
Till what time is the database restored? I assume its till 11 am since the L0 backup finishes at 11 am though I have asked it to restore till 11:30 am
During the recovery, ONLY the archives generated between Saturday 3 am and till the time i asked for recovery (Saturday 11:45 am ) are required. But, checking the recovery log file, i was surprised to see that RMAN has restored archive files starting from Friday 9:30 pm (Much before the time the Level 0 backup even started).
We are doing RMAN Duplicate set until time to refresh daily our test database for our developers and it taking long time to finish. We noticed on the restore log that RMAN was using a day old old backup pieces to refresh the test database and don't immediately use the latest backup pieces instead.
For additional details here's the rman duplicate command we are using which we run daily(mon-sat) at 4am once daily full backup on production completed.
RMAN Duplicate commands: run { set until time "to_date(to_char(sysdate,'Mon DD YYYY') || ' 04:00:00', 'Mon DD YYYY HH24:MI:SS')"; allocate auxiliary channel ch1 type disk; duplicate target database to testdb; } exit
Is there a way on how to let RMAN use the latest backup pieces instead?
Is this script is enough to delete the backup pieces older than 2 days.
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS; configure device type disk parallelism 1 backup type to compressed backupset;
run { allocate channel d1 type disk ; backup filesperset 5 format '/u06/backup/EBSDEV/EBSDEV_data_t%t_s%s_p%p' database ; sql 'alter system archive log current' ; backup filesperset 20 format '/u06/backup/EBSDV3/EBSDV3_arch_t%t_s%s_p%p' archivelog all delete input ;
We have configured tivoli and getting the below error while execute rman backup.
> rman target / catalog rman/*****@CATLOGDB Recovery Manager: Release 11.2.0.3.0 - Production on Sat Nov 17 13:35:03 2012 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: AMTMXPRD (DBID=534215973) connected to recovery catalog database
