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?
View 8 RepliesWe 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.
How we can overcome this.
Oracle 10g
AIX 5.1
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
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 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.
View 7 Replies View RelatedOracle 10gR2 on 64-bit RHEL.Backup Strategy:There will be a level-0 backup of the database every Sunday and level-1 every weekday.Archivelogs will be backed up up every 30 minutes.
Q: How can I delete ALL the archivelog backups that were taken that day (every 30 minutes) right after successful completion of level-0 or level-1 backup?
I want to delete them because they may not be of any use after the level-0 or level-1 backup (am I right)?
can we restore database from obsolete backup using rman
View 2 Replies View RelatedI 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 a policy running every night and it makes:
- level 0 for datafiles not backed up,
- 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.
My scenario is: database is in archivelog mode.
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.
We have EM (Cloud 12c) initiated scheduled backup jobs that perform (all below are online backups, obviously archivelog mode)
- level 0 Incremental 3AM on Sunday - with options backup all archive logs, delete input, delete obsolete
- level 1 Incremental (non cumulative) 3AM every other day - same options
Recovery window is set to 3 days, other options below:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 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 '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;
[code]....
Everything appears to be working normally (archive logs are being backed up and once they are the archive logs themselves are being deleted from the FRA), but I'm having some trouble understanding the behavior of the delete obsolete.
With a recovery window of 3 days, on Monday at 11AM my expectation would be that I would find in backups the following:
- level 0s from day before (Sunday) and the previous Sunday (8 days prior)
- all level 1s from previous Sunday on (so Mon-Sat and this morning)
- archivelog backups from Friday until this morning
What I'm not understanding is that I'm seeing archivelog backups from last Monday, Tuesday, etc. - i would have thought these would have gone obsolete based on my recovery window, yet when I run report obsolete in RMAN nothing is showing up.
RMAN is not removing obsolete backups and now the backup directory is nearly full.Retention policy is 1, however, there are backups more than 6 weeks old still in the backup directory.crosscheck and delete obsolete commands run every night, and I have also run these manually, yet the backup files still remain.It is like RMAN is not aware of their existance.How can I confirm that RMAN does not need them and therefore delete them manually using OS commands.
View 17 Replies View RelatedEnvironment:
oracle 10.2.0.1.0
Windows XP
I have taken the RMAN Full database backup through the following command.My database is in no archivelog mode.
AT RMAN prompt
Shutdown immediate;
Startup mount;
run
{
allocate channel c01 device type disk format 'd:
man_bkp est_%U';
allocate channel c02 device type disk format 'd:
man_bkp est_%U';
backup full database tag 'full_bkup_test_081111';
backup current controlfile;
backup spfile;
release channel c01;
release channel c02;
}
Now i have deleted my all controlfile and spfile/Pfile from the database.So how can i recover my SPfile and controlfile? i do not have autobackup on of SPfile/Controlfile.
I have a live server on which Oracle 10g Database is running. We take full RMAN Backups everyday. Now we want to restore the RMAN Backup file from the Live server to another machine (which is going to be a test system). I want to restore the latest RMAN backup on the test machine (which is not on network).
When I copy the RMAN backup set in the flash recovery area of the test machine and then use "list backup", the backup set is not listed. I also tried "crosscheck backup" and then "list backup" but still the backup set does not appear. how can I register the backup set from live server into test machine and then restore it.
is it possible to have a vss snapshot backup on the top of an RMAN backup. Because the link [URL] says that we can have an incremental level 1 backup on the vss snapshot backup.
So I need to know if interoperability between RMAN and VSS exists or not.
Also is it possible to have mixed backups meaning vss snapshot backups and rman backups. Whenever we take snapshot backup, is it updated in the control file?
I am trying to learn about RMAN Incrementally Updated Backups. I created a database on Server A with the parameters and configurations as shown in image attached. I would like to restore full database on Server B (Test DB).The Server B is exactly same in directory structure as the Server A
e.g. ('E:archive','E:incr_backup'). I would like to automate this process so that it updates the Server B on daily basis for R&D purpose.
Any procedure which we can initiate an incremental backup without Level 0 backup.
View 9 Replies View RelatedCan the control file be used to store scripts which are used to perform backups? I know the RMAN recovery catalog can.
Does the SHOW command display detailed reporting on the RMAN catalog contents other than configuration 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 ;
[Code]....
I've created a small script witch delete the obsolete and expired backups of RMAN.
The problem is: the "delete obsolete" and the "delete expired backup" command needs a confirmation with YES. I don't need to confirm the command and he deletes the backups directly?
Here is my little script:
#!/bin/ksh
export ORACLE_SID=dbtest2
export ORACLE_HOME=/home/oracle/srv/ora/product/11.2.0/dbtest_2
export ORACLE_BIN=/home/oracle/srv/ora/product/11.2.0/dbtest_2/bin
alias RMAN=$ORACLE_BIN/rman
[code].....
if I run below rman command lines in 10g and 11g RMAN, it works well, but NOT in RMAN (Release 8.1.7.4.0), so which commandlines I should use to get to the same pursposes in RMAN 8.1.7.4?
run {
ALLOCATE CHANNEL c1 TYPE 'sbt_tape';
ALLOCATE CHANNEL c2 TYPE 'sbt_tape';
ALLOCATE CHANNEL c3 TYPE 'sbt_tape';
[Code]...
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
[code]...
I am going through the Oracle VSS writer , trying out various methods. Just keen to know if this is the right place to ask VSS related questions as I could not find any post related to VSS.
For Volume based VSS shadow copy backups for a logged database, I am unsure about the restore method using VSS writer. Also oracle doc does not mention any steps for volume based restore of a logged (archive log mode db) database.
I've done a crosscheck backup in RMAN and the list of expired objects has actually gone down, in number, from the last time I did this ( 2 weeks prior). We do NOT delete anything from our RMAN catalog on a routine basis (ie. no "DELETE EXPIRED BACKUP commands were issued) so normally the list of expired backup objects increases with each RMAN maintenance task we do. Why the number of expired objects might actually go down in this particular instance ?
View 15 Replies View Relatedthe rman backup script for weekly full backup and daily incremental backups with configure commands for oracle 11g database.
View 10 Replies View RelatedWe 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.
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.
understanding rman scn based Backup Algorithm .. In SCN based backup do rman generate backup from archivelogs ???
View 1 Replies View RelatedI 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)