RMAN backup to tape and disk script

Similar Questions

• Movement of RMAN backups on tape

  Hello
  
  How to make the backup of the database, which took by rman to tap.
  
  Ex:
  I have a database and backup taken by rman, connecting mode without a catalog. as the target of $rman.
  
  so backup is generated and stored on disk only.
  
  Now, I want to tap these backup file, how can we move these files.
  
  Please let me know
  
  Thank you!

  You plan change your backup strategy, or just to make a single copy?

  The last submission, if the backup destination is file system, then you can directly copy the backup files generated by RMAN with a command of the OS.
  If within ASM, you will need to copy the files first. According to the version of database you are using, you have different ways to do this.

  If you want to copy on tape with RMAN, then you must configure a media management library. For a running time, it will be too much effort. Please see how to configure: http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmconfb.htm#i1006526

  If you plan to do on a regular basis, it will be a good option to do with RMAN.
  There, you can create backups directly to tape or copy existing (as rp0428 said). See the full example on 11.2 documentation: http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV89492

  Kind regards.
  Nelson

• RMAN backup to the remote disk in Windows

  Hello
  
  I'm under Oracle 9.2.0.1 with Windows Server 2003 in Server A and Server B. My first DB is stored in the server a in the meantime my catalog RMAN is to Server B. I'm under RMAN to do the backup of the DB in Server A, which is short of space. So, I decided to put my backupsets to Server B since I got here a few hundred Gs. Overall, I will push the catalog RMAN backup script to Server B and store the backupsets to Server B.
  My problem is when I run the script, what either him or from a server or Server B, I get the following error. Tied together correspond to the configuration of RMAN settings.
  
  Error:
  
  ***********************************************************************************
  RMAN > backup database;
  
  From backup 20 August 09
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 13 devtype = DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: sid = 9 = DISC devtype
  allocated channel: ORA_DISK_3
  channel ORA_DISK_3: sid = 14 devtype = DISK
  channel ORA_DISK_1: from full datafile backupset
  channel ORA_DISK_1: specifying datafile (s) in backupset
  input datafile fno = 00012 name = F:\ORADATA\DRDB\DATA\DATA01. DBF
  channel ORA_DISK_1: starting piece 1 at 20 August 09
  channel ORA_DISK_2: from full datafile backupset
  channel ORA_DISK_2: specifying datafile (s) in backupset
  input datafile fno = name 00002 = F:\ORADATA\DRDB\DATA\DATA07. DBF
  channel ORA_DISK_2: starting piece 1 at 20 August 09
  channel ORA_DISK_3: from full datafile backupset
  channel ORA_DISK_3: specifying datafile (s) in backupset
  input datafile fno = name 00006 = E:\ORADATA\DRDB\INDEX\INDX01. DBF
  channel ORA_DISK_3: starting piece 1 at 20 August 09
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 2009-08-20 17:06:
  56
  ORA-19504: cannot create the file '\\ServerB\f$\drdb\backupset\BackupDRDB_DB_39k '.
  n665g_105_1 ".
  ORA-27040: skgfrcre: error, unable to create the file
  04002 - OSD: could not open the file
  S/O-error: (OS 5) access denied.
  
  RMAN > show all.
  
  RMAN configuration parameters are:
  CONFIGURE REDUNDANCY 10 RETENTION STRATEGY;
  CONFIGURE BACKUP OPTIMIZATION # by default
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FOR DEVICE TYPE DISK FORMAT to ' \\ServerB\f$\d
  rdb\controlfile\Backup%d_CTL_%F';
  SET UP THE DEVICE TYPE DISK PARALLELISM 3;
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' \\ServerB\f$\drdb\backupset\Backup
  % d_DB_ % %%p s_ u_ ';
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE the SNAPSHOT CONTROLFILE NAME to ' \\ServerB\f$\drdb\controlfile\SNCFDRDB.
  CTL';
  
  **********************************************************************************
  
  My login ID exists in the administrator and ORA_DBA group in Server A and Server B. I can manually run the path '\\ServerB\f$\drdb\backupset\' on server A and able to create/modify/delete a file inside this folder. But I don't understand why the error "access denied"? In any case, is it a proper way to do remote disk backup? I am quite new to Oracle and just attended courses RMAN with the OU. I have Google-ed this problem but no one can help me. Please help me or share your knowledge to solve this problem.
  
  Thank you and best regards,
  Nsiala

  Hi nsiala.

  Under windows, the oracle process runs as a service. By default, this service runs under the Local System account. This account is fairly low privileged when it comes to remote network privileges and therefore cannot see the directory you are trying to write your backups to.

  You can change the user that the service is running as, there are a few notes on metalink for this and I remember well find some info usually using google.

  Concerning
  André

