Backup & Recovery :: Delete Obsolete Backup From RMAN?
Jul 17, 2013
Environment: 2 Node Oracle(10.2.0.4.0) RAC on Aix 6.1.
Backups using RMAN utility.Our system is configured to take backups on Tape library using TSM server.
We take incremental level 1 backup on all days and Level 0 backup on Wednesday.We would like to keep the RMAN retention period of 14 days.I delete the backups that are 7 days old from the disk to save space and 14 days older backup from Tape.
I am getting below error in my RMAN backup logfiles.Also attached
RMAN-06207: WARNING: 147 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
The configuration of RMAN is:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
[code].....
How to avoid this error ? Can we set "Retention period" as 14 days in RMAN level and delete the backups in disk which is older than 7 days?Should the deletion of tape backup be handled in TSM level ?
I am working on Oracle 10g Rel 2. I am unable to delete the OBSOLETE from rman
previously my senior use to take backup on remote m/c.
While giving the command
rman>delete obsolete
RMAN-06207: WARNING: 228 objects could not be deleted for DISK channel(s) due RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status RMAN-06210: List of Mismatched objects RMAN-06211: ========================== RMAN-06212: Object Type Filename/Handle RMAN-06213: --------------- --------------------------------------------------- RMAN-06214: Backup Piece \192.168.1.162BACKUPFINPRODDB_T619092194_S12_P1 RMAN-06214: Backup Piece \192.168.1.162BACKUPFINPRODDB_T619093015_S13_P1
I have a problem in running delete obsolete or report obsolete using rman. Although the retention policy is set to "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 60 DAYS;", when running delete obsolete or report obsolete it deletes or returns all the backupsets till sysdate. What should I do to solve this issue?
- level 1 for datafile not backed up since 'sysdate-1' then another policy makes:
- level 0 when the datafiles become read only
The recovery windows is set to 1 day.
In the following situation:
RMAN> list backup of datafile 394;
List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 12721 Incr 0 13.25M SBT_TAPE 00:01:13 25-MAY-11 BP Key: 12777 Status: AVAILABLE Compressed: NO Tag: ST_TRONLINE_FB20110525 Handle: bk_13201_1_752082473 Media: A00003
[code]....
I expect that the first L0 backup is going to become obsolete, but even if I run crosscheck, it never become obsolete.
We observed that our RMAN backup was taking more time to complete. CROSSCHECK is the main culprit as because of having data in the catalog for more than 3 years.
So in the part of script we added delte obsolete recovery windoe of 14 days. (Redundancey 1).
Here the problem is we are getting error as
RMAN-03002 - failure of delete command RMAN-06091 - NO channel allocated for maintenance (of an appropriate type).
Reason: Till 2 years back the backup was stored in tape and after that it got changed to disk. So allocating channel disk to delete obsolet is not working. How we can over come this.
We tried like allocating channel tape sbt_type. It got failed as no media manager information configured. We dont have that information.
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 ;
note in our database we changed RMAN backup to redundancy 7.
RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 7; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default 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 ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_mscmada.f'; # default
Also we have scheduled in our dailly backup to delete obsolete backup means to delete backup which completed more that 7 times, but when we check our backup still in our disk for 1 Month.Note we have scheduled to delete obsolete backup dailly.
I have set the RETENTION POLICY TO RECOVERY WINDOW Values to 2 days,but my backup sets which backuped before 2 days(30-NOV-11),and the backup set is avaliable also,i think it must be expired or obsolete,why?
RMAN> show all; RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
I am trying to delete the backupset using Delete Obsolete command, but i am unable to get the success. As per the oracle Doc after completion of Retention Period oracle automatically deletes the backupset. I have set the retention period of 8 days.
I am getting the below error while executing "report obsolete" and "delete obsolete " commands in RMAN. except these two all the RMAN commands are working fine like "list backup summary" "list backup" .....
Error:
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of delete command at 08/28/2012 11:03:04 RMAN-06004: ORACLE error from recovery catalog database: ORA-01403: no data found OS: IBM AIX Oracle Version: 9.2.0.8
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)
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.
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?
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.
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
I am trying to setup incremental backup on my windows OS based server using RMAN command in batch file. When I use batch file in OS scheduler it is working fine, when I am calling same batch file from my LOCAL desktop PC it throws errors as below.
D:> \3.193.211.19sgdba mankp_acressit.bat D:>rman catalog rman/******@acressit target / cmd file=E:sgdba mankp_arch.rcv log E:sgdba mansit_arch_rman_backup.log RMAN-00557: could not open MSGLOG "E:sgdba
[code]....
Both single and double quotes (' or ") are accepted for a quoted-string.
Quotes are not required unless the string contains embedded white-space.
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00556: could not open CMDFILE "E:sgdba mankp_arch.rcv"
[code]....
* on my DB server I am login using my administrator account, on my PC I dont have admin account.
* I have checked remote execution using local user as well as admin user.
* I have checked the permission and my local ID & EVERYONE has all permission in that folder.
We are using Oracle 10g R2 in Windows Server 2003. I'm trying to restore a database in a new server, using RMAN backups.
Our external consultant configured RMAN scripts for full and incremental backups but never tested them . Since he just doesn't show up, I'm forced to tested them, restoring the whole database in a new server.
My instance is named MTDPROD, and I will create all from scratch.
At current server, RMAN files are generated in: //192.168.1.149/g$/XXXSRV4-ArcLogs/MTDPROD/RMAN
At new server, I run all these commands:
C:>oradim -new -sid MTDPROD -intpwd mtdprod Instance created -- I created the relevant folder hierarchy under <ORACLE_BASE> directory -- Then, I created the relevant directories for Oracle Database, as follows: --a. Create BDUMP, CDUMP, and UDUMP directories under '<ORACLE_ BASE>
[code]....
By instance, I see a lot of this kind of files:
- FULL_MTDPROD_20110529_386_1.BAK - INCR_MTDPROD_20110621_480_7.BAK And only see these two files: - C-2169285856-20110527-03 - C-2169285856-20110527-04
It seems that this C-2169285856-.... files only were on 27/05/2011 and then no more. However, the FULL_... and INCR_.. files are generated every day. The FULL is generated at the end of each month and INCR is generated every day.
This is the backfull.sql:
run { allocate channel c1 type disk maxpiecesize=4G; CROSSCHECK archivelog all; backup incremental level 0 format '\192.168.1.149g$XXXSRV4-arclogsMTDPRODRMANFULL_
[code]....
This is the backincr.sql:
run { allocate channel c1 type disk maxpiecesize=4G; CROSSCHECK archivelog all; backup incremental level 1 cumulative format '\192.168.1.149g$XXXSRV4-arclogsMTDPRODRMANINCR_ %d_%T_%s_%p.bak'
Tape streaming is not happening while performing RMAN tape backup. On investigation, you find that it is not because of the incremental backup or the empty file backup and that RMAN is sending data blocks to the tape drive fast enough.What could be a solution to make tape streaming happen during the backup?
A.Configure backup optimization
B.Configure the channel to increase MAXOPENFILES
C.Configure the channel to increase the capacity with the RATE parameter
D.Configure the channel to adjust the tape buffer size with the BLKSIZE option
We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
run { CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/dd_oraback/tkprod/%F'; CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 22 DAYS; sql 'alter system archive log current';
[code]...
So /dd_oraback is a Data Domain mount. Not sure if that makes any difference or not.
I am attempting to use an rman backup form our live server to restore live data over an existing dev database with a different name. I cant use the duplicate command as the versions of oracle are different (10.2.0.4 EE on live, 10.2.0.5 SE on dev) So I copied the backup sets including an autobackup control file onto the dev server. I set the ORACLE_SID to the DEV version (SUN43DEV) and startup nomount and restore controlfile from the backup location. This works and restored the live controlfile. However, I then wanted to mount the database and catalog the backupsets before making a note of the last archivelog etc and restoring the backup with set newname options. But when I try to mount the database I am told that the database has a different name (SUN43 is not SUN43DEV). I read somewhere that I need to set the ORACLE_SID to the live value (SUN43) and restore as that, then use nid TO RESET THE DBID and DATABASE NAME. However, my tnsnames on DEV has no entry for the live database, and we do not have any service defined through ORADIM for the live instance on the dev server. Should I be creating an entry in DEV tnsnames that actually looks at the LIVE server? or do I need to create a service and tns entry etc for SUN43 on my DEV server pointing at the DEV server I have not seen any mention in instructions of creating a service or adding the entry to tnsnames, or indeed adding an entry to the listener for the original live sid. I am worried that if I actually point to the live server then the restore would be attempted on the live server not dev even though I am running it from Dev.
Also, do I need to drop the existing database on DEV before I restore or will RMAN just restore over the top of it?
Finally, if I try to add an entry to the LISTENER.ORA for the new sid, when I stop and start the listener, or reload, the entry is not recognised. I also noticed that the existing SUN43DEV entry is not in there either, yet I can still use that SID - I am assuming that is because the listener is not being used and the sid is recognised from the existence of the service in windows services instead?
