Return to site

How To Install Tsm

broken image


This page describes how to set up the Tivoli Storage Manager client software on your Windows computer, connect it to the UIC backup Server, schedule incremental backups, make sure the program is running properly, and optionally make an initial full backup.

Register Node on TSM Server

Nodename: DB2

Install TSM

[root@db2 ~]# cd /tmp/
[root@db2 tmp]# tar -xvf CZGL9ML.tar.gz
[root@db2 tmp]# rpm -i TSMCLI_LNX/tsmcli/linux86/gskcrypt32-8.0.13.3.linux.x86.rpm
[root@db2 tmp]# rpm -i TSMCLI_LNX/tsmcli/linux86/gskssl32-8.0.13.3.linux.x86.rpm
[root@db2 tmp]# rpm -i TSMCLI_LNX/tsmcli/linux86/gskssl64-8.0.13.3.linux.x86_64.rpm
[root@db2 tmp]# rpm -i TSMCLI_LNX/tsmcli/linux86/gskcrypt64-8.0.13.3.linux.x86_64.rpm
[root@db2 tmp]# rpm -i TSMCLI_LNX/tsmcli/linux86/TIVsm-API.i386.rpm
Postinstall of the API

TSM Linux API installation complete.

Be sure to set up the configuration files!

[root@db2 tmp]# rpm -i TSMCLI_LNX/tsmcli/linux86/TIVsm-API64.i386.rpm
Postinstall of the API64

TSM Linux API64 installation complete.

Be sure to set up the configuration files!

[root@db2 tmp]# rpm -i TSMCLI_LNX/tsmcli/linux86/TIVsm-BA.i386.rpm
Postinstall of the Backup Archive client

TSM Linux client installation complete.

Be sure to set up the system configuration file
before starting the client!

Configure TSM

[root@db2 tmp]# cd /opt/tivoli/tsm/client/api/bin64/
[root@db2 bin64]# cp dsm.sys.smp dsm.sys
[root@db2 bin64]# chmod 666 dsm.sys
[root@db2 bin64]# vi dsm.sys

SErvername TSMSrvCOMMMethod TCPipTCPPort 1500TCPServeraddress 192.168.0.5passwordaccess generatepassworddir /home/instown1

nodename DB2

[root@db2 bin64]# vi dsm.opt

servername TSMSrv

[root@db2 bin64]# chmod 666 dsm.opt
[root@db2 bin64]# cd /opt/tivoli/tsm/client/ba/bin/
[root@db2 bin]# ln /opt/tivoli/tsm/client/api/bin64/dsm.sys dsm.sys

Configure DB2 and set DB2 to archive log mode

[root@db2 bin]# su – instown1
[instown1@db2 ~]$ vi sqllib/userprofile

DSMI_DIR=/opt/tivoli/tsm/client/api/bin64DSMI_CONFIG=/opt/tivoli/tsm/client/api/bin64/dsm.optDSMI_LOG=/tmpexport DSMI_CONFIGexport DSMI_DIR

export DSMI_LOG

[instown1@db2 ~]$ db2stop
[instown1@db2 ~]$ db2start
[instown1@db2 ~]$ db2 update db cfg for dbname using logarchmeth1 tsm
[instown1@db2 ~]$ db2 backup db dbname to .

Configure TSM Scheduler

How To Install Tsm Youtube

[instown1@db2 ~]$ mkdir tsm
[instown1@db2 ~]$ vi tsm/tsmbackup.sh

#!/bin/kshLOG=/home/instown1/tsm/db2backup_${DOW}.log./home/instown1/sqllib/db2profileDB=dbname

KEEP_FULL=10

#

# First backup the database

#

db2 backup db $DB online use tsm >> $LOG 2>&1

#

# Verify if return code from backup is 0

#

RC=$?

if [ $RC != 0 ]

then

echo '$RC'

echo 'Backup was not successful'

exit 1

fi

#

# Get the timestamp from backup out of logfile

#