• RMAN - backup on FRA and somewhere else

  Hi all
  
  I would like to configure RMAN, so it would create two copies of backupset...
  In the recovery area Flash (maintenance of the FRA nice, i.e. < file_name > F:\ora_fra\db_name\backupset\ directory structure) and the other to a custom domain (say I:\ora_bck\ < Filename >).
  
  I tried on:
  RMAN > 2 copies of backup of database format 'F:\ora_flash\%U', 'I:\ora_bck\%U ';
  But this resulted in the creation of a file directly in F:\ora_flash (not in accordance with the FRA directory structure, so I don't really know if this file is or is not included in FRA)
  
  If I do the following:
  RMAN > backup database;
  RMAN > run {}
  2 > backup copies of the value = 2;
  3 > backupset backup completed between ' sysdate-1' and 'sysdate' format 'I:\ora_bck\%U ';
  {4 >}
  To do this, what I expect of her (a good copy in FRA, second on I :), but I can even smell it is a terrible solution.)
  
  Any ideas? (The requirement must perform full backup of the DB from time to time in 2 places - FRA and disk I :)
  
  Thank you.
  Adam

  Unfortunately, two-sided printing is unusable during the creation of files in the flash recovery area. BACKUPSET BACKUP is an option, or you can just use a command of the o/s to copy, and then if necessary CATALOGUE files.

• RMAN backup destination changed on disk

  11.2/Solaris 10
  
  We had implemented the backups for a DB go using tape

   
  CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

  It worked very well.
  
  Yesterday we had to take a special cold backup for this DB on the disk. By using the FORMAT parameter to point to the location of the disk, I took this backup in NOCATALOG mode IE. using the control as the catalog file.
  
  Now, when I connected to the catalog for this DB and did a WHOLE SHOW. I see that the backup location is changed on the drive even in the catalog.

   
  CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;

  This has happened because of resynchronization. I think so.
  So whenever I take disk based backups by using the control as the catalog file, I connect the real catalog RMAN schema and return to the location of backup using SBT_TAPE

   
  CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

  ?

  Hi Max,.
  You can declare your allocation of channels within a block run like this:

  Run {}
  allocate channels c1 type DISK;

  backup of database format <..>more archivelog format <..>;

  output channel c1;
  }

  That she should not update the Setup value of the channels, rman to the Ribbon in the catalog or the controlfile.
  Rgds,
  Tycho

