This is an old revision of the document!

TSM

Some tips from Oxford University
Some useful TSM server queries
TSM - How to determine management class and retention using dsmc - nice syntax highlighting!

Tivoli Storage Management

Default location for files

0@@

Restart ITM Monitoring agent

To see if the Oracle module is installed

1@@

and see which agents are running

2@@

and see which agents are configured (or not)

3@@

See which instances have been setup to be monitored

4@@

5@@

Add an instance to be monitored

6@@

This one should also be done in order that rc.d scripts know to start the agent as itmora instead of root

7@@

Restart the Oracle agents

To avoid issues with orphaned processes, restart is best done with a combination of stop, cleanup, start. Stop all Oracle agents

8@@

or, the standard method…

9@@

Check agent processes have stopped

10@@

Any remaining processes (containing a SID) should be killed. It is normal to have agents for 61, ul and ux still running. Check agent RunInfo file is correct If this file is corrupted, the StartAgent.sh script does not function correctly

11@@

…and remove any lines containing database SIDs in the 4th column Start all Oracle agents

12@@

or …using ITM standard command to restart one agent

13@@

Perform cleanup as above

14@@

Check the agent is running

15@@

Reconfigure agent

16@@

Troubleshooting

cinfo -r reports processes not running (as well as running)

eg:

17@@

need to remove the first 2 lines…

18@@

and remove the unnecessary lines

Remove / uninstall / decommission an ITM agent

Check agent is configured

19@@

Stop the running agent

20@@

Delete config files for the instance

21@@

Modify the rz environment file

22@@

Modify the rz agent startup file

Remove line from “start_all” section
Remove line from “stop_all” section

23@@

Recheck if the agent is configured (SID should have gone from list)

24@@

Automate modification of ORACLE_HOME in config files and restart ITM agent for each database

After an upgrade, the hard-coded(!!!) path to ORACLE_HOME needs modifying to use the new location

25@@

Starting the TSM client

On Unix

26@@

On Windows

27@@

Send a file to TSM

28@@

Query the archive to see if a file is available in TSM

29@@

Query all the files sent to the monthly node since start of FEB 2013 (using dateformat YYYY-MM-DD)

30@@

and on Windows…

31@@

Note: You will get an error with the above command as Windows ignores the dateformat on the command line! To fix it, put dateformat 3 in the opt file.

List all export jobs on this TSM node

32@@

Retrieve file from TSM

33@@

This opens an interactive window listing all files that match the file query (note the wildcard) Files can be toggled on and off for recovery by pressing the number associated with the file then recover with the letter o (for ok!). If several versions of the same file exist, use the description field to make the distinction

34@@

Retrieve a file from TSM and save it to a different name

35@@

Restore a file from TSM (from backup not archive)

36@@

Check backup is performed across DWDM (diagonal) to TSM server in remote location

Some customers want the backups of the databases running in one data centre to be sent to the other data centre providing “data centre down” recovery. Put this into a temporary file on the management server…

37@@

then send it to, and run it on, all the satellite servers…

38@@

This spits out a list of host | Instance | TSM server If this list is pasted into a spreadsheet, a formula in Column 4 will show any bad ones (still backed up to the local data centre).

39@@

Obviously this is customer specific! Character positions 3-4 of the hostname show where the server is hosted, positions 4-5 of the TSM server name show its location.

Show details about all management classes on the TSM server

40@@

Query running sessions on a TSM node

41@@