Daily Administrator Checklist for TSM Server

1. List TSM license compliance.

audit lic
select compliance from licenses

2. Query server processes and pending requests to determine if any jobs are waiting on operator action.

q pr
q req
q se

3. Query all disk storage pools to determine if the migration process has completed.

select stgpool_name, pct_utilized from stgpools where devclass='DISK'

4. List all drives that are OFFLINE.

select drive_name from drives where not online='YES'


5. List all paths that are OFFLINE.

select source_name, source_type, destination_name, destination_type from paths where not online='YES'

6. List all locked nodes.

select node_name from nodes where not locked='NO'

7. List all non-writeable tape and disk volumes.

q v acc=unavail
q v acc=reado
q v acc=destroyed

select volume_name, read_errors, write_errors from volumes where (read_errors>0 or write_errors>0)

select volume_name from volumes where devclass_name='DISK' and not status='ONLINE'

8. Verify that the library has sufficient scratch volumes.

select library_name,status,count(*) as "VOLUMES" from libvolumes group by library_name,status

9. Verify that the database extension and reduction values are non-zero and that the Cache Hit Ration is above 99%.

q db f=d

10. Verify that the recovery log extension and reduction values are non-zero and that the Wait Percentage is zero.

q log f=d



11. Verify that database and recovery log volumes are online and synchronized.

q dbv f=d
q logv f=d

12. Inspect TSM database fragmentation level.

select cast((100 - (cast(max_reduction_mb as float) * 256 ) / (cast(usable_pages as float) - cast(used_pages as float) ) * 100) as decimal(4,2)) as PERCENT_FRAG from db

13. Verify that the scheduled database backups completed successfully.

select date (date_time) as date, time(date_time) as time, volume_name, type from volhistory where type in ('BACKUPFULL', 'BACKUPINCR', 'DBSNAPSHOT', 'DBDUMP')

14. Verify that all CLIENT schedules for the last day succeeded.

q ev * * begind=-1 endd=today begint=00:00:00 endt=00:00:00

To restrict the listing to only those nodes with non-completed status:

q ev * * begind=-1 endd=today begint=00:00:00 endt=00:00:00 ex=y

15. Verify that all ADMINISTRATIVE schedules for the last day succeeded.

q ev * t=a begind=-1 endd=today begint=00:00:00 endt=00:00:00

To restrict the listing to only those nodes with non-completed status:

q ev * t=a begind=-1 endd=today begint=00:00:00 endt=00:00:00 ex=y

16. Check the activity log for error messages.

q actl search=AN?????E begind=-1 begint=00:00 endd=today endt=00:00

17. Open files and other missed filed will often not have the schedule name in activity log error messages. This query will list these files:

select nodename,date_time,message from actlog where (date_time>currenttimestamp-1 day) and msgno in (4005,4007,4018,4037,4046,4047,4987,4973,4034,4042)

18. List nodes that are not associated with a backup schedule.

select node_name from nodes where node_name not in (select node_name from associations)

19. Cross match the TSM node name with the host name or computer name.

select node_name, tcp_address, tcp_name from nodes

20. List PRIMARY POOL volumes that have been checked out of the library.

select volume_name, stgpool_name from volumes where stgpool_name in (select stgpool_name from stgpools where devclass<>'DISK' and pooltype='PRIMARY') and volume_name not in (select volume_name from libvolumes)

21. Checkout all D/R Media for offsite storage.

move drm * wherest=mo tost=va rem=b

22. Verify that all D/R volumes have been checked out.

select volume_name from libvolumes where volume_name in (select volume_name from volumes where stgpool_name in (select stgpool_name from stgpools where devclass<>'DISK' and pooltype='COPY'))

23. Verify that all TSM database backup volumes have been checked out.

select volume_name from libvolumes where last_use='DbBackup'

24. Identify previous offsite volumes that can be recycled to scratch status and checkin the same.

q drm wherest=vaultr
move drm * wherest=vaultr tost=onsite
checki libv checkl=b stat=scr search=b wait=0

25. Generate a list of unlocked TSM administrator accounts with full system privileges.

select admin_name from admins where not system_priv='No' and not locked='No'

