A member of the Enterprise Recovery Group needs to add your system, hereafter called node, to the server using the administrator GUI, and then add the node to the appropriate schedule.

If your node already has TSM, stop the scheduler service then remove the previous version of Tivoli.

As root , run the following commands (This creates a temporary directory to store the installation files.):

Note: Uncompressed file is 297mb

mkdir /tmp/tsm
cd /tmp/tsm

Access [ http://help.unc.edu/?id=6327 ] Tivoli Storage Manager help document for current IBM TSM client downloads.

Review the README files for the latest news and APAR's for this client. Also, be aware that if you accept defaults regarding where to install things, then you can ignore setting the DSM_CONFIG and other environment variables.

Follow the README.FTP instructions to install the software: When it asks for files to install, press F4 for a list and install all but ba.gpfs, hsm.gpfs, hsm.jfs2 and client.jbb. Explicitly select to install all xlC.aix50, xlC.msg.en, xlC.rte files.

Change to the directory where the client is installed:

cd /usr/tivoli/tsm/client/ba/bin

Use a web browser to access this web site: [ https://its.unc.edu/esm/backup/TSM_Clients/AIX/ ] https://its.unc.edu/esm/backup/TSM_Clients/AIX/ and copy the dsm.opt , dsm.sys , and inclexcl.dsm files to the above directory. (If you are already using TSM you do not need to change these files, only save them):

/usr/tivoli/tsm/client/ba/bin/

Modify the dsm.opt, dsm.sys, and inclexcl.dsm files customizing each for your system.

Type the command dsmc . At the prompt type the password given to you by the TSM administrator, then exit and retype dsmc . If it doesn't ask for a password and doesn't report errors, the client is installed correctly.

For non-root users (like "oracle") can run dsmc backup/restore scripts, do the following:

cd /usr/Tivoli/tsm/client/ba/bin (or the directory you use for TSM logs) 
touch dsmprune.log
chmod 666 dsmerror.log dsmprune.log dsmwebcl.log

TSM needs port 1500 (communication from client to backup server) and port 1501 (communication from backup server to client) open in the firewall, which allows the backup server to initiate automated backups.

To start the TSM client on reboot, edit /etc/inittab and insert the line:

ad:2345:respawn:/usr/bin/dsmc sched >/dev/null2>&1

Then run the following command from the /etc directory:

telinit q

This will cause the program to rerun its inittab and start a client schedule daemon. To verify the daemon is running, run the command:

ps aux | grep dsm

To verify the client scheduler log is working run the following command:

more /usr/tivoli/tsm/client/ba/bin/dsmsched.log

Do a manual backup by typing:

dsmc incremental

When this manual backup is complete, check the results of the dsmsched.log file and make sure the last few lines states "waiting to be contacted by server" .

The day after any significant change to your client (TSM client or server software update, client operating system or hardware upgrade, etc.), check the results of the dsmsched.log file. If you have any errors, contact the TSM administrator. Otherwise, daily monitoring of your client is handled by our automated systems, which will alert you by email only if problems occur.