tsm 6 client linux

Installing the TSM Version 6 Client for Linux

1. Platform Support

These pages contain information about, and links to, the latest HFS packages of the IBM Tivoli Storage Manager Client for Linux on Intel x86 and x86_64 platforms.

Up until version 6.2 the TSM client was 32-bit and could be used on x86 and x86_64 platforms. From version 6.3 IBM have made the client 64-bit so it runs on x86_64 platforms only. The

32-bit x86 platform is still supported but you must use the version 6.2 client. The HFS packages make sure you have the appropriate version for your system installed.

The latest HFS packages provide the IBM TSM Client Version 6 Release 4 Level 0.7 (referred to numerically as 6.4.0.7) for 64-bit systems and Version 6 Release 2 Level 5.0 (6.2.5.0) for

32-bit systems.

These versions of the client include native support for the following filesystem types: EXT2, EXT3, EXT4, JFS, XFS, NSS, ReiserFS, VxFS, and GPFS.

IBM officially supports (to varying degrees) the TSM Linux client on recent versions of Red Hat Enterprise Linux, SUSE Linux Enterprise Server, CentOS, Debian, Fedora, Oracle

Enterprise Linux, Scientific Linux, SUSE Linux Enterprise Desktop, RedHat Desktop, Asianux, Mandriva, and Ubuntu. However in practice just about any recent Linux distribution (based

on the 2.6 or 3 kernel) should be able to run the TSM backup/archive client software and we have successfully tested on a number of others. In certain cases it may not be possible to run

the Java GUI client but even then the command line client can usually be installed and run.

2. Prerequisites

The preferred method of installation is using the IT Services HFS software repositories. When doing this software prerequisites should be automatically installed. These include:

Item Version Notes

libstdc++ 5 (for 6.2 client) and 6

X Window System required for the GUI

Java runtime JRE 5 or 6 required for the GUI

acl >2.0.19 required for EXT2/EXT3/XFS ACL support

IBM GSKit libraries supplied with the TSM client software

It is possible to run the command line application without having to have a Java runtime or X Window System installed.

