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,
* 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
TCPPortneed to be configured as per the entries for Server Name, DNS Name and Port, respectively, in the table below.
Nodenamevalue 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.
- 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 file systems.
Domainline 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/02Please 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
Servernameoption does not have to be defined in
dsm.opt, but if it is then it must match the