IBM Tivoli Storage Manager Extended Edition, Version 7.1

Automated SCSI library at the original site and a manual scsi library at the recovery site

Ensure that the DEFINE DRIVE and DEFINE LIBRARY commands in the device configuration file are valid for the new hardware configuration.

About this task

For example, if an automated tape library was used originally and cannot be used at the recovery site, update the device configuration file. Include the DEFINE LIBRARY and DEFINE DRIVE commands that are needed to define the manual drive to be used. In this case, you must manually mount the backup volumes.
Note: If you are using an automated library, you may also need to update the device configuration file to specify the location of the database backup volume.
Here is an example of an original device configuration file, which describes an automated tape library:
/*  Device Configuration */

define devclass auto8mm_class AIX operating systems Linux operating systems Oracle Solaris operating systems Windows operating systems devtype=8mmHP-UX operating systems devtype=generictape format=drive
  mountlimit=2 mountwait=60 mountretention=60
  prefix=tsm library=auto8mmlib
 
define library auto8mmlib libtype=scsi 
 
define drive auto8mmlib 8mm_tape0 element=82 online=yes
 
define drive auto8mmlib 8mm_tape1 element=83 online=yes

define path server1 auto8mmlib srctype=server desttype=library
 device=Windows operating systems lb4.0.0.1Linux operating systems HP-UX operating systems Oracle Solaris operating systems /dev/rmt/4lbAIX operating systems /dev/lb4

define path server1 8mm_tape0 srctype=server desttype=drive 
library=auto8mmlib device=Windows operating systems mt1.0.0.1HP-UX operating systems Linux operating systems Oracle Solaris operating systems /dev/rmt/1mtAIX operating systems /dev/mt1

define path server1 8mm_tape1 srctype=server desttype=drive 
library=auto8mmlib device=Windows operating systems mt2.0.0.1HP-UX operating systems Linux operating systems Oracle Solaris operating systems /dev/rmt/1mtAIX operating systems /dev/mt2
 
/* LIBRARYINVENTORY SCSI AUTO8MMLIB KEV004 1 101*/
/* LIBRARYINVENTORY SCSI AUTO8MMLIB KEV005 3 101*/ 
Here is an example of the updated device configuration file when a manual library is used at the recovery site:
/* Device Configuration */

define devclass auto8mm_class AIX operating systems Linux operating systems Oracle Solaris operating systems Windows operating systems devtype=8mmHP-UX operating systems devtype=generictape format=drive
  mountlimit=1 mountwait=60 mountretention=60 prefix=tsm
  library=manual8mm   
 
define library manual8mm libtype=manual
 
define drive manual8mm 8mm_tape0 

define path server1 8mm_tape0 srctype=server desttype=drive 
library=manual8mm device=Windows operating systems mt1.0.0.1HP-UX operating systems Linux operating systems Oracle Solaris operating systems /dev/rmt/1mtAIX operating systems /dev/mt1
The following changes were made:
  • In the device class definition, the library name was changed from AUTO8MMLIB to MANUAL8MM. The device class name remains the same because it is associated with the database backup volumes in the volume history file.
  • The manual library, MANUAL8MM, was defined.
  • A new drive, 8MM_TAPE0, was defined for the manual library.
  • The comments that named the location of volumes in the automated library were removed.
After you restore the database, modify the device configuration file in the database. After starting the server, define, update, and delete your library and drive definitions to match your new configuration.
Note: If you are using an automated library, you may need to use the AUDIT LIBRARY command to update the server inventory of the library volumes.


Feedback