• RMan backup to tape

  Hello
  
  1 at - it no differnece between rman full backup and backup of level 0 to increment. If so, what is that.
  
  2. why tape backup, taking a lot of time to fill in when comparing the type of backup device.
  Backup size is also very high. Why is it?
  
  
  Imran

  1. Yes, there is a difference - you cannot perform any additional number 1 or above backups on a backup however on an additional workforce 0 you can (see documentation).

  2. the device may be SBT or DISC - SBT means Media Manager which can technically be somewhere, a disk drive. When you write data on broadband network is slower than directly on the drive (if it's asking your question). Size of backup depends on the database, if you want to reduce the size at the expense of the syntax «backup as compressed backupset...» "use backup/restore time.

• Restore the RMAN backup on another server

  Hello

  ENV: Oracle 10 g 2 64 bit, RHEL 5.8 64 bit on ASM, Database size = ~ 1.3 to

  Backup RMAN of PROD will FRA and then backed up to tape. I have limited access to the PROD because it is maintained by 3rd party.

  My client is planning to move this database on their own datacenter (from the 3rd party data center). For test purposes, I asked DBA of 3rd party to provide us with an export of drawings required data pump. Export takes about 8 hours, and the import takes the same time to the new location. To copy the files exported to new locations takes another few hours (over the network). The total size of the dump file is around 500 GB. Thus, a whole cycle of Export-Import-copy takes about ~ 20 + Hrs.

  I want to try another option to reduce the time required for the updating of the database of PROD and which is "use RMAN backup of PROD ' and restore it on the data center server. RMAN full backup takes ~ 4hrs PROD and the restoration should be at the same time (new server has better and faster HW, storage with a SSD). I found this thread very useful on the Oracle Forms on this topic:

  Restore backup RMAN on another server

  This thread contains very good example for a restoration of database on the file system.

  I have a bit of confusion because my database uses ASM. The default location of the backups in PROD is FRA (on ASM == > db_recovery_file_dest = + FRA ). If I understand correctly, the RMAN backup must be in the same place where he was on the PROD Server - i.e. the diskgroup FRA.

  If I get a copy of the part 3 RMAN backup, how would I copy on FRA?

  OR can / should I just change the init parameter "db_recovery_file_dest" on the new server to point to the file system directory where the backup (say "/ ora_backup") and RMAN will pick up and restore the database?

  Please advise!

  Best regards

  You can restore the backup files to any location, then you must configure the channel using the "CONFIGURE CHANNEL device type disk format 'new location ';

  This thread will help

  Restore from a different location from the original location of RMAN backup

• Is the license needed to hit the backups on tapes?

  Hi all
  
  Our Organization is planning to have Oracle implemented in our business processes, and we plan to have RMAN to hit backups.
  
  Our application server, Oracle database and applications are allowed. As you know there are 2 ways to hit the tape via the Oracle secure backup backup and media management layer, I wanted to know because we have the "HP DL380 G6" server can we use the media management layer to hit backups on tapes and do we need licenses for it.
  
  I think that we need secure backup licensing Oracle, but my question is what is the case in the media management layer.
  
  best regards,

  A.R.M Asif wrote:
  Thanks for the quick reply Rajest...

  Most welcome :)

  Will the procedure mentioned below if management limited in case out for a third-party media management layer (most likely they used), but as an alternative will be the following:

  1 perform RMAN backups on record (as backupset).
  2. take these backups copied to RMAN through OS command.
  3. copy backups on disk to a tape if the tape backups are necessary if the backups on disk are not available.
  4. run the RMAN catalog command to detect the backup
  5 restore and recover the database

  Yes it will work...

  Concerning
  Rajesh

• RMAN BACKUP - validate

  Dear Experts,
  
  Version of DB - 11.1.0.7
  
  I have an RMAN BACKUP taken on the disk with the tag 'NAME of the tag. Is there a way to validate the backup using its tag name to check if it will be useful for a successful restoration and recovery of a different envt? Enjoy your thougts
  
  Thank you

  You can try

  RESTORE DATABASE FROM TAG 'tagname' VALIDATE ;
  RESTORE ARCHIVELOG ALL FROM TAG 'tagname' VALIDATE;
  

  There is also a command post, but it's the syntax requires allows you to specify the BACKUPSET and not the tag

  VALIDATE BACKUPSET 'key' ;
  

  Hemant K Collette

• Oracle RMAN compressed backupset on TSM disk pool

  Hello
  
  We have an Oracle 11.2.0.3 database, size * 2.2Tb* on AIX 6.1.
  
  There are a bunch of disks in TSM 6.3, size * 4 Tb *.
  When you try to take a Tablet backupset on this pool with the command:

  run {
  allocate channel ch01 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch02 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch03 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch04 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch05 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch06 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch07 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch08 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch09 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch10 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch11 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch12 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch13 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch14 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch15 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  allocate channel ch16 device type SBT parms 'ENVTDPPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
  
  BACKUP AS COMPRESSED BACKUPSET FULL DATABASE;
  
  release channel ch01;
  release channel ch02;
  release channel ch03;
  release channel ch04;
  release channel ch05;
  release channel ch06;
  release channel ch07;
  release channel ch08;
  release channel ch09;
  release channel ch10;
  release channel ch11;
  release channel ch12;
  release channel ch13;
  release channel ch14;
  release channel ch15;
  release channel ch16;
  }

  backup fails with the error:
  

  RMAN-03009: failure of backup command on ch16 channel at 11/28/2012 12:22:17
  ORA-19502: write error on file "CS_20121128_qlnrehrm_1_1.DBF", block number 257 (block size=8192)
  ORA-27030: skgfwrt: sbtwrite2 returned error
  ORA-19511: Error received from media manager layer, error text:
     ANS1311E (RC11)   Server out of data storage space
  channel ch16 disabled, job failed on it will be run on another channel

  Attempts to run above the command also failed on cluster disks in TSM with size * 5 TB *, * 7 TB *. But this size is 2 - 3 times bigger than the original DB Dimensions (2.2 to).
  The last attempt to run our command successful on TSM disk pool of * 15 TB *!. During its execution, we could monitor the use of the disk pool of * ~ 7 TB *. Once the backup is complete, the disk pool released and only * ~ 100 GB * compressed backupset remained.
  
  -----
  So the question is: is this a problem or an RMAN or TSM normal?
  
  We will be very greatfull for your kind answers!
  
  
  Kind regards
  Iago

  Hello;

  Not sure how the algorithm works or how the channels have an effect on the compression. Would assume its done in memory or speed would suffer.

  It shows all and testing them to get an idea of what to expect:

  RMAN backup compression

  http://gavinsoorma.com/2009/12/11g-release-2-RMAN-backup-compression/

  And so for this:

  http://taliphakanozturken.WordPress.com/2012/04/07/comparing-of-RMAN-backup-compression-levels/

  And finally:

  http://www.dbspecialists.com/blog/database-backups/RMAN-compression-algorithms-in-11gr2/

  Best regards

  mseberg

  Published by: mseberg on December 7, 2012 03:52

