Konfiguration unter Linux

After installation, some changes to the configuration are necessary, which can be made either via the graphical interface (Edit -> Preferences) or by directly editing the configuration files.
Under Linux, editing is the more common method and will therefore be described briefly here.

The configuration files are located in the installation directory (/opt/tivoli/tsm/client/ba/bin/) and are called dsm.sys and dsm.opt.
The main entries are in the file dsm.sys, which can only be written by root, while dsm.opt contains optional attributes that can be freely selected by each user.

In response to your node registration request, you have received an e-mail containing the server name and the server port number of the server on which the node was registered. 
You must now enter these in the dsm.sys. 
Here is an example of a dsm.sys for the node test node, which is on the server S10.abs.lrz.de with the port number 2500:

*### Servername is freely selectable. It only must be the same as in the dsm.opt. Our Recommendation is to call it as the NODENAME
servername Testnode
*### Configuration for the Connection to the TSM/ISP Server
nodename         Testnode
tcpserveraddress s10.abs.lrz.de
tcpport          2500
COMMMETHOD V6TCPIP
*### Please uncomment pwgen (with *) before the first login, only necessary if the Node password has not been changed yet.
PASSWORDACCESS GENERATE
*### Include Exlude List is necessary to choose which
inclexcl /opt/tivoli/tsm/client/ba/bin/dsm.excl.local
*###Setting for the automatic Backup service
managedservices schedule
QUERYSCHEDPERIOD 1
*###Logfile Location
ERRORLOGName /var/log/dsmerror.log
SCHEDLOGName /var/log/dsmsched.log
*###Logpruning after 7 Days
schedlogretention 7 D
errorlogretention 7 D

Accordingly, here, for example, is the matching dsm.opt:

*### Servername is set to the same as in the dsm.sys that the ISP Client knows which Settings belong to which node
servername Testnode
*### This Option must be set if Subdirectorys should be backuped too
SUbdir yes
*###  Specify which partitions you want to Backup
domain /media/test
domain /home/administrator

Inclexcl file for including or excluding folders and files from the backup

In dsm.sys, you can specify the path to a file containing include/exclude instructions for ISP. This allows you to explicitly exclude files and directories from the backup.
The path to this file is then entered in dsm.sys:

InclExcl /opt/tivoli/tsm/client/ba/bin/dsm.excl.local

Here you can find the detailed IBM support article on how to exclude directories and folders using this list.

Use automatic backup

When registering the node, you must indicate that you wish to use the option (within a certain time window).
However, you can also do this at any time by formulating your request in an incident via the LRZ servicedesk.

There are two different ways to start the automatic backup under Linux:

  1. You can use the shell to start the scheduler for automatic backups in this way:
    nohup dsmc schedule > /dev/null 2>&1

    Please note that the process must run as root and the option passwordaccess generate in dsm.sys must be set.

  2. Start at boot using /etc/inittab or an rc file:
    To do this, you must add the following line to /etc/inittab or the rc file:

    ISP::once:/pfad/zu/dsmc sched > /dev/null 2>&1

    Alternatively, the command can also be started using a cron job or similar. In this case, however, we have no way of notifying you in the event of an error.

Under Ubuntu 20.04 and 22.04, a systemd service is automatically set up under /etc/systemd/system/dsmcad.service, which is already active.
For this to work, however, you must create the file /opt/tivoli/tsm/client/ba/bin/dsmcad.lang and enter the variables LANG and LC_ALL accordingly.
Example for German:

LANG=de_DE.UTF-8
LC_ALL=de_DE.UTF-8

There exists also the FAQ 301 entry about it.

 The ISP Acceptor Daemon scheduler service 

This must be set up differently depending on the operating system. Therefore, please select the section that applies to your operating system.

After the setup steps, you will also find instructions on how to check whether the scheduler is working. Please also carry out these steps.

New Linux distributions based on systemctl (including SUSE Linux 15, but not Debian/Ubuntu):

Execute all of the following commands as root:

  •  Enter the following lines in your dsm.sys (default path /opt/tivoli/tsm/client/ba/bin):
    passwordaccess generate
managedservices schedule
  • Now start the Acceptor Daemon with the command systemctl start dsmcad.service. 
  • Execute a command such as dsmc query sess to save the password for the node.
  • To ensure that the service is started automatically in future, please execute systemctl enable dsmcad.service.

Older Linux distributions based on init.d (not Debian/Ubuntu):

Execute all of the following commands as root:

  • Enter the following lines in your dsm.sys (default path /opt/tivoli/tsm/client/ba/bin):
    passwordaccess generate
managedservices schedule
  • Now start the Acceptor Daemon with the command systemctl start dsmcad.service.
  • Execute a command such as dsmc query sess to save the password for the node.
  • To ensure that the service is started automatically in future, please add cad::once:/opt/tivoli/tsm/client/ba/bin/dsmcad >/dev/null 2>&1 to the /etc/inittab file.

New Debian/Ubuntu distributions:

