5. Configuration

TSM needs two configuration files:
  • dsm.sys
  • dsm.opt
Example versions of these files are installed in the installation directory /opt/tivoli/tsm/client/ba/bin/ and they are dsm.opt.example and dsm.sys.example (or dsm.opt.oucs and dsm.sys.oucs in older package versions.

In older versions there was an incl.excl where the include and exclude statements were placed.

The installation process should configure these files for you, but if you feel the need to edit them yourself you may find helpful our page on manually configuring TSM for Linux/Unix.

5.1. Editing the dsm.sys file

VirtualMountPoint
The option VirtualMountPoint can be used to logically partition your filespaces, but more usefully can give basic backup and restore functionality on unsupported filesystems. For more details on the virtualmountpoint option take a look at our page on supported Linux and Unix file systems.

5.2. Editing the dsm.opt file

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.

5.3. Editing the include excludes

Traditionally include and exclude statements used to be placed in incl.excl. Now they are put into dsm.sys. Include and Exclude statements offer a finer discrimination than the Domain line in the dsm.opt file, limiting what is backed up from within filesystems. You should study the include and excludes within dsm.sys, consider your filestore usage, and amend the file to avoid backing up unnecessary files (for example, temporary files used by programs and utilities, virtual machine images, spool files, cached web pages and so forth). Backup performance can be greatly improved by not backing up unnecessary files.

If you have an old customised incl.excl file, these statements will have been merged into the dsm.sys file on an upgrade.

TSM processes the Exclude.fs then Exclude.dir before any of the Exclude file directives. Each group of directives is then processed working from the bottom to the top of the list. You can view the order of this processing by running: 

dsmc query inclexcl

To quit the session, issue quit at the prompt. For further help on includes/excludes see our page on how to exclude files and folders from backup.

5.4. Log file location

TSM also writes a number of log files, the locations of which are controlled by the variable DSM_LOG set in the wrapper shell scripts dsmc, dsmj, dsmcad in /usr/bin. By default these are set as below:

Log file Location Description
dsmerror.log $HOME Logs any errors when running manual backups
dsmsched.log /var/log Logs all transactions when running scheduled backups
dsmwebcl.log /var/log Logs the time of next scheduled backup
dsmerror.log /var/log Logs any errors when running scheduled backups

5.5. Running the TSM client as a non-root user

By default non-root users are not able to use the TSM software to back up and restore their own files. Should you wish to enable this functionality, do as follows:
  • Make the setuid bit on the /opt/tivoli/tsm/client/ba/bin/dsmtca executable, by running the following command as the root user: 
     chmod 4555 /opt/tivoli/tsm/client/ba/bin/dsmtca
  • Ensure that there is access to dsmerror.log. You can do this by changing the value of errorlogname in dsm.sys from the default (/var/log/dsmerror.log) to a location where the user concerned has access, e.g. their home directory. An alternative is to change permissions on /var/log/dsmerror.log, to enable write-access.
This will enable a non-root user to back up and restore only their own files. To back up and restore all files, please run TSM as the root user.

Up: Contents Previous: 4. Upgrading from TSM client version 5.3 or below Next: 6. Initial Backup using the TSM Client