• format + RMAN backup

  Dear friends,
  
  Seasonal greetings.
  
  I use these commands to make my backup.
  

  backup database tag "everyday_full_bkup" format='D:\Oracle_Backup\Database_Name\%I_%T.bkp';

  Can I use the .bkp?
  
  This is the message I get when I run the above, receives the command.
  

  Starting backup at 11-MAY-10
  using channel ORA_DISK_1
  channel ORA_DISK_1: starting full datafile backupset
  channel ORA_DISK_1: specifying datafile(s) in backupset
  input datafile fno=00002 name=D:\ORACLE\DATA\MARSDB\UNDO_01.DBF
  input datafile fno=00001 name=D:\ORACLE\DATA\MARSDB\SYSTEM_01.DBF
  input datafile fno=00004 name=D:\ORACLE\DATA\MARSDB\DATA_01.ORA
  input datafile fno=00005 name=D:\ORACLE\DATA\MARSDB\INDEXES_01.ORA
  input datafile fno=00003 name=D:\ORACLE\DATA\MARSDB\SYSAUX_01.DBF
  input datafile fno=00006 name=D:\ORACLE\DATA\MARSDB\XXSMALLTABS_01.ORA
  channel ORA_DISK_1: starting piece 1 at 11-MAY-10
  channel ORA_DISK_1: finished piece 1 at 11-MAY-10
  piece handle=D:\ORACLE_BACKUP_DATA\MARSDB\1970380511_20100511 tag=EVERYDAY_FULL_BKUP comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
  channel ORA_DISK_1: starting full datafile backupset
  channel ORA_DISK_1: specifying datafile(s) in backupset
  including current control file in backupset
  channel ORA_DISK_1: starting piece 1 at 11-MAY-10
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/11/2010 11:03:01
  ORA-19504: failed to create file "D:\ORACLE_BACKUp\DatabaseName\1970380511_20100511"
  ORA-27038: created file already exists
  OSD-04010: <create> option specified, file already exists

  Seeing this error, I removed the backup:
  

  list backup;
  delete backup piece n; 

  n is based on the number that I see in the backup from the list.
  
  Since then, I thought that set up channel might help, tried this but still getting the same error.
  

  RMAN>
  
  CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT 'the path\%F.bkp';
  BACKUP DATABASE tag "everyday_full_bkup";

  Want to clarify, if the channel set is only to set the path where is made the backup as well as the naming convention?
  
  Just to make sure that everything is fine, I checked
  

  crosscheck backup;

  and all is well.
  
  I even tried
  

  rman> backup database;

  and still the same error.
  
  Please throw some light on this. Please guide me. I'm desperate.
  
  Thanking you in advance.
  
  See you soon!
  
  Nith
  
  Published by: user645399 on May 11, 2010 11:00
  
  Published by: user645399 on May 11, 2010 11:36
  
  Published by: user645399 on May 11, 2010 11:53

  Hi.There occur error because you used format(for backup) is a mistake. Because used this format, rman cannot generate a unique name for each backupset. RMAN create the first backup set using this format, then want to also eponymous and the error occur (backupsets cannot be the same name). You can use %U this guarantees uniqueness in
  generated backups.
  See also
  http://SS64.com/ora/rman_format_string.html

