![]() |
![]() |
The following sections describe how to define libraries and drives, as well as their paths, to Tivoli Storage Manager. See Managing Libraries, Managing Drives, and Managing Pathsfor information about displaying library, drive, and path information, and updating and deleting libraries and drives.
Task | Required Privilege Class |
---|---|
Define or update libraries | System or unrestricted storage |
Before you can use a drive, you must first define the library to which the drive belongs. This is true for both manually mounted drives and drives in automated libraries. For example, you have several stand-alone tape drives. You could define a library named MANUALMOUNT for these drives by using the following command:
define library manualmount libtype=manual
For all libraries other than manual libraries, you must also define a path from the server once you have defined the library. For more information about paths, see Defining Paths. For example, if you have an Exabyte EXB-120 device, you could define a library named ROBOTMOUNT using the following command:
define library robotmount libtype=scsi
Next, you use the DEFINE PATH command. In the path, you must specify the DEVICE parameter. The DEVICE parameter is required and specifies the device special file by which the library's robotic mechanism is known.
define path server1 robotmount srctype=server desttype=library device=/dev/lb0
If you have an IBM 3494 Tape Library Dataserver, you can define a library named AUTOMOUNT using the following command:
define library automount libtype=349x
Next, assuming that you have defined one LMCP whose device name is /dev/lmcp0, you define a path for the library:
define path server1 automount srctype=server desttype=library device=/dev/lmcp0
Task | Required Privilege Class |
---|---|
Define drives | System or unrestricted storage |
To inform the server about a drive that can be used to access storage volumes, issue the DEFINE DRIVE command, followed by the DEFINE PATH command. For more information about paths, see Defining Paths. When issuing the DEFINE DRIVE command, you must provide some or all of the following information:
For example, to define a drive that belongs to the manual library named MANLIB, enter this command:
define drive manlib tapedrv3
Next, you would define the path from the server to the drive using the device name used to access the drive:
define path server1 tapedrv3 srctype=server desttype=drive library=manlib device=/dev/mt3
Data movers are SAN-attached devices that, through a request from Tivoli Storage Manager, transfer client data for backup, archiving or restore purposes. Data movers are defined as unique objects to Tivoli Storage Manager. Types of data mover devices include NAS file servers.
When issuing the DEFINE DATAMOVER command, you must provide some or all of the following information:
For example, to define a NAS data mover named NAS1, you would enter the following:
define datamover nas1 type=nas hladdress=netapp2.tucson.ibm.com lladdress=10000 userid=root password=admin dataformat=netappdump
Before a device can be used, a path must be defined between the device and the server or the device and the data mover responsible for outboard data movement. This command must be used to define the following path relationships:
When issuing the DEFINE PATH command, you must provide some or all of the following information:
For example, if you have a SCSI type library named AUTO8MMLIB that has a device name of /dev/lb3, you could define the path to the server named ASTRO1 by doing the following:
define path astro1 auto8mmlib srctype=server desttype=library device=/dev/lb3
If you had a drive, DRIVE01, that resided in library AUTO8MMLIB, and had a device name of /dev/mt4, and you wanted to define it to server ASTRO1, you would do the following:
define path astro1 drive01 srctype=server desttype=drive library=auto8mmlib device=/dev/mt4