Configuration and automatic backup in Linux

• Client-specific configurationClient-specific configuration
• Setting up an automatic backupSetting up an automatic backup
• Verifying the configurationVerifying the configuration

    Client-specific configuration

Please perform the following steps as root. 

The configuration files must exist or be recreated in the directory "/opt/tivoli/tsm/client/ba/bin/". 

Editing configuration files are easily done with an editor such as "vi"

In the file "dsm.opt", normally only one type of label is set, this is also true for the file dsm.sys. 

For example, in dsm.opt the content of the file can be copied.

For example, connection data is now entered into the dsm.sys file. In the following example of a "dsm.sys" file, you can make a few adjustments. The corresponding steps for the adjustment are described below.

• Entries marked with "*)" must be replaced with the ones you have been given by the ZIH.
• You should adjust information according to information "DOMAIN" on your system. There, the file systems (not directories) must be entered, from which data is to be saved.
• Adapt the information under “exclude and include” into your system. The system filters with these instructions what to back up from the file systems what to ignore during backup. Please remember that the file is read from bottom to top.

The keywords occurring in the dsm.sys as well as syntactical peculiarities are described in more detail at Configuration details.

If both configuration files (dsm.opt and dsm.sys) are created and customized, you can establish contact with the backup server. This is done with the command "dsmc" in the command line. The request for the "USERID" refers to the "node name". Simply confirm. After that, the password is required, which you received from the ZIH. After entering the password, you will receive a prompt from the backup client software "tsm>"

Now you can perform a manual backup. Below is a single file backup as an example.

If storing the password in an encrypted form worked locally on your computer, you can reach the TSM prompt in the next call to dsmc without retyping the password.

If this works, the automatic backup can be configured/setup.

In order to avoid too much data being backed-up, for example due to syntax errors in the configuration files, one can determine in advance which data will flow into the backup. For detailed information, please visit the FAQ'S, in this link.

    Setting up automatic backup

A prerequisite for setting up the automatic backup: the dsmc command must be able to start without a password. The timing of your backup to the server is set to your preference in the application. As described below, you can check when an automatic backup is scheduled for your clients. In the following example, the backup to the server is set for daily at 2pm (TGL_1400). If this time is inappropriate, please contact  the .

In order for scheduled backup to take place, the scheduler (Process or Daemon) must be running on the computer. The launch from the command line (e.g. for tests) can be carried out as follows:

After restarting the computer, the daemon does not start automatically. You must provide the Linux-specific command as shown above that tells the the corresponding daemon to run continuously. The establishment of the automatic backups for Suse Linux is described here.
Ubuntu users, use this link.
The following query shows this process.

It should always show an active process as shown below.

    Verifying the configuration

Especially after the first backup, you should check that there were no errors. As an administrator of a backup client, you will receive a daily status email from backup-service client. The status is noted in the subject of mail. Anything other than "Completed" requires a more detailed inspection. 

Unfortunately, there are some errors (bugs) that the software does not recognize, and you will still receive a “Completed” status. 

Therefore, you should always check both log files dsmsched.log and dsmerror.log (usually in "/opt/tivoli/tsm/client/ba/bin/"). Please respond appropriately when errors occur. When in doubt, open a Ticket

Advice on known errors / bugs

• Often we see the mistake that a folder or filename has an umlaut or special character in the name that cannot be read. Then, the backup of this particular folder/file does not occur. Nevertheless, you receive a status that is "Completed", (backed up successfully). You can find this type of error in the dsmerror.log file. More detailed guidance for the analysis and solution of the problem can be found here.
• Even if the backup software does not support a file system type, a "Completed" status could be reported. Unfortunately, in this case you cannot catch this error in the dsmerror.log. Check the dsmsched.log – compare the amount of data has been scanned and saved with the actual values. You can also try to restore or display the files that were backed up in a given period. For more detailed information, see "additional documentation -> IBM documentation -> Installation instructions. ( weitere Dokumentation -> IBM-Dokumentation -> Installationsanleitung)

Advice on the graphical interface: This configuration us partially possible with the graphical user interface. Since this hardly applies to our description, it has been omitted. Using the command “dsmj” will access the graphical user interface. "Java JRE 5" or a newer version must be installed on your computer.