• Error in the creation of the database of hot RMAN backup

  Hello
  
  I created the database at the time of the installation of Oracle software. Name AAA
  Now I took hot RMAN backup of database and after the fall of database.
  
  Now I want to restore the database again, but I am facing a problem.
  
  as: if I want to connect RMAN, $rman target / it gives error
  
  Recovery Manager: Release 10.2.0.1.0 - Production on Tue may 24 15:29:17 2011
  
  Copyright (c) 1982, 2005, Oracle. All rights reserved.
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-04005: target database error:
  ORA-12560: TNS:protocol adapter error
  
  Please help to get me out of this problem.
  
  
  Regs,
  Brij

  See this topic and say if this can help

  http://forums.Oracle.com/forums/thread.jspa?threadID=2190328&TSTART=90

• content managed rman backup crushing and selection procedure of the tape media

  Hello Experts.

  I have a question about the backupset rman tape media manage tape of the osb.

  [ENV]

  Exadata rman backup assistance OSB(version: 10.4.0.3.0) SL500 LTO5 4 Tape Drive with rman scripts and full backup is working well.

  1 Appendix backup on OS crontab

  -Each backup full day at 00:00 AM

  2 rman view all:

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  using the control file of the target instead of recovery catalog database

  RMAN settings for database with db_unique_name TESTDW are:

  CONFIGURE RETENTION POLICY TO 3 DAY RECOVERY WINDOW;

  CONFIGURE BACKUP OPTIMIZATION # by default

  CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';

  SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  3 rman backup scirpts

  Run {}

  allocate channels c01 type 'sbt_tape' connect 'sys/manager@testdw1';

  allocate channel c02 type 'sbt_tape' connect 'sys/manager@testdw2';

  allocate channel c03 type 'sbt_tape' connect 'sys/manager@testdw1';

  allocate channels c04 type 'sbt_tape' connect 'sys/manager@testdw2';

  Backup section size 900g database;

  output channel c01;

  output channel c02;

  output channel c03;

  output channel c04;

  }

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  1st quarter > after several weeks and I run the command as "#obtool u admin Pei welcome1 lsvol-L lib1.

  and are used in many media of rman backup band (about 50EA media, perhaps 46EA are full and 4EA are appendble)

  So, I issue the command 'lsvol - a - c' and could not display expired on all media content.

  Why OSB no has not select and replace the tape media despite the rman rman default retention policy (3days) all show the setting.

  Why OSB does not have the expired status of rman content on tape media?

  -> I need the rman (delete expired, delete obsolete etc...) command to share the summary status of OSB and rman rman?

  Q2 > selection procedure for the tape media all backup rman

  Suppose the total number of tape media is 5EA. (1,2,3,4,5) with an available tape LTO5 drive.

  Status: 1 (full-rman content already expired), 2 (content integral-rman not expired), 3 (editable, remaining space), 4 (new media), 5 (currnet wring media)

  If OSB burn now 5 and reach at the end of the Strip and possibly another media, media to be selected by the OSB?

  Advanced thanks.

  If I place the order obsolete in the rman script as 'delete type 'SBT_TAPE' noprompt obsolete device;' the results will be the same as your

  the syntax because rman default setting (CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS ;) has already been fixed on the command "Show all", right? @)

  Yes.

  I use the catalog of recovery on a different database and backup script has catalog db connection string.

  And if I only use controlfile instead of recovery catalog to save the backup information and put in place "control_file_record_keep_time" a default of 7 days to 365 days, "remove obsolete" command to remove several weeks backupset works well, is it not?

  Possible problem are existing backups for several weeks if you left default control_file_record_keep_time. Change now will not help unless you catalog later manually all the old pieces not catalogued on tape backup.

  After you clean up the situation and particularly to remove obsolete in your script, rman, you will never make problems with control_file_record_keep_time from this moment. By default will do just fine because it is larger than your window of recovery.

  Kind regards

  Mitja

