Frequently asked questions (FAQs) about the backup system

Back to overview

The backup client supports common operating systems such as Windows, Linux or macOS.

A detailed list of supported operating systems can be found here (external link): Overview - IBM Storage Protect Supported Operating Systems

Information on the retention period of your backup can be found under Retention periods.

Read the explanation of node name / node name in the glossary.

It is possible that your computer is protected by a firewall. The outgoing TCP port 1500 should be open on your computer.

If you have problems with your registration, you can get help via our online form or our IT service desk.

It might help to increase the TCP/IP options Buffer size (max. 512) and Window size (for Windows max. 63). This can be done in the TSM client via Edit - Preferences - Transmission, where you can enter the values or directly in the option file dsm.opt TCPBUFFSIZE and TCPWINDOWSIZE with the desired value, and the scheduler must be restarted for automatic backup.

If you are using the TSM scheduler and have made changes to the options (such as DOMAIN, INCLUDE or EXCLUDE), but these changes are not visible in the backup, it could be because the scheduler process has not been restarted.

You can set the client so that old data records are always deleted from the log file. With the Windows client, this works as follows:

Open the Tivoli client (Save-Archive GUI)
At the top of the bar, go to Edit and click on Client Preferences. There click on "Scheduler". Under the heading Scheduling log you can check the box "Clean up old entries" and enter a number of days (e.g. 7).
You must then restart the scheduler so that the cleanup is triggered.
In the Linux client, the option "SCHEDLOGRetention 7 D" must be in the dsm.sys file. (e.g.)

The problems are most likely due to the character set used by the Linux system (UTF-8). You can solve the problem by exporting the variables LANG=de_DE@euro and LC_ALL=de_DE@euro in the shell before calling TSM. When using the automatic backup, these two variables must also be set to de_DE@euro in the startup script /etc/init.d/tsm.

If it still does not work, try to generate the character set with:

locale-gen de_DE or sudo locale-gen de_DE (under Ubuntu this is often the case).

An entry may also be missing for generation in the file:<<BR>>

/etc/locale.gen

If the line de_DE ISO-8859-15 is not present there, you should add it and then trigger the generation with locale-gen de_DE.

With 64-bit Linux, it is possible that some 32-bit libraries are not installed.

You can find out which libraries are missing with the command

  • ldd /usr/bin/dsmc
  • The missing libraries must be installed. Libstdc++.so.6 is usually missing
    It is installed with
    apt-get install lib32stdc++6
    (previously searched for with apt-cache search libstdc++)

In this case, the version number of the libcurl library from the TSM package does not match. Remedy:
Delete the line
/opt/tivoli/tsm/client/ba/bin
from the file
/etc/ld.so.conf
and then execute the command
ldconfig
. Everything should then work again.