Execute all of the following commands as root:

  • Enter the following lines in your dsm.sys (default path /opt/tivoli/tsm/client/ba/bin):
    passwordaccess generate
managedservices schedule

  • Now start the Acceptor Daemon with the command systemctl start dsmcad.service. 

  • To ensure that the service is started automatically in future, please execute systemctl enable dsmcad.service.

Older Debian/Ubuntu distributions:

Execute all of the following commands as root:

  • Enter the following lines in your dsm.sys (default path /opt/tivoli/tsm/client/ba/bin):
    passwordaccess generate
managedservices schedule
  • Execute the commands chmod a+x /etc/init.d/dsmcad and update-rc.d dsmcad defaults.
  • Execute the command dsmc q f and enter your node password.
  • Now you can start the daemon with /etc/init.d/dsmcad start. 
    If you see the error message dsmcad start this distribution is not supported: 
    Then you must edit the file rc.dsmcad under /opt/tivoli/tsm/client/ba/bin and replace the string redhat-release in the If condition with debian_version.
  • To ensure that the service is started automatically in future, please add cad::once:/opt/tivoli/tsm/client/ba/bin/dsmcad >/dev/null 2>&1 to the /etc/inittab file.

Check whether the scheduler service is working

If the scheduler service has been set up successfully, you should see an entry similar to this one in the dsmsched.log file (you can set the path to this in your dsm.sys by using the SCHEDLOGName variable):

IBM Spectrum Protect-Client für Sichern/Archivieren Version 8, Release 1, Stufe 6.0
Server wird nach dem nächsten geplanten Ereignis abgefragt.
Knotenname: Testnode
Sitzung hergestellt mit Server S10: Linux/x86_64
Serverversion 7, Realease 1, Stufe 7.300
Serverdatum/-zeit: Letzer Zugriff: 02.10.2018 10:18:16
 
--- ANFANG DER PLANUNGSPROTOKOLLABFRAGE
--- ENDE DER PLANUNGSPROTOKOLLABFRAGE
Nächste geplante Operation:
-------------------------------------
Zeitplan:              WD0900
Aktion:                Incremental
Objekte:
Optionen:
Server-Fensterstart:   09:00:00 am 03.10.2018
-------------------------------------
Zeitplan wird aktualisiert in 1 Stunde.

If your entry in the dsmsched.log differs from this, please check the dsmerror.log for errors. If you continue to have problems with the scheduler, you are welcome to create an incident via our LRZ servicedesk.

Notification of the status of the automatic backup via e-mail

To keep track of your automatic node backups, you can activate e-mail notification for each node in DATWeb.
To do this, double-click on the node on which you want to activate e-mail notification and then click on Change Node Details in the top right-hand corner.

Now select the desired notification method under Backup emails: or Backup emails: (Aux.)::

  • Unsuccessful Backup means that you will only receive an email if the backup did not run or was completed with errors.
  • Daily means that you will receive an email every day, regardless of whether the backup was successful or not.

Configuration of multiple nodes on one system

You can enter several nodes in dsm.sys:

SErvername nodename1
Nodename nodename1
TCPServeraddress isp1.abs.lrz.de
TCPPort 1500
COMMmethod TCPip
DOMAIN /mnt/test1
passworda generate
*** Kommentar Node 2
SErvername nodename2
Nodename nodename2
TCPServeraddress isp2.abs.lrz.de
TCPPort 1500
COMMmethod TCPip
DOMAIN /mnt/test1
passworda generate

Accordingly, both server names must also be entered in dsm.opt:

SErvername nodename1
SErvername nodename2

Now you can use nodename1 with the command dsmc -servername=nodename1. For nodename2 the command is dsmc -servername=nodename2.
Of course, this also works with the ISP client GUI (command dsmj): dsmj -servername=node1 and dsmj -servername=nodename2.

Scheduler Daemon Service with multiple nodes when using systemctl:

Here is an example of how the above instructions for the scheduler must be adapted on the basis of systemctl:

  • You must create a separate configuration file with <nodename>.opt for each configured node.
  • Copy the script /opt/tivoli/tsm/client/ba/bin/dsmcad.service to /etc/systemd/system, if this has not already been done by installing the ISP client.
  • Create a copy of the script just copied for each node in /etc/systemd/system and name it according to the scheme dsmcad-<nodename>.service, e.g. dsmcad-nodename1.service and dsmcad-nodename2.service. 
  • Change the respective script of the nodes as follows:
    Replace the line ExecStart=/usr/bin/dsmcad with ExecStart=/usr/bin/dsmcad -optfile=/opt/tivoli/tsm/client/ba/bin/dsmnode.opt
    (The path to the optfile must match the respective node if you use several dsm.opt files).
  • Reload the systemctl service with systemctl daemon-reload.
  • Activate the autostart for each service, in our example systemctl enable dsmcad-nodename1.service and systemctl enable dsmcad-nodename2.service.
  • Now start the services with systemctl start dsmcad-nodename1.service and systemctl start dsmcad-nodename2.service.

Please also carry out the check here to see whether the scheduler service is working, which was shown above for a node.