• RMAN backup and cross-checking script

  Hello
  
  I just joined a new company this week. As would any s/n, I was going just through the RMAN backup scripts used in the new environment.
  Here we run weekly RMAN backup complete for some of the databases that I am responsible for managing. The script and schedules are as follows.
  
  Every Sunday from 21:00, we organize a weekly job overlap
  
  Connect target username/pwd@DBNAME
  Connect catalog username/pwd@DBNAME
  
  Run {}
  CROSS-CHECKING OF BACKUP;
  DUPLICATION OF COPY;
  OVERLAP BACKUPSET;
  OVERLAP ARCHIVELOG ALL;
  DELETE NOPROMPT OBSOLETE;
  }
  
  Every Sunday from 9:30, we run the RMAN backup command which is
  
  Connect target username/pwd@DBNAME
  Connect catalog username/pwd@DBNAME
  
  run
  {
  CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  SQL 'alter system archive log current';
  backup as backupset database include current controlfile;
  SQL 'alter system archive log current';
  ARCHIVELOG BACKUP of time ' SYSDATE-8';
  DELETE ARCHIVELOG ALL COMPLETED BEFORE ' SYSDATE-15';
  }
  
  
  A database that I will handle has been set up just over a week before I join.
  28 FEV 21:00 - no set of backup/copy/backup of overlap. I hope it will be cuts across all archive logs available in the database. No obsolete backup/copy/backup/archivelogs to remove.
  28 FEV 21:30 - sets the retention policy at 7 days, full backup of database backup and backup all archivelogs (sysdate-8). No newspaper archive to remove the database was created (migrated) less than 15 days back.
  
  7 March 21:00 - contre-vérifie the backupset (taking the 28 fev 21:30). No backup/copy of overlap.
  Question 1: Is there a backup obsolete here to delete?
  Own thought: Recovery window is 7 days. RMAN needs a backup in order to recover the database in any time-7 days to the present time (7 March 21:00 - 7 days = 28 fev 21:00). No obsolete backup to delete.
  
  7 March 21:30 - full database backup and fails to save all logs archiving (sysdate-8). No space in the Flash recovery disk group. As the archivelog backup failed and RMAN complete, it has not removed the archivelogs ' sysdate-15'.
  
  Backup is running again on 14 March. Of course, it will fail because there is no enough space in the Group of recovery disks.
  
  Future: I'm confused
  March 14, 21:00: contre-vérifie the backupset (supported March February 21:30). No backup/copy of overlap.
  Question 2: How do I know what is here obsolete? From the window of 7 days recovery, 14 March 21:00-7 days is March 7, 21:00. Last backup was taken on March 7, 21:30.
  To get back to 21:00, RMAN makes keep the backup of 28 March?... Does this mean whenever I'll have copies of backup 3?...
  
  14 March 21:30 - backup database... Log Archive backup will fail because there is no space. (I think to make a compressed backup).
  
  Question 3: How those wise commands?
  ARCHIVELOG BACKUP of time ' SYSDATE-8';
  DELETE ARCHIVELOG ALL COMPLETED BEFORE ' SYSDATE-15';
  
  If I take a successful backup of the archivelogs sysdate-8, why I need to keep the archivelogs before that? What could be the reason the previous DBA kept DELETE ARCHIVELOG COMPLETED BEFORE ANY 'SYSDATE-15 '; Rather than give DELETE ARCHIVELOG FINISHED FIRST and FOREMOST ' SYSDATE-8 "?
  
  Thanks in advance for your help.
  
  Published by: user8907052 on March 11, 2010 12:10

  If your database to 9i and above, then you don't need to pass - sql 'alter system archive log current;' before you perform the backup as RMAN automatically archives the log during recovery.

• RMAN backup to disk vs. tape

  AIX R 2
  Oracle: 10.2.0.4
  
  I tested strategies of rman backup on a database in noarchivelog (development) using the following command:
  (*) note: if db is in noarchivelog then you must make a backup, cold have mounted db but not opened.
  
  RMAN > backup database format ' / a010/d01/bck/%U'
  
  I found that this rman backup disc about 2 GB per minute. Now, I want to test it on tape to compare settings.
  
  Question: Which configurations RMAN should write directly to tape?
  What are the safeguards to write to tape? I have to specify the channel of the band and also where the output format is written?
  
  Thank you all.

  Ok

  You must install the Oracle for Tivoli driver (eventually sold with Tivoli) and install it in your Oracle software tree.
  You can set up your channels to write to tape (this is documented).
  For the rest, there is no difference, although there is no directory name.

  -----------
  Sybrand Bakker
  Senior Oracle DBA