Tivoli Header

Administrator's Guide


Defining Devices and Paths

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.

Defining Libraries


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

Defining Drives


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:

Library name
The name of the library in which the drive resides.

Drive name
The name assigned to the drive.

Element address
The element address of the drive. The ELEMENT parameter applies only to SCSI libraries. The element address is a number that indicates the physical location of a drive within an automated library. The server needs the element address to connect the physical location of the drive to the drive's SCSI address. You can get the element address from this Web site: http://www.tivoli.com/support/storage_mgr/tivolimain.html.

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

Defining Data Movers

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:

Data Mover Name
The name of the defined data mover.

Type
The type of data mover being defined.

High Level Address
The High Level Address is either the numerical IP address or the domain name of a NAS file server.

Low Level Address
The Low Level Address specifies the TCP port number used to access a NAS file server.

User ID
The User ID specifies the user ID for a user when intiating a Network Data Management Protocol (NDMP) session with a NAS file server.

Password
The password specifies the password for a user ID in order to log onto a NAS file server.

Online
The online parameter specifies whether the data mover is online or not.

Data Format
The data format parameter specifes the data format used according to the type of data mover device used.

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

Defining Paths

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:

Source Name
The name of the server or data mover being defined as the source for the path.

Destination Name
The assigned name of the device being defined as the destination for the path.

Source Type
The type of source being defined for the path.

Destination Type
The type of device being defined as the destination for the path.

Library Name
The name of the library that a drive is defined to if the drive is the destination of the path.

Device
The special file name of the device being defined. This parameter may be used when defining a path between a server or a NAS data mover and a library or drive.

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


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]