TIMESTAMP=$(tail -3 $LOG | awk ‘{print $11}')

#

# Verify backup

#

#

db2adutl verify full taken at $TIMESTAMP db $DB without prompting >> $LOG 2>&1

#

# Check if verification is ok

#

#RC=$?

#if [ $RC != 0 ]

#then

#echo 'Verify was not successful'

#exit 1

#fi

#

# Delete full DB backups and keep $KEEP_FULL

#

db2adutl delete full keep $KEEP_FULL db $DB without prompting

#

# This is the tricky part to determine the oldest logfilenumber

# We assume that the last image in the query output has the oldest log number

# We had to subtracte one from the oldest logfile in order to keep the

# last backup valid.

#

let OLDEST_LOG=$(db2adutl query full nonincremental db $DB | tail -2 | awk ‘{print $6}' | cut -c2-8 )

let OLDEST_LOG=$OLDEST_LOG-1

OLD_LOG=$(printf '%-7.7d' $OLDEST_LOG)

OLD_LOG='S$OLD_LOG.LOG'

# Now delete obsolete logs

#

db2adutl delete logs between S0000000.LOG and $OLD_LOG db $DB without prompting

exit 0

[instown1@db2 ~]$ chmod 744 tsm/tsmbackup.sh
[instown1@db2 ~]$ exit
[root@db2 ~]# nohup dsmc sched &

Advertisements

System Engineer @ATOS, vExpert2015, VCP5, RHCSA, Specialized Linux,Storage and Virtualization.

Tagged with: Backup, DB2, TSM
Posted in Database, Storage

Note: If you are installing this on Ubuntu or debathena, please view [these instructions].
On this page:

  • 1Install TSM
  • 2Configure TSM
  • 3Install the Scheduler
  • 4Confirm Scheduled Backups; Check the TSM Schedule Log Periodically
  • 5Other Distributions

Instructions are for both new installations and updates of a pre-existing one. Assume that all TSM files have been left in their default locations when performing an upgrade.

Note: The dsm GUI command is no longer available. It has been replaced by the dsmj command which has comparable functionality.

Install TSM

  1. Download the Linux TSM 6 installation archive and Sun's JRE, if necessary, to your workstation from the Software Grid
  2. Extract the contents of the installation file using the command below:
    tar xvf 6.2.2.0-TIV-TSMBAC-LinuxX86.tar
    Result: The following files appear:
  3. Log in as the root user.
  4. If you have an existing TSM backup installation, perform the following two sub-steps; otherwise, skip to the next step.
    1. cd to /opt/tivoli/tsm/client/ba/bin and add the following line to the 'dsm.sys' file with a text editor if it is not already present:
    2. cd to the /etc directory and add the following line to the /etc/inittab file with a text editor if it is not already present:
  5. For Red Hat Enterprise only (all others skip to the next step), you need to install the compat-libstdc++-33-3.2.3 rpm if it is not already installed. The easiest way to install it (and other needed Red Hat rpms) is via the Red Hat update service using 'yum'.
    For example, yum install compat-libstdc++-33-3.2.3
  6. Java issues:
    • To use the GUI dsmj client, you will need a compatible Java runtime installed and on your path ahead of any other Java versions you may have already installed.
    • IBM specifies a version 1.5 or 1.4.x, with x >=1. A number of Red Hat supplied Java 'compat' rpms (such as java-1.4.2-gcj-compat-1.4.2.0-26jpp.noarch.rpm supplied with RHEL4) are NOT compatible.
    • IBM recommends using Sun's JDK or JRE.
    • The self-extracting installer is available from www.java.com
  7. Use the cd command to move to the directory where the installation packages are located.
  8. If you are updating a prior TSM installation, perform Step a. If you are performing a new installation, go to Step b.
    1. Updating a prior installation:
      Enter the following commands to update the TSM Backup-Archive client (command-line, API and GUI), the administrative client (command-line), and the Web client:
      1. 32 Bit:
      2. 64 Bit:
    2. Starting with a new installation:
      Enter the following commands to install the TSM Backup-Archive client (command-line, API and GUI), the administrative client (command-line), and the Web client.
      1. 32 Bit:
      2. 64 Bit:

Configure TSM

Install

If you are setting up TSM on your system for the first time, perform all the steps below.

You'll need to download the MIT TSM sample configuration files for UNIX --'dsm.sys' and 'dsm.opt' -- and then edit the 'dsm.sys' file as described below.

  1. Copy the MIT sample configuration files to this directory: /opt/tivoli/tsm/client/ba/bin
  2. Open the dsm.sys file in a text editor, and enter your TSM nodename in the 'NODename' line.
  3. Specify your assigned TSM server by uncommenting the appropriate 'TCPServeraddress' line.

If you are unsure of your TSM server, check the confirmation email sent from the Service Desk, or contact the Computing Helpdesk: 617-253-1101 or helpdesk@mit.edu.

Install the Scheduler

  1. Become 'root' if you are not 'root' already.
  2. Add the following entry to the /etc/inittab file:
  3. After modifying your configuration, your TSM Scheduler needs to be restarted. The easiest way to do this is to reboot. You will need to do this again any time you make further configuration changes.

Confirm Scheduled Backups; Check the TSM Schedule Log Periodically

  1. Check the Schedule Log, /opt/tivoli/tsm/client/ba/bin/dsmsched.log
  2. Use a text editor to open the schedule log.
  3. Go to the end of the log and look for confirmation that the backup completed. Look for completion summary beginning with the text:
  4. You may find it helpful to create an alias on the desktop as a reminder to periodically check it.

Other Distributions

How To Install Tsm Apphelper

Note: The Linux distribution listed below is unsupported by IS&T. Our staff members were able to get TSM 6 running on it and the summary information provided is intended to assist you if you wish to attempt such an installation with TSM 6. We will be able to provide only minimal, 'best effort,' assistance if you run into difficulties.

As per the detailed RHEL instructions above, if you are updating an existing TSM installation, you must first delete the existing TSM rpms with rpm -e followed by an install of the new rpms with rpm -i; do not use the rpm -Uvh update command.

Fedora Core 14:

  1. Install as above.
  2. Using /etc/inittab to autostart 'dsmc sched' doesn't seem to work any more, so using the method below seems to work sufficiently.
    Create /etc/init/dsm-sched.conf with the contents:
  3. The first line of /opt/tivoli/tsm/client/ba/bin/dsmj needs to be edited to #!/bin/ksh as Fedora puts ksh in /bin.




broken image