26. List TSM Nodes and Client (BA/TDP) versions by platform.

select platform_name as OS, client_os_level as OS_VER, node_name as Node, cast(cast(client_version as char(2)) '.' cast(client_release as char(2)) '.' cast(client_level as char(2)) '.' cast(client_sublevel as char(2)) as char(15)) as "TSM Client" from nodes order by platform_name, "TSM Client", Node

27. Data backed up in the last 24 hours:

select entity, date(start_time) as DATE, time(start_time) as START_TIME, time(end_time) as END_TIME, substr(char(end_time-start_time),3,8) as DURATION, cast((bytes/1024/1024/1024) as decimal(18,2)) as GB_BACKED_UP, successful from summary where cast((current_timestamp-start_time) hours as decimal)<24>=current_timestamp-24 hours and activity='BACKUP' group by entity

28. Size and duration of archive operations for each node in the last 24 hours:

select entity as "Node Name ", cast(sum(bytes/1024/1024) as decimal(10,3)) as "Total MB", substr(cast(min(start_time) as char(26)),1,19) as "Date/Time ", cast(substr(cast(max(end_time)-min(start_time) as char(20)),3,8) as char(8)) as "Length " from summary where start_time>=current_timestamp-24 hours and activity='ARCHIVE' group by entity

29. Compare PRIMARY and COPY pool occupancy totals.

select sum(num_files) as num_of_files,sum(physical_mb) as Physical_mb,sum(logical_mb) as logical_mb from occupancy where stgpool_name in (select stgpool_name from stgpools where pooltype='PRIMARY')

select sum(num_files) as num_of_files,sum(physical_mb) as Physical_mb,sum(logical_mb) as logical_mb from occupancy where stgpool_name in (select stgpool_name from stgpools where pooltype='COPY')

TSM LANFREE BACKUP CONFIGURATION STEPS(SAN backup)

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


Steps:

1) Server side Configuration

Server to Server Communication

Set Servername TEST

Set serverpassword xxxxx

Set serverhladderess i.e 10.1.10.64

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

library=3573_shared

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—>

.-SPACEMGTECHnique–=–NONE———-.

>–+————————–———-+——————-—->

‘-SPACEMGTECHnique–=–+-AUTOmatic-+-’

+-SELective-+

‘-NONE——’

.-AUTOMIGNOnuse–=–0—-.

>–+————————+-———————————->

‘-AUTOMIGNOnuse–=–days-’

.-MIGREQUIRESBkup–=–Yes—–.

>–+————————–—+————————–—->

‘-MIGREQUIRESBkup–=–+-Yes-+-‘

‘-No–’

>–+————————–—-+————————-—->

‘-MIGDESTination–=–pool_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

TCPPORT 1502


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

Creating Multiple TSM Instances in a UNIX Environment

To run multiple Tivoli Storage Manager servers on the same machine, you must create unique port numbers TCPPORT, HTTPPORT, SHMPORT and TCPADMINPORT and maintain database and recovery log files that are separate to each TSM server instance. Each server instance needs its own ports and its own database and recovery log.


Take note that you need a separate license for each unique instance of the server in order to run additional servers.


When running multiple servers, note that running a server from a directory other than the installation directory is only supported by setting the DSMSERV_DIR environment variable. This is because the base install directory is used for more than just finding the executables; e.g. the license and message file. To run a server from a directory other than the installation directory, you set the DSMSERV_DIR environment variable to point to the installation directory and add /opt/tivoli/tsm/server/bin to your path.

This exercise assumes that both servers will be using the same IP address and clients will be connecting to both servers. In order to set this up, two unique TCPPORTS and HTTPPORTS must be used in the dsmserv.opt. Otherwise the ports will not be open for connection when both servers are running, because the server that starts up first claims the port and the port will be bound to that server.

The TSM server software code is installed in /opt/tivoli/tsm/server/bin. The same executable, but different TSM Disk Definition – dsmserv.dsk, TSM Server Options – dsmserv.opt, Volume History and Device Configuration files will be used in each instance. This exercise assumes that the user will be keeping a set of these files for one instance in /opt/tivoli/tsm/server_A and in /opt/tivoli/tsm/server_B for the other. However, any filesystem can be used.

