1) TSM Storage Agent for client with same level fix according to the TSM server

2) TSM server Side Configuration

3) Tape library device driver’s installation on client side for sharing library

4) Environment considerations for LAN free Backup

5) TSM storage Agent Configuration on client side

6) TSM storage Agent Initialization


1) Server side Configuration

Server to Server Communication

Set Servername TEST

Set serverpassword xxxxx

Set serverhladderess i.e

Set serverlladdress i.e 1500

You may review your settings with the query status command

2) Defining library, drives, and associated paths on the server

Steps to follow to define and library sharing in tsm server side.

tsm: BRAINSTROM>define library 3573_shared libtype=scsi shared=yes resetdrives=yes autolabel=yes serial=autodetect

ANR8400I Library 3573_SHARED defined.

tsm: BRAINSTROM>define path BRAINSTROM 3573_SHARED srctype=server

cont> desttype=library autodetect=yes device=/dev/smc0

ANR1720I A path from BRAINSTROM to 3573_SHARED has been defined.

tsm: BRAINSTROM>define drive 3573_shared dr00 serial=autodetect

cont> element=autodetect cleanfrequency=none

ANR8404I Drive DR00 defined in library 3573_SHARED.

tsm: BRAINSTROM>define drive 3573_shared dr01 serial=autodetect

cont> element=autodetect cleanfrequency=none

ANR8404I Drive DR01 defined in library 3573_SHARED.

tsm: BRAINSTROM>define path BRAINSTROM dr00 srctype=server desttype=drive

cont> library=3573_shared device=/dev/rmt0 online=yes

ANR1720I A path from BRAINSTROM to 3573_SHARED DR00 has been defined.

tsm: BRAINSTROM>define path BRAINSTROM dr01 srctype=server desttype=drive


cont> device=/dev/rmt1 online=yes

ANR1720I A path from BRAINSTROM to 3573_SHARED DR01 has been defined.

3) Defining the device class –TSM server Side

Define the device class for the shared library

tsm: BRAINSTROM>define devclass LTOultrium devtype=LTO library=3573_SHARED

cont> format=ULTRIUM2C mountretention=5 mountlimit=DRIVES

Note: In a mixed server and Storage Agent version environment, you should choose a recording format supported by both server and Storage Agent. For example, if your drives support more than one recording format (that is, LTO3 drives support writes using both LTO2 and LTO3 format), and your server is running Version 5.3.2 (which supports LTO3), but Storage Agents are on 5.2.3 (which supports only LTO2), you must either choose LTO2 format or upgrade your Storage Agent to a version that supports LTO3.

4) Creating primary sequential storage pool for LAN-free

Define a primary sequential storage pool for LAN-free

tsm: BRAINSTROM>define stgp tapedata_lf ltoultrium description=”Lan-free storage pool” collocate=no maxscratch=99

ANR2200I Storage pool TAPEDATA_LF defined (device class LTOultrium).

5) Defining policy

Prepare policy components for the LAN-free clients

tsm: BRAINSTROM>define mgmtclass server server lanfree migdestination=NONE

ANR1520I Management class LANFREE defined in policy domain SERVER, set SERVER.

tsm: BRAINSTROM>define copygroup server server lanfree type=backup verexist=3

verdel=1 retextra=100 retonly=100 destination=TAPEDATA_LF

ANR1530I Backup copy group STANDARD defined in policy domain SERVER, set

SERVER, management class LANFREE.

tsm: BRAINSTROM>validate policy server server

ANR1515I Policy set SERVER validated in domain SERVER (ready for activation).

tsm: BRAINSTROM>activate policy server server

Do you wish to proceed? (Yes (Y)/No (N)) y

ANR1514I Policy set SERVER activated in policy domain SERVER.

Syntax for define mgmt class as follows for reference

>>-DEFine MGmtclass–domain_name–policy_set_name–class_name—>















