IBM Tivoli Storage Manager, Version 7.1

Giving storage agents access to FILE volumes

You must ensure that storage agents can access newly created FILE volumes. To access FILE volumes, storage agents replace names from the directory list in the device class definition with the names in the directory list for the associated path definition.

About this task

The following example illustrates the importance of matching device classes and paths to ensure that storage agents can access newly created FILE volumes. Suppose you want to use these three directories for a FILE library:

c:\server
d:\server
e:\server

/usr/tivoli1
/usr/tivoli2
/usr/tivoli3

/opt/tivoli1
/opt/tivoli2
/opt/tivoli3

Procedure

Use the following command to set up a FILE library named CLASSA with one drive named CLASSA1 on SERVER1:

define devclass classa devtype=file 
directory="c:\server,d:\server,e:\server" 
shared=yes mountlimit=1

define devclass classa devtype=file 
directory="/usr/tivoli1,/usr/tivoli2,/usr/tivoli3"
shared=yes mountlimit=1

define devclass classa devtype=file 
directory="/opt/tivoli1,/opt/tivoli2,/opt/tivoli3" 
shared=yes mountlimit=1

You want the storage agent STA1 to be able to use the FILE library, so you define the following path for storage agent STA1:
```
define path server1 sta1 srctype=server desttype=drive device=file
directory="\\192.168.1.10\c\server,\\192.168.1.10\d\server,
\\192.168.1.10\e\server" library=classa
```
```
define path server1 sta1 srctype=server desttype=drive device=file
directory="/usr/ibm1,/usr/ibm2,/usr/ibm3" library=classa
```
```
define path server1 sta1 srctype=server desttype=drive device=file
directory="/opt/ibm1,/opt/ibm2,/opt/ibm3" library=classa
```
In this scenario, the storage agent, STA1, will replace the directory name c:\server with the directory name \\192.168.1.10\c\server to access FILE volumes that are in the c:\server directory on the server.

In this scenario, the storage agent, STA1, will replace the directory name /usr/tivoli1 with the directory name /usr/ibm1 to access FILE volumes that are in the /usr/tivoli1 directory on the server.

In this scenario, the storage agent, STA1, will replace the directory name /opt/tivoli1 with the directory name /opt/ibm1/ to access FILE volumes that are in the /opt/tivoli1 directory on the server.

Results

File volume c:\server\file1.dsm is created by SERVER1. If you later change the first directory for the device class with the following command:

update devclass classa directory="c:\otherdir,d:\server,e:\server"

SERVER1 will still be able to access file volume c:\server\file1.dsm, but the storage agent STA1 will not be able to access it because a matching directory name in the PATH directory list no longer exists. If a directory name is not available in the directory list associated with the device class, the storage agent can lose access to a FILE volume in that directory. Although the volume will still be accessible from the Tivoli® Storage Manager server for reading, failure of the storage agent to access the FILE volume can cause operations to be retried on a LAN-only path or to fail.

If file volume /usr/tivoli1/file1.dsm is created on SERVER1, and if the following command is issued,

update devclass classa directory="/usr/otherdir,/usr/tivoli2,
/usr/tivoli3"

SERVER1 will still be able to access file volume /usr/tivoli1/file1.dsm, but the storage agent STA1 will not be able to access it because a matching directory name in the PATH directory list no longer exists. If a directory name is not available in the directory list associated with the device class, the storage agent can lose access to a FILE volume in that directory. Although the volume will still be accessible from the Tivoli Storage Manager server for reading, failure of the storage agent to access the FILE volume can cause operations to be retried on a LAN-only path or to fail.

If file volume /opt/tivoli1/file1.dsm is created on SERVER1, and if the following command is issued,

update devclass classa directory="/opt/otherdir,/opt/tivoli2,
/opt/tivoli3"

SERVER1 will still be able to access file volume /opt/tivoli1/file1.dsm, but the storage agent STA1 will not be able to access it because a matching directory name in the PATH directory list no longer exists. If a directory name is not available in the directory list associated with the device class, the storage agent can lose access to a FILE volume in that directory. Although the volume will still be accessible from the Tivoli Storage Manager server for reading, failure of the storage agent to access the FILE volume can cause operations to be retried on a LAN-only path or to fail.

Feedback