Data Guard :: RMAN Archive Log Backup With Delete Input Command
Mar 17, 2012
I have following query in Dataguard ..
If I want to take Rman archive log backup with delete input command , how the archive logs will be copied to standby database
For eg
I am taking archive backup as
RMAN>backup archivelog all delete input;
here consider few archives are not copied to standby database (due to nw issue) then how standby will receives these missing archives as those are deleted by rman backup at primary side.
I am not getting any document related to above query.
We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.
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 have a Primary database and Standby database both in ASM. Recently my archive logs got deleted and i am trying to recover my standby database with an incremental backup based on scn from primary database. But i face the below error when i recover the standby database with the incremental backup taken in primary database.
RMAN> recover database noredo;Starting recover at 06-NOV-13using target database control file instead of recovery catalogallocated channel: ORA_DISK_1channel ORA_DISK_1: SID=21 device type=DISKchannel ORA_DISK_1: starting incremental datafile backup set restorechannel ORA_DISK_1: specifying datafile(s) to restore from backup setdestination for restore of datafile 00001: +STDBY/11gdb/datafile/system.258.805921881destination for restore of datafile 00002: +STDBY/11gdb/datafile/sysaux.259.805921967destination for restore of datafile 00003: +STDBY/11gdb/datafile/undotbs1.260.805922023destination for restore of datafile 00004: +STDBY/11gdb/datafile
I am trying to remove archive log file on my standby site but I am getting the following message. There are lots of archive logs are present on the storage but rman is unable to displaying that.
RMAN> list archivelog all;
specification does not match any archived log in the repositoryRMAN>
I have One Production and one logical standby database . Due to tape problem we are unable to take backups of primary . And due to business , we cannot take back up on disk in hot period(Bank database ) .
If i take logical standby database backup(level 0 ) using RMAN , then will i be able to restore it on production dtbs (In case Production down) ? . Logical standby is in sync with primary .
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
I had a production db with archive logging enabled
SQL> select name,status 2 from v$archived_log;
NAME STATUS ---------------------------------------- - D:ORACLEARCHIVE_ORCL11_13.DBF A D:ORACLEARCHIVE_ORCL11_14.DBF A D:ORACLEARCHIVE_ORCL11_15.DBF A
[code]...
So i need to restore archivelogs by using sequence
RMAN>RESTORE ARCHIVELOG FROM SEQUENCE 20 UNTIL SEQUENCE 28; So the restore is completed successfully So its very hard to monitor archivelog files i feel i should have included all archivelog files while taking RMAN backup
RMAN >backup database plus archivelog all delete input;
but the problem is my RMAN backup is already 360GB in size and it takes 4-5 hrs to complete .so i need to schedule RMAN backup at one time (e.g sunday) ,delete the archivelog files older than sundayand now schedule the archivelog backup at another day (e.g wed &sat)
my question is where i have to change my script to backup all avaialbe archivelog files if old archivelog files are deleted at os level?
RMAN> run { 2> allocate channel c1 type disk; 3> sql 'alter system archive log current'; 4> backup archivelog all format 'D:oracleackuplog_t%t_s%s_p%p' delete input; 5> release channel c1; 6> }
We are having an intermittent problem related to failing RMAN archive log backups. Normally everything works fine but once every fortnight or so the archive log backup starts to fail with the below message. We run two Oracle instances on this windows box, so they are using same oracle and TSM client binaries, but it is only of the instances that have this problem - the largest instance though. Restarting the Oracle instance solves the problem and everything is back to normal, until next time ...
This is the error message in the rman log file CODERMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of allocate command on c1 channel at 03/27/2013 11:00:29 ORA-03113: end-of-file on communication channel
Trace file CODE Trace file R:\ORA_DATA\SDC002\diag\rdbms\sdc002\sdc002\trace\sdc002_ora_12328.trc Oracle Database 11g Release 11.2.0.3.0 - 64bit Production Windows NT Version V6.1 Service Pack 1 CPU : 40 - type 8664, 20 Physical Cores Process Affinity : 0x0x0000000000000000 Memory (Avail/Total): Ph:85656M/147445M, Ph+PgF:96175M/157683M Instance name: sdc002 Redo thread mounted by this instance: 1 Oracle process number: 57 Windows thread id: 12328, image: ORACLE.EXE (SHAD)
I have the incident file as well if that is of any use.
Could the problem be related to running two backups in parallel?
We run full backups once a week and both this time and last time the archive log backup failed it was in conjunction to when the full backup also was running.
Is there any other solution to the problem than restarting the oracle instance?
Since this is a busy production instance it is a big problem for us to restart it outside of maintenance windows.
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 are going to implement oracle 11g. Now I wanna use rman to take the incremental backup in the follwing way:
Level-0 backup weekly, in the way:
run { allocate channel c1 type disk; allocate channel c2 type disk; BACKUP incremental level 0 DATABASE TAG 'Weekly_full' FORMAT 'E:RMAN_backupweekly_full_%d_%Y%M%D_s%s_p%p.bak'; backup archivelog all not backed up 1 times delete input TAG 'Weekly_full_arc' FORMAT 'E:RMAN_backupweekly_full_arc_%d_%Y%M%D_s%s_p%p.bak';
[code].....
and RETENTION POLICY TO RECOVERY WINDOW is set to 10 days, so that there is no chance that i will delete expired backup before taking backup.
Now my question is,
1) Is the way is correct that there is no wrong configuration. My main concern is about archive log, is it correct?
2) As i am deleting archive log files with the backup and after that the expired archive log backup is also deleted, so is there any chance of failure in recovery.
3) here how archive log backup will work with 10 days retention policy.
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.
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 trying to backup archive logs using rman in standby database. I'm able to backup archive logs using simple command it get's successfully completed. rman > BACKUP ARCHIVELOG ALL When i'm trying to do with keep command it's getting failed.I'm trying to do on physical standby databaseBACKUP ARCHIVELOG ALL KEEP UNTIL TIME 'SYSDATE+100' TAG = 'TEST'.
We have a nightly rman backup that was complete and clean.The backup contains a Data File, Control File and a backup Archive Log file.The database server crashed with all the subsequent archive logs lost.
We are trying to recover from the three backup files.We are bumping into the backup piece missing as all the archive logs are done. how to restore with the exising backup files. the lost archive logs are probably salvageable.
I have a RAC system with DR set-up, this is a test environment and it doesn't have any backup, why DR is required but it exist. Since this is a test a lot or archives gets generated and deleting the archives has become a daily job for this server manually.
I want have a script to delete archive logs which is in non-ASM (i.e. filesystem) after ensuring that the archive log has been applied in standby database. If this can done only by RMAN.
We recently configured data guard in test machine.Archives not applied in physical standby.Where i need to start investigation?
Primary SQL> select THREAD#,max(sequence#) from v$archived_log where applied='YES' group by thread#; THREAD# MAX(SEQUENCE#) ---------- -------------- 1 301 [code]...
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
