Recovery Manager (RMAN) :: How To Delete All Archivelog Backups Of The Day
Sep 3, 2013
Oracle 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)?
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?
am trying to run rman backup plus archivelog TO tape disk my rman configuration settings are as seen below
RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 2; CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; [code].....
get the following error when i do this, RMAN-03009: failure of backup command on C3 channel at 01/03/2013 11:33:45 ORA-00600: internal error code, arguments: [ksfdfetch1], [], [], [], [], [], [],
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.
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.
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';
I have a standby database in which I am backing up my database from. I also backup my archivelogs on my primary site as well as the control file. My issue is that I cannot find the correct RMAN command that will allow me to delete the actual backupsets from disk after say 7 days.
I know how to delete automatically the actual archivelog files, but not how to only have 7 days of archivelog backupsets available at any one given time.
We have two Windows 2008 VMs with Oracle 11G configured as primary and standby.This configuration has been defined by a partner who is no longer working for us.We have broken the correct application of the redo log on the standby when we have not correctly restored some snapshots on those two VMs.I would like to create a new Oracle server that will become the new standby. For that, I need too :
- Display the full dataguard configuration to reproduce it on the new server - Stop (delete ?) the configuration on the primary server.
We also have the current problem that RMAN refuses to delete old archivelog since they have not been applied to the standby.
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 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.
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.
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.
I'm on a Windows server 2003 R2 64 bit, database is 11.1.0.7. From RMAN connected to the target and the catalog, this is a show all;
RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:oracleadmin
[code]....
I'm running incremental backups, a level 0 on sunday and a level 1 the other days of the week, this is the ctl file:
LEVEL 0: connect target /@ORCL connect catalog rman/rmanpw@rmancat RUN {
[code]....
The level 0 does delete the archive logs (because of the delete input). Each backupset has two copies of the archive logs (which is what I want), and I expected the logs to be deleted after being backed up 2 days (each day is twice, 2 days = 4 times). But it's not deleting the logs, even after 6 runs.
I am using RMAN with a recovery catalog option on a separate Database. My question is
When we use catalog does RMAN keep the information in Control file of the Target Database as well or only in recovery catalog? I am asking this in case We lost the database which contains the recovery catalog what to do?
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 am making incremental backups via RMAN, the backups are staying at disk. And the infrastructure team will copy this files backups to tape. And they want delete the files that will staying in disk via RMAN. Until now it's ok.
But and if I need of backups that stay on tape, it's possible make a recovery of deleted files by rman.
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 seen in many RMAN backup scripts that a manual log switching is performed in first line of the script? What is it purpose, just to write changes needed to reconstruct the DML/DDL statements to online redo logfiles and start the archiving process if db is running in archive log mode?
