|
|Use this command to define a path from a source to a destination. |When a path is defined between a source and a destination, the destination is |accessible from that source. You must define the source and destination |before you can define a path.
|Privilege Class
|To issue this command you must have system privilege or unrestricted |storage privilege.
|Syntax
|
|
When the destination is adrive |
>>-DEFine PATH--source_name--destination_name-------------------> >--SRCType--=--+-DATAMover-+--DESTType--=--DRive----------------> '-SERVer----' >--LIBRary--=--library_name--DEVice--=--+-device_name-+---------> '-FILE--------' .-ONLine--=--Yes-----. >--+--------------------+---------------------------------------> '-ONLine--=--+-Yes-+-' '-No--' .-DIRectory--=--current_directory_name-. >--+--------------------------------------+-------------------->< '-DIRectory--=--directory_name---------' |
|Syntax
|
|
When the destination is alibrary |
>>-DEFine PATH--source_name--destination_name-------------------> >--SRCType--=--DATAMover--DESTType--=--LIBRary------------------> .-ONLine--=--Yes-----. >--DEVice--=--device_name--+--------------------+-------------->< '-ONLine--=--+-Yes-+-' '-No--' |
|Parameters |
|When a path is defined between a source and a destination, the destination |is accessible from that source. The source must already be defined to |the TSM server.
|The source uses the device name to access the drive or library. See Table 75 for examples.
|
|
|
|
|
|
|Table 75. Examples of Device Names
Source to destination | Example |
---|---|
Storage agent to a drive (not a FILE drive) | mt3 |
Storage agent to a drive when the drive is a logical drive in a FILE library | FILE |
NAS data mover to a library | mc0 |
NAS data mover to a drive | rst0l |
|sysconfig -t
|Use this command to determine the device name for a library:
|sysconfig -m
||The source and the destination must both be available to use the |path. For example, if the path from a data mover to a drive is online, |but either the data mover or the drive is offline, you cannot use the |path.
|Attention: If the path to a library is offline, the server |will not be able to access the library. If the server is halted and |restarted while the path to the library is offline, the library will not be |initialized. See Administrator's Guide for additional |information.
|The directory name identifies the location where the storage agent reads |and writes the files that represent storage volumes for the FILE device class |that is associated with the FILE library. The default value for |DIRECTORY is the directory of the server at the time the command is issued, |unless the DSMSERV_DIR environment variable has been set. In most |cases, the default value for DIRECTORY will not be useful because the |directory location can vary among systems accessing the same data on the |SAN.
|Use a naming convention that allows you to associate the directory with a |particular physical drive. This can help ensure that your configuration |is valid for sharing the FILE library between the server and storage |agent. If the storage agent is on a Windows NT or Windows 2000 system, |use a universal naming convention (UNC) name.
|For information about the DSMSERV_DIR variable, refer to Quick |Start. |
|Examples
|Task
|Define a path from the data mover that is a NAS file server to the |drive that the NAS file server will use for backup and restore |operations. In this example, the NAS data mover is NAS1, the drive name |is TAPEDRV3, the library is NASLIB, and the device name for the drive is |rst0l. |
|Task
|Define a path from storage agent SA1 to the drive that the storage |agent uses for backup and restore operations. In this example, the |library is TSMLIB, the drive is TAPEDRV4, and the device name for the drive is |mt3. |
|Task
|Define a path that allows the storage agent to access files on disk |storage shared with the Tivoli Storage Manager server. Drive FILE9 is |defined to library FILE1 on the server. The storage agent SA1 accesses |FILE9. The data for FILE9 resides on the server at |d:\tsmdata\filedata. On the storage agent, this data |is on directory c:\tsmdata\filedata. |
|Related Commands
|
|Table 76. Commands Related to DEFINE PATH
Command | Description |
---|---|
DEFINE DATAMOVER | Defines a data mover to the Tivoli Storage Manager server. |
DEFINE DRIVE | Assigns a drive to a library. |
DEFINE DRIVEMAPPING | Defines the drive name that will be mapped to the storage agent allowing for direct storage and retrieval of data. |
DEFINE LIBRARY | Defines an automated or manual library. |
DELETE PATH | Deletes a path from a source to a destination. |
QUERY PATH | Displays information about the path from a source to a destination. |
UPDATE DATAMOVER | Changes the definition for a data mover. |
UPDATE PATH | Changes the path from a source to a destination. |