1. Introduction

From TSM 5.4 onwards, users can automatically configure TSM on installation. However, there may be cases where one wants to configure the client manually - if the installation fails then you may prefer to edit the relevant files by hand rather than using the HFS helper scripts. If this is the case, the important parameters are usually commented out: comments start with a * at the beginning of the line - to uncomment, remove the *. See the following two sections for which entries to edit in the two TSM configuration files, dsm.sys and dsm.opt.

2. Editing dsm.sys

The important parameters are: Nodename, Servername, TCPServer, TCPPort.

An example of part of dsm.sys for an unconfigured client due to a problem with post-installation is as follows: 

    
               *                     Linux Client for TSM
               
               * This is the example dsm.sys file for use with Backup to the
               * HFS at Oxford. As supplied, it must be edited as described
               * below.  
               
               * Server settings: these determine which part of the HFS
               * service you back up to. If the installer has found your
               * node on a server then it will have automatically configured
               * these for you as well as the nodename below. If it failed
               * to do so, then they will be commented out.
               
               *SErvername             UNKNOWN
               *TCPServer              dsmbNUM.ox.ac.uk
               *TCPPort                0
               
               *NODEname               CHANGE.THIS
The three server parameters Servername, TCPServer and TCPPort need to be configured as per the entries for Server Name, DNS Name and Port, respectively, in the table below.
Server Name DNS Name IP Address Port HFS Service
OX_HFS dsma.ox.ac.uk 163.1.219.9 2000 Archive
OX_HFS_B1 dsmb1.ox.ac.uk 163.1.219.1 1500 Desktop Backup
OX_HFS_B3 dsmb3.ox.ac.uk 163.1.219.3 1600 Desktop Backup
OX_HFS_B5 dsmb5.ox.ac.uk 163.1.219.5 1700 Desktop Backup
OX_HFS_B7 dsmb7.ox.ac.uk 163.1.219.7 1800 Desktop Backup
OX_HFS_B2 dsmb2.ox.ac.uk 163.1.219.2 2500 Server Backup
OX_HFS_B4 dsmb4.ox.ac.uk 163.1.219.4 2600 Server Backup
OX_HFS_B6 dsmb6.ox.ac.uk 163.1.219.6 2700 Server Backup
OX_HFS_B8 dsmb8.ox.ac.uk 163.1.219.8 2800 Server Backup
OX_HFS_B10 dsmb10.ox.ac.uk 163.1.219.15 2900 Server Backup
OX_HFS_VPN dsmvpn.ox.ac.uk 163.1.219.10 3200 VPN-based Backup

Except as described below and in the comment lines in these files, please do not make arbitrary changes to the values of options unless advised specifically by OUCS.

Nodename
Edit the Nodename value from CHANGE.THIS to the name that your client was registered as for TSM backup. Typically this will be of the form name.dept or username-freetext-dept.
VirtualMountPoint
The option has two functions: it can either be used to logically partition your filespaces, on which see the relevant section in our page on backing up machines which have high file counts; and to give basic backup compatibility support, on which see our page on supported Linux and Unix file systems.

3. Editing dsm.opt

Domain
Amend the Domain line to list the local filesystems you wish to have backed up. This list should be space-separated and may be specified on multiple lines to additively list a number of filesystems, as below: 
                     Domain              /   /usr   /usr/local
                     Domain              /data/01   /data/02
Please avoid backing up filesystems such as /tmp and /var/tmp which contain nothing of a permanent nature. Please also avoid backing up NFS-mounted filesystems; these should be backed up from their home machine. A symbolic link to a filesystem cannot be included in the Domain list.
Servername
Strictly the Servername option does not have to be defined in dsm.opt, but if it is then it must match the Servername defined in dsm.sys.