From here on, assume that server_A is the default installed TSM environment and that server_b is to be created.

The following steps can then be implemented:

For server_A:

1. After halting server_A, change to the server_A instance directory.

cd /opt/tivoli/tsm/server_A

2. Edit’s its dsmserv.opt file (the bare minimum setup below):

commmethod tcpip
tcpport 1500
commmethod http
httpport 1520
devconfig devcfg_serverA.out
volhist volhist_serverA.out

3. server_A can be started up by using

3.1 The –o parameter of the dsmserv command to specify an options file name.
3.2 The following command if your shell is in the csh family:

setenv DSMSERV_DIR /opt/tivoli/tsm/server/bin
setenv DSMSERV_CONFIG=/opt/tivoli/tsm/serverA /dsmserv.opt
nohup /opt/tivoli/tsm/server/bin/dsmserv quiet &

3.3 The following command if your shell is in the ksh family:

export DSMSERV_DIR=/opt/tivoli/tsm/server/bin
export DSMSERV_CONFIG=/opt/tivoli/tsm/serverA/dsmserv.opt
nohup /opt/tivoli/tsm/server/bin/dsmserv quiet &

For server_b:

1. Change to the server_B instance directory.

cd /opt/tivoli/tsm/server_B

2. Edit’s its dsmserv.opt file (the bare minimum setup below):

commmethod tcpip
tcpport 1501
commmethod http
httpport 1521
devconfig devcfg_serverB.out
volhist volhist_serverB.out

3. Format the database and recovery logs files. For example, to format two 10 GB database volume and a 1 GB recovery log volume, enter:

dsmfmt –g –db server_B_dbvol1.dsm 10 server_B_dbvol2.dsm 10
dsmfmt –g –log server_B_logvol1.log 1

4. Initialize the database and recovery log in the new server directory:

dsmserv format 1 server_B_logvol1.log 2 server_B_dbvol1.dsm server_B_dbvol2.dsm

5. When the server is started, it searches the current directory for the existence of the dsmserv.dsk file. If the file is found, the names of the recovery log and database files are used for server operation. If the dsmserv.dsk file is not found in the current directory, Tivoli Storage Manager issues an error message (ANR0212E) and server initialization stops.


6. Create server_B’s dsmserv.dsk file with contents as follows:

/opt/tivoli/tsm/server_B/server_B_logvol1.log
/opt/tivoli/tsm/server_B/server_B_dbvol1.dsm
/opt/tivoli/tsm/server_B/server_B_dbvol2.dsm

7. The TSM lock management process creates the adsmserv.lock file in the same directory as the dsmserv command. If the adsmserv.lock file is unable to be created, locked or written to, the message indicates the server is already running. To allow for the creation of a second lock file, create a soft link in server_B’s instance directory to the dsmserv command.

ln –s /opt/tivoli/tsm/server/bin/dsmserv /opt/tivoli/tsm/server_B/dsmserv

8. server_B can be started up by using

8.1 The –o parameter of the dsmserv command to specify an options file name.

8.2 The following command if your shell is in the csh family:

setenv DSMSERV_DIR /opt/tivoli/tsm/server/bin
setenv DSMSERV_CONFIG=/opt/tivoli/tsm/serverB/dsmserv.opt
nohup /opt/tivoli/tsm/server/bin/dsmserv quiet &

8.3 The following command if your shell is in the ksh family:

export DSMSERV_DIR=/opt/tivoli/tsm/server/bin
export DSMSERV_CONFIG=/opt/tivoli/tsm/serverB/dsmserv.opt
nohup /opt/tivoli/tsm/server/bin/dsmserv quiet &


9. You will also want to use the SET SERVERNAME to give each server instance a unique name in order to be able to manage these multiple TSM servers from the same ISC/Admin Center interface at 5.3 - if the multiple servers all have the same servername, then you will not be able to create a unique Admin Center connection to each of these servers while they are running on the same system. Furthermore, you may also want to set each servers internal name to something other than the defaults (the system name) for to make it easier to differentiate which one you are working on. This must be done before any device paths or server to server communication is configured.

bar