>–+————————–—+————————–—>< ‘-DESCription–=–description-‘ You may review your settings with the query copygroup server active lanfree f=d command in TSM server Register u r node with Server command as follows tsm: BRAINSTROM>register node datawritepath=any datareadpath=any maxnummp=2

ANR2060I Node registered in policy domain STANDARD.

ANR2099I Administrative userid defined for OWNER access to node


6) LAN-free validation

Validate management classes and storage pools for LAN-free

tsm: BRAINSTROM>validate lanfree

ANR0387I Evaluating node using storage agent for LAN-free data movement

Storage Agent setup Client side

To configure the Storage Agent:

1. Identify the shared library and drives in the client operating system.

2. Install device drivers for the library and tape drives.

3. Install the Storage Agent software.

4. Configure the Storage Agent and set it as a service.

5. Obtain device information.

6. Define the Storage Agent and device paths.

7. Customize the client options file to enable LAN-free.

Note: Remember, you cannot install the Storage Agent on a machine that is an Tivoli Storage Manager server

1 & 2 steps you should have to follow before installing the Storage Agent Software very in windows device
manager whether it installed properly.
After verifying install this Storage agent software as follows:

1. To install Storage Software Click TSM Storage Agent and a wizard will launch. Click Next
2. Follow the screen to install the Software in client side

Configuring the Storage Agent

tsm: BRAINSTROM>define server sta_diomede serverpassword=sta_diomede532

cont> hladdress=diomede.itsosj.sanjose.ibm.com lladdress=1502

1. cont> description=”Storage Agent on Diomede”

***sta_diomede =Storage agent name

Customize Storage Agent configuration file

The next step is to edit the Storage Agent configuration file.
This is analogous to the server options file, and is called dsmsta.opt,
located in the installation path. There are numerous options you may set;
however, for the basic setup you need only the devconfig and tcpport options as follows:

Option file dsmsta.opt

DEVCONFIG devconfig.txt


Storage Agent initialization using GUI wizard

To initialize:

To start it, select

Start ? Programs ? Tivoli Storage Manager ? Management Console.

you can start it manually by double-clicking Storage Agent Initialization on the right hand side of the window.

On the final screen, click Back to review the entries, or complete the

initialization by clicking Finish

Storage Agent sessions on the server

If the service started successfully, two sessions are opened to the Tivoli Storage Manager server. One session is for the Storage Agent itself, and the other is for event logging to the Tivoli Storage Manager by applying this command u can check whether sessions established are not.

tsm: BRAINSTROM>query session

Verifying the connection from the server to the Storage Agent

Storage Agent is reachable on the specified address, but also that the Storage Agent is listening on the specified port as well by applying this command as follows :

tsm: BRAINSTROM>ping server



after everything is successfull.you should compare serial number

lsdev -Cc tape|awk ‘{print $1}’| while read a
echo $a
lscfg -vl $a |grep “Serial Number”

Serial Number……………xxxxxxxxxxxxxxx DRIVE01
Serial Number……………xxxxxxxxxxxxxxx DRIVE03
Serial Number……………xxxxxxxxxxxxxxx DRIVE02
Serial Number……………xxxxxxxxxxxxxxx DRIVE04
Serial Number…………..xxxxxxxxxxxxxxx

tsm: TSM>q drive TS3500 DRIVE01 f=d

WWN: xxxxxxxxxxxx
Serial Number: xxxxxxxxxxxxx

tsm: TSM>q drive TS3500 DRIVE02 f=d

WWN: xxxxxxxxxxxxx
Serial Number: xxxxxxxxxxxx

tsm: TSM>q drive TS3500 DRIVE03 f=d

WWN: xxxxxxxxxxxxx
Serial Number: xxxxxxxxxxxx
tsm: TSM>q drive TS3500 DRIVE04 f=d
WWN: xxxxxxxxxxxx
Serial Number: xxxxxxx




Please enter your comment!
Please enter your name here