TSM 6 for Linux - Install, Configure, Set Up, and Confirm the Scheduler

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

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 LINK TO SOFTWARE PAGE and Sun's JRE, if necessary, to your workstation from the MIT Software: Linux page. [Certificates required.]
2. Extract the contents of the installation file using the command below:
   tar xvf tsm6200lnx.tar
   
   Result: The following files appear:
   
   

   NOTICES.TXT
   README_api_enu.htm
   README_enu.htm
   README_hsm_enu.htm
   TIVsm-API.i386.rpm
   TIVsm-API64.i386.rpm
   TIVsm-BA.i386.rpm
   TIVsm-HSM.i386.rpm
   gskcrypt32-8.0.13.3.linux.x86.rpm
   gskcrypt64-8.0.13.3.linux.x86_64.rpm
   gskssl32-8.0.13.3.linux.x86.rpm
   gskssl64-8.0.13.3.linux.x86_64.rpm
   

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:
      

      ERRORLOGName /opt/tivoli/tsm/client/ba/bin/dsmerror.log
      

   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:

      tsm::once:/usr/bin/dsmc sched > /dev/null 2>&1
      

5. For Red Hat Enterprise only (all others skip to the next step), you need to install the compat-libstdc++-296-2.96 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 up2date (RHEL4) or yum (RHEL5).
   Additionally, if you are using a 64 bit Red Hat operating system, you will also need to install the following rpm if it is not already installed:
   compat-libstdc++-33-3.2.3
   
   Additional requirements for RHEL5:
   You may need to install the following additional rpms:
   ksh-20060214 (if ksh is not present on your computer)
   libXp-1.0.0 (if libXp.so is not present on your computer)
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:

         rpm -e TIVsm-BA
         rpm -e TIVsm-API
         rpm -i gskcrypt32-8.0.13.3.linux.x86.rpm
         rpm -i gskssl32-8.0.13.3.linux.x86.rpm
         rpm -i TIVsm-API.i386.rpm
         rpm -i TIVsm-BA.i386.rpm
         

      2. 64 Bit:

         rpm -e TIVsm-BA
         rpm -e TIVsm-API64
         rpm -e TIVsm-API
         rpm -i gskcrypt32-8.0.13.3.linux.x86.rpm
         rpm -i gskcrypt64-8.0.13.3.linux.x86_64.rpm
         rpm -i gskssl32-8.0.13.3.linux.x86.rpm
         rpm -i gskssl64-8.0.13.3.linux.x86_64.rpm
         rpm -i TIVsm-API.i386.rpm
         rpm -i TIVsm-API64.i386.rpm
         rpm -i TIVsm-BA.i386.rpm
         

   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:

         rpm -i gskcrypt32-8.0.13.3.linux.x86.rpm
         rpm -i gskssl32-8.0.13.3.linux.x86.rpm
         rpm -i TIVsm-API.i386.rpm
         rpm -i TIVsm-BA.i386.rpm
         

      2. 64 Bit:

         rpm -i gskcrypt32-8.0.13.3.linux.x86.rpm
         rpm -i gskcrypt64-8.0.13.3.linux.x86_64.rpm
         rpm -i gskssl32-8.0.13.3.linux.x86.rpm
         rpm -i gskssl64-8.0.13.3.linux.x86_64.rpm
         rpm -i TIVsm-API.i386.rpm
         rpm -i TIVsm-API64.i386.rpm
         rpm -i TIVsm-BA.i386.rpm
         

Configure TSM

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:

   tsm::once:/usr/bin/dsmc sched > /dev/null 2>&1
   

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:

   *SCHEDULEREC STATUS BEGIN*
   

4. You may find it helpful to create an alias on the desktop as a reminder to periodically check it.

Other Distributions

Note: The Linux distributions listed below are unsupported by IS&T. Our staff members were able to get TSM 5.4 running on them 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 6:
Installs as for RHEL4 and RHEL5. Java from Sun j2re-1_4_2_15-linux-i586.rpm was used.

openSUSE 10.2:
Installs as for RHEL4 and RHEL5. Java from java-1_4_2-sun-1.4.2_update13-3.1 in the SuSE software installer was used.

Ubuntu 7.04:
IBM rpms were converted with alien to .deb as follows:

• alien --scripts TIVsm-BA.i386.rpm
• alien --scripts TIVsm-API.i386.rpm

The .deb files were installed with:

• dpkg -i tivsm-api-5.4.1-1-i386.deb
• dpkg -i tivsm-ba-5.4.1-1-i386.deb

ksh needed to be installed with:

• apt-get install ksh

To set up automatic start of dsmc scheduled backup daemon at boot, it was necessary to use a SysV boot script in /etc/init.d as this Ubuntu release does not have /etc/inittab.

Java from Sun jre-1.4.2_15-linux-i586.bin was used.