HOW TO CATALOG TAPE BACKUP PIECES [ID 550082.1]

MARK下这个文章,很有用


HOW TO CATALOG TAPE BACKUP PIECES [ID 550082.1]To BottomTo Bottom

Modified:Dec 20, 2011Type:HOWTOStatus:PUBLISHEDPriority:3
There are no commentsComments (0)Rate this documentEmail link to this documentOpen document in new windowPrintable Page

In this Document
  Goal
  Solution


Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.1.0.6 - Release: 10.1 to 11.1
Information in this document applies to any platform.
Applies to databases release 10g and further

Goal

Starting with 10g, it's possible to use the rman CATALOG command to add backuppieces stored in disk to the rman repository.

You may need  to catalog backup pieces in the following situations:

  • You copy or move a backup piece with an operating system utility and want it to be usable by RMAN.

  • The RMAN metadata for the backup piece was removed, but the backup piece still exists. This situation can occur if you ran the DELETE command on a backup piece that was only temporarily unavailable.

  • You make a NOCATALOG backup on one database host in a Data Guard environment and move the backup piece to the same location on a different database host. In this case, the recovery catalog has no record of the original backup piece.

  • You do not use a recovery catalog and must re-create the control file, thereby losing all RMAN repository data. Cataloging your backups makes them available again.

  • When control file autobackup is disabled, you back up the control file and then back up the archived redo logs. You can restore and mount the control file, but must catalog the backup pieces containing the archived redo logs backed up after the control file.

But it's not possible to use the CATALOG command for backup pieces stored in TAPE.  This note explains how to add backuppieces stored in TAPE to the repository

Solution

From 10.1, there is an undocumented command that allows to catalog tape backup pieces:

 CATALOG DEVICE TYPE 'SBT_TAPE' BACKUPPIECE '';


* Prerequisites

1. Use automatic channel configuration.  It's mandatory to configure one sbt_tape device channel in your  rman automatic configuration  parameters;

 CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS ''

2. It's necessary to know the backup piece file name in the tape and the backup piece file needs to
   be available and accessible.

* How to

Once there is a tape channel configured for accessing to the tape, the rman CATALOG command can be used to  insert in RMAN catalog the tape backup piece:
  
       CATALOG DEVICE TYPE 'SBT_TAPE' BACKUPPIECE '';

* Examples

- This is an example using Oracle Secure Backup (OSB):

1. Define a tape channel in the RMAN automatic configuration:
  
  RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE'
      PARMS 'SBT_LIBRARY=/usr/local/oracle/backup/lib/libobk.so,ENV=(OB_MEDIA_FAMILY=RMAN-DEFAULT)';

2. Check that channel configuration is correct


  RMAN> show all;
 
  ....
  CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=/usr/local/oracle/backup/lib/libobk.so,ENV=(OB_MEDIA_FAMILY=RMAN-DEFAULT)';
  ....

3. Catalog the backup piece

   RMAN> CATALOG DEVICE TYPE 'SBT_TAPE' BACKUPPIECE '0pivagf8_1_1';


- The following will catalog a backuppiece on netbackup:

RMAN>CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE'
     PARMS 'ENV=(NB_ORA_CLASS=oraclebkup, SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so)';

RMAN> CATALOG DEVICE TYPE 'SBT_TAPE' BACKUPPIECE 'lij1qaa3_1_1';

 


请使用浏览器的分享功能分享到微信等