The TSM software installs in /opt/tivoli and /usr/local/ibm. It must be possible to create these directories (if they don't exist) and write into them.

You will also need a standard 100Mb/s (or faster) network connection to the University network or a connection to the Oxford eduroam wireless network (please see page on backing up

over wireless for more details). The HFS only supports VPN-based backup for systems registered for VPN-based backup.

3. Installing or Upgrading the TSM Client

3.1. General outline

The installation or upgrade procedure depends on the distribution and version of Linux you are using. For most recent Linux releases you download and install a package that configures

your system to use the HFS repository. You then install the TSM client from that repository which means all dependencies will be automatically installed and also you will automatically get

TSM client updates alongside all your other software updates.

The Linux repositories are signed. If you wish to confirm the signing key refer to Checking the repository signing key.

For Linux versions that don't have repository support you can download and install from rpm files, or for distributions that don't support rpm (e.g. Gentoo) we provide a tar file that can be

used to install the TSM client.

When installing the TSM client for the first time the HFS-packaged TSM Client will ask for your nodename, password, and whether you want to run scheduled backups, and will then

automatically configure the TSM software correctly to connect to the HFS service.

Provided it finds an existing valid configuration the installer will upgrade that configuration without any further input on your part. If you were previously running scheduled backups the

installer will stop the old scheduler before upgrading the software then restart it afterwards. It will upgrade your dsm.opt and dsm.sys configuration files. Note that if you are upgrading

from TSM version 5.3 or earlier you should read the section Upgrading from TSM client 5.3 or below.

If something does go wrong with the upgrade process your old configuration files will have been saved with the suffix .SAVE, for example as /opt/tivoli/tsm/client/ba/bin

/dsm.opt.SAVE.

If it can work out how to do it, the installer will create a desktop menu item for Tivoli Storage Manager. When you select this you will usually be prompted for a password to enable you to

run this with administrative privileges.

The TSM Linux client installs into /opt/tivoli/tsm/client/ with some additional files placed in /usr/bin. The GSKit packages installed as a dependency install into

/usr/local/ibm.

The relevant executables are:

dsmj The Java GUI client

dsmc The command line client

dsmtca The 'trusted client agent', which allows non-root users to connect to the HFS

A file /etc/TIVGUID is created the first time a client is run. This file holds the Global Unique Identifier that associates a TSM client with a TSM server and should not be edited or

removed.

The password for the HFS account will be stored in an encrypted form, readable only by root, in /etc/adsm/TSM.PWD.

We want to use cookies to collect data on how people use our site. Click here to accept, and dismiss this notice. For more information, and to change your preferences later, see our cookie policy.If you prefer not to accept them you may disable them (this sets a cookie).

[IT Services] Installing the TSM Version 6 Client for Linux http://www.oucs.ox.ac.uk/hfs/clients/supported/linux/index.xml?splitLevel=-1

1 of 12 5/21/2013 1:40 PM

If you have installed from the IT Services HFS repository you will get TSM client updates along with all your other system updates.

If you have specific installation problems then email [email protected] attaching /opt/tivoli/tsm/client/ba/bin/tsm-install.log. This describes what the post installation

scripts have attempted to do, and highlights any problems. It may also be required to email the following files: dsm.sys, dsm.opt.

3.2. Choosing the installation method

The following table gives links to the correct procedure for installation and upgrade from versions 5.4 and above for various Linux distributions. If a distribution/version is not in the table it

doesn't mean you can't use TSM - it just means we haven't tried it - so review the different procedures and select the one that fits your distribution best. For distributions that use rpm

packages but can't use the HFS repository see 3.3.5. Manual RPM Install. For upgrades from TSM version 5.3 or lower see 4. Upgrading from TSM client version 5.3 or below

Distribution Version Install/update method Notes

Centos 4, 5, 6 Red Hat based systems see note 1

Debian 5, 6, 7 Debian based systems

Fedora 12, 13, 14, 15, 16, 17 Red Hat based systems see note 2

Gentoo tar file

Linux Mint 9, 10, 11, 12, 13, 14 Debian based systems

Mandriva 2010.2, 2011 Mandriva systems

Mageia 2, 3 Mandriva systems

OpenSUSE 11.2, 11.3, 11.4, 12.1, 12.2, 12.3 SUSE systems

Red Hat Enterprise Linux 4, 5, 6 Red Hat based systems see note 1

Scientific Linux 4, 5, 6 Red Hat based systems see note 1

Ubuntu 8.04 LTS, 10.04 LTS, 10.10, 11.04, 11.10, 12.04 LTS, 12.10 Debian based systems see note 2

Note 1: The TSM client version 6.2 will not run on Red Hat Enterprise Linux 4 or on version 4 of distributions based on RHEL4. However you can still follow these installation instructions

which will result in the 6.1 client being installed on these Linux versions.

Note 2: We have had reports of problems with TSM on the latest versions of Fedora (Fedora 18) and Ubuntu (Ubuntu 13.04): the TSM installer does not complete, and TSM cannot be run.

The problem does not occur on all installations of Fedora 18 or Ubuntu 13.04 and we have as yet been unable to reproduce it on a test system. Nonetheless at the moment we cannot

guarantee that you can run TSM on these Linux versions. We will continue to investigate the problem.

3.3. Installation

3.3.1. Debian based distributions (e.g. Debian, Ubuntu)

3.3.1.1. Setting up the repository

Download the ox-hfs-repo package from ftp://ftp.hfs.ox.ac.uk/repo/apt/deb/ox-hfs-repo.deb. If you download this using a browser you may be prompted to install it. You can do it this way

if you wish (the details will vary from one distribution to another). Alternatively save the file somewhere, open a command shell, change to the directory where you saved the file, and run

(as root or prefixed with sudo).

dpkg -i ox-hfs-repo.deb

3.3.1.2. Installing the TSM client

You can now install the TSM client using apt:

Make sure the universe repository is enabled in /etc/apt/sources.list1.

Update your list of packages with apt-get update2.

To install the full TSM client including GUI support do apt-get install tsm-client3.

Alternatively to install the command line only TSM client do apt-get install tsm-client-base4.

The selected package as well as some packages it depends on (including gskcrypt32 and gskssl32 for TSM 6.2 or gskcrypt64 and gskssl64 for TSM 6.3) will be installed. For new

installs you will be prompted for your TSM nodename and password and will be asked whether you want to run scheduled backups.

5.

It is also possible to install the TSM client with GUI tools. However the details vary between distributions so are not covered here.

3.3.1.3. Upgrading the TSM client

If you are upgrading from TSM 6.1, 5.5 or 5.4 first install the ox-hfs-repo package as described above.

Usually the TSM client will be updated alongside all your other software updates. If you want to upgrade just the TSM client run the following two commands (as root, or prefixed with

sudo):

apt-get update apt-get install tsm-client

or

apt-get update apt-get install tsm-client-base

if you have only the tsm-client-base package installed.

If your upgraded configuration is not working and you would like to start with a fresh configuration then run:

dpkg-reconfigure tsm-client-base

This will ignore your old configuration files and prompt you for your Nodename and Password, and whether you want to run scheduled backups.

If the update was successful, you can continue to use the TSM client as previously. Your scheduled backups should also continue to function as previously.

3.3.2. Red Hat based distributions (e.g. Red Hat Enterprise Linux, Fedora, CentOS, Scientific Linux)


Download the ox-hfs-repo package from ftp://ftp.hfs.ox.ac.uk/repo/rpm/ox-hfs-repo.rpm. If you download this using a browser you may be prompted to install it. You can do it this way if


2 of 12 5/21/2013 1:40 PM

you wish (the details will vary from one distribution to another). Alternatively save the file somewhere, open a command shell, change to the directory where you saved the file, and as root

run

rpm -i ox-hfs-repo.rpm


You can now install the TSM client using yum:

Make sure you are logged in as root1.

To install the full TSM client including GUI support do yum install tsm-client2.

Alternatively to install the command line only TSM client do yum install tsm-client-base3.

The selected package as well as some packages it depends on (including gskcrypt32 and gskssl32 for TSM 6.2 or gskcrypt64 and gskssl64 for TSM 6.3) will be installed.4.

Run /opt/tivoli/tsm/client/ba/bin/HFSsetup.sh. This will prompt for a Nodename, Password, and whether to start the scheduler.5.

It is also possible to install the TSM client with GUI tools. However you will still need to run /opt/tivoli/tsm/client/ba/bin/HFSsetup.sh as root after installation.

3.3.2.3. Upgrading the client


Usually the TSM client will be updated alongside all your other software updates. If you want to upgrade just the TSM client run the following commands as root:

yum update tsm-client

or

yum update tsm-client-base



/opt/tivoli/tsm/client/ba/bin/HFSsetup.sh reconfigure



3.3.3. SUSE distributions


Download the ox-hfs-repo package from ftp://ftp.hfs.ox.ac.uk/repo/rpm/ox-hfs-repo.rpm. If you download this using a browser you may be prompted to install it. You can do it this way if

you wish. Alternatively save the file somewhere, open a command shell, change to the directory where you saved the file, and as root run



You can now install the TSM client using zypper:


To install the full TSM client including GUI support do zypper install tsm-client2.

Alternatively to install the command line only TSM client do zypper install tsm-client-base3.



It is also possible to install the TSM client with GUI tools. However the details vary between distributions so are not covered here. You will still need to run /opt/tivoli

/tsm/client/ba/bin/HFSsetup.sh as root after installation.



Usually the TSM client will be updated alongside all your other software updates. However, because of the change from 32-bit to 64-bit software you will not be automatically updated to

6.3 from an earlier version. In this case, or if you want to just install the TSM client and not other packages, run the following commands as root:

zypper update tsm-client tsm-client-base

or

zypper update tsm-client-base






3.3.4. Mandriva/Mageia distributions


Download the ox-hfs-repo package from ftp://ftp.hfs.ox.ac.uk/repo/rpm/ox-hfs-repo.rpm. If you download this using a browser you may be prompted to install it. Don't do this as it won't


3 of 12 5/21/2013 1:40 PM

install properly. Instead you must save the file somewhere, open a command shell, change to the directory where you saved the file, and run as root



You can now install the TSM client using urpmi:


To install the full TSM client including GUI support do urpmi tsm-client2.

Alternatively to install the command line only TSM client do urpmi tsm-client-base3.



It is also possible to install the TSM client with GUI tools. However the details vary between distributions so are not covered here. You will still need to run /opt/tivoli

/tsm/client/ba/bin/HFSsetup.sh as root after installation.



Usually the TSM client will be updated alongside all your other software updates. However, because of the change from 32-bit to 64-bit software you will not be automatically updated to

6.3 from an earlier version. In this case, you must first uninstall the old version:

urpme tsm-client tsm-client-base gskcrypt64 gskssl64

if upgrading from TSM 6.2, or

urpme tsm-client

if upgrading frome earlier versions. Then install the latest TSM client as described above.

If you want to just install the TSM client and not other packages, run the following commands as root:

urpmi tsm-client

or

urpmi tsm-client-base






3.3.5. Manual RPM Install

3.3.5.1. Installing

Install the HFS rpm signing key

rpm --import ftp://ftp.hfs.ox.ac.uk/repo/rpm/repodata/repomd.xml.key

Download all the RPM files from ftp://ftp.hfs.ox.ac.uk/repo/rpm/ for 64-bit Linux or from from ftp://ftp.hfs.ox.ac.uk/repo/62/rpm/ for 32-bit Linux

For 64-bit Linux install all the downloaded packages with

rpm -i ox-hfs-repo.rpm tsm-client-6.4.0.7-2.x86_64.rpm tsm-client-base-6.4.0.7-2.x86_64.rpm gskcrypt64-8.0-14.14.x86_64.rpm gskssl64-8.0-14.14.x86_64.rpm

or if you only want the command line client

rpm -i ox-hfs-repo.rpm tsm-client-base-6.4.0.7-2.x86_64.rpm gskcrypt64-8.0-14.14.x86_64.rpm gskssl64-8.0-14.14.x86_64.rpm

For 32-bit Linux install all the downloaded packages with

rpm -i ox-hfs-repo.rpm tsm-client-6.2.5.0-3.i386.rpm tsm-client-base-6.2.5.0-3.i386.rpm gskcrypt32-8.0-14.6.i386.rpm gskssl32-8.0-14.6.i386.rpm


rpm -i ox-hfs-repo.rpm tsm-client-base-6.2.5.0-3.i386.rpm gskcrypt32-8.0-14.6.i386.rpm gskssl32-8.0-14.6.i386.rpm

If this complains about missing dependencies (for example compat-libstdc++-33) you will need to find and install those packages for your distribution. If the dependent libraries are

actually installed you can try using the --nodeps switch to install ignoring dependencies. If you can't meet dependencies for the tsm-client package try omitting that - you may still

be able to install the command line only package. (Note that the ox-hfs-repo package is installed even though you can't use a repository as as it is a dependency of the

tsm-client-base package).

To automatically configure the client run: /opt/tivoli/tsm/client/ba/bin/HFSsetup.sh. This will prompt for a Nodename, Password, and whether to start the scheduler.

3.3.5.2. Upgrading

Follow the instructions above for installation only use rpm -U option in place of rpm -i, that is for 64-bit clients

rpm -U ox-hfs-repo.rpm tsm-client-6.4.0.7-2.x86_64.rpm tsm-client-base-6.4.0.7-2.x86_64.rpm gskcrypt64-8.0-14.14.x86_64.rpm gskssl64-8.0-14.14.x86_64.rpm


rpm -U ox-hfs-repo.rpm tsm-client-base-6.4.0.7-2.x86_64.rpm gskcrypt64-8.0-14.14.x86_64.rpm gskssl64-8.0-14.14.x86_64.rpm


4 of 12 5/21/2013 1:40 PM


However, if your configuration is not working after the upgrade and you would like to start with a fresh configuration then run:


Then follow the installation instructions. This will ignore your old configuration files and prompt you for your Nodename and Password, and whether you want to run scheduled backups.

3.3.6. Installing using the tar file (e.g. Gentoo)

3.3.6.1. Installing the TSM client (64-bit systems)

Download the gzipped tar file from ftp://ftp.hfs.ox.ac.uk/repo/tar/tsm-client-6.4.0.7-2.tgz

Install the software by untarring the file from the root directory.

After the TSM software has been unpacked, to automatically configure the client run: /opt/tivoli/tsm/client/ba/bin/HFSsetup.sh. This will prompt for a Nodename and

Password, and whether you want to run scheduled backups. (If you are using a system with a startup script system significantly different to that used on Debian and Redhat systems, e.g.

Gentoo, you may have to manually configure the scheduler to start).

For example:

cd /tmp wget ftp://ftp.hfs.ox.ac.uk/repo/tar/tsm-client-6.4.0.7-2.tgz cd / su - tar -xhzf /tmp/tsm-client-6.4.0.7-2.tgz /opt/tivoli/tsm/client/ba/bin/HFSsetup.sh

3.3.6.2. Installing the TSM client (32-bit systems)

Download the gzipped tar file from ftp://ftp.hfs.ox.ac.uk/repo/62/tar/tsm-client-6.2.5.0-3.tgz

Install the software by untarring the file from the root directory.

After the TSM software has been unpacked, to automatically configure the client run: /opt/tivoli/tsm/client/ba/bin/HFSsetup.sh. This will prompt for a Nodename and

Password, and whether you want to run scheduled backups. (If you are using a system with a startup script system significantly different to that used on Debian and Redhat systems, e.g.

Gentoo, you may have to manually configure the scheduler to start).

For example:

cd /tmp wget ftp://ftp.hfs.ox.ac.uk/repo/tar/tsm-client-6.2.5.0-3.tgz cd / su - tar -xhzf /tmp/tsm-client-6.2.5.0-3.tgz/opt/tivoli/tsm/client/ba/bin/HFSsetup.sh

3.3.6.3. Upgrading the TSM client.

Save the files dsm.opt, dsm.sys, incl.excl and dsmsched.rc (if they exist) to a safe area.

Remove the /opt/tivoli directory tree.

Download the tar file and untar as for a fresh installation.

Copy back the files you saved earlier (dsm.opt, dsm.sys, etc) back to /opt/tivoli/tsm/client/ba/bin/

Run the /opt/tivoli/tsm/client/ba/bin/HFSsetup.sh script, which will upgrade the existing configuration.


4. Upgrading from TSM client version 5.3 or below

4.1. Overview

TSM 5.3 and earlier clients were packaged differently. Upgrading from these involves saving your configuration, uninstalling the old version, and reinstalling the new version.

Remove the previous version as follows:

Save the files dsmsched.log, dsmerror.log, dsm.opt, dsm.sys, incl.excl to a safe area.1.

Stop the Scheduler daemon.2.

Uninstall the TSM package TIVsm-OUCS / TIVsm-OUCS-bX / tsm-client-bX3.

Delete the script file dsmsched / dsmcad-init used to start / stop the Scheduler daemon.4.

Now follow the instructions in: 3. Installing or Upgrading the TSM Client .5.

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


5 of 12 5/21/2013 1:40 PM

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.

6. Initial Backup using the TSM Client

6.1. Introduction and CLI

Having installed the TSM Backup Client software, you will now want to back up your data. There are two methods for doing this, either using the command line tool or using the Java

based GUI.

To use the command line tool, open a terminal and run dsmc. This will give you a command line interface (CLI). Or you can just run commands straight from the shell. For example

dsmc incr /home

For more in depth usage of the CLI, see Using the TSM Client Command Line Interface for Backup & Restore

6.2. Select all local partitions

To use the Java based GUI open a terminal window, become root (unless non-root usage has been enabled) and run dsmj. Alternatively find "Tivoli Storage Manager" on the desktop

menus and select that. In this case you will be asked to authenticate to run the command as root.

The GUI first displays a splash screen, and then the TSM Hub window is displayed as below. From here you can select Backup under BACKUP.


6 of 12 5/21/2013 1:40 PM

This pops up another window as below.

To just back up all local disks, click on the grey box to the left of the icon and the word Local. If you have more data than the daily backup limit you may not want to do this. Scroll down

for other examples.

The Local node in the tree has been ticked. Notice the parent node HFS-TEST-OUCS - this name will be replaced with your TSM nodename.

6.3. Back up Local Filesystems

Now to back up the files, all that is required is to click on Backup.


7 of 12 5/21/2013 1:40 PM

This will then show a progress bar as below.

It is also possible to see a report of current progress by clicking on Report. If you want to interrupt the backup process, click on the Stop button.

Once the backup process has completed then a message will pop up. It is possible for this to become hidden behind another window.


8 of 12 5/21/2013 1:40 PM

Clicking OK will return you to the TSM Hub window.

6.4. Selecting local filesystems

It is possible to select some partitions to manually back up.

To view the individual filesystems click on the small square to the left of the tick box and the word Local. This will expand the tree to display the filesystem partitions.

To select filesystem partitions click on the square grey box to the left of the partition name. In the example below the following partitions have been selected: /, /usr and /var.


9 of 12 5/21/2013 1:40 PM

To back up the files click on Backup. You may want to follow the screenshots above in 6.3. Back up Local Filesystems .

6.5. Exploring the filesystem

It is possible to expand the tree to see what will be backed up. This is done by clicking on the small square to the left of the tick box.

You may have noticed the red circle over /tmp/. This means that it has been excluded in dsm.sys. If you click on a directory or icon (in the example below bin has been selected) then

the files will be displayed in the right hand pane.

6.6. Selecting a directory


10 of 12 5/21/2013 1:40 PM

It is possible to select a particular directory to back up. In this example it is /bin/. Notice that I have clicked on the check box and then clicked on the folder icon or directory name (bin)

to show what is inside the directory as above.


6.7. Selecting a file

It is possible to select a particular file to back up (or even a number of individual files). In this example it is /etc/ssh/sshd_config.


To cancel any individual selection, click the selector box to toggle it off. To cancel all your selections first select the parent folder icon in the left hand pane, then choose the [Deselect

Items] option from the [Edit] menu.

7. Troubleshooting

7.1. On installation error ANS1357S

During the installation you may see some installation output similar to the following:

Attempting to find server... TCP probing dsmb1.ox.ac.uk 1500 ... success. Contacting TSM server: OX_HFS_B1 Attempting to store password... Attempting to connect to TSM server... connect_test() ERROR: ANS1357S. The post install script does not understand this error. Please report it to [email protected]. ...

The error message ANS1357S means "Session rejected: Downlevel client code version". This message may arise if a TSM account is used first with the Windows TSM software and then

afterwards with the Linux version of TSM.

If this is the case then it is best practice to use separate TSM accounts for the separate operating systems.

7.2. General configuration errors

If TSM cannot connect because of an invalid servername, invalid hostname, or some other configuration problem try recreating a new configuration. On Debian/Ubuntu systems this is

done with


11 of 12 5/21/2013 1:40 PM

dpkg-reconfigure tsm-client-base

On all other systems run


8. Further Help

Sources of further help include:

If you have a query about the operation of the GUI, click on the Help button or press F1.

To access help in the command line client just press h at the tsm> prompt.

If you have a query about options in the configuration files dsm.sys and dsm.opt, then please see the further instructions that appear as comments at the top of each file.

If you have a problem or query check first the help pages to see if it is answered there. If your query is still unresolved, then contact [email protected] with as much detail as possible,

including copies of the files dsm.sys, dsm.opt, dsmerror.log and, if the query relates to scheduled backup, the dsmsched.log and dsmwebcl.log files.

If you have specific installation problems then email [email protected] with /opt/tivoli/tsm/client/ba/bin/tsm-install.log. This describes what the post installation

scripts have attempted to do and highlight any problems. It may also be required to email the following files: dsm.sys and dsm.opt.

About | Contact | Privacy | Cookies | Feedback | Accessibility | © University of Oxford.

IT Services documents are available in alternative formats through advance request from the Help Centre.

Written by OUCS, OUCS. Latest revision Fri, 17 May 2013

[Change Page Style: Simple text | Printable version | Normal ]


12 of 12 5/21/2013 1:40 PM

tsm 6 client linux

Documents