Automatic backups using ISP Client Acceptor (CAD) or via Crontab/schedule

In the case of an automatic backup, there is the option of letting the IBM SP (IBM Spectrum Protect) server control the automation (CAD). For Linux - for Windows.

The second option is to control this yourself as a user via crontab (Linux) or a schedule (Windows).


Configuration of the automatic backup (CAD) for Unix- and Windows systems

UNIX

The IBM SP client is configured so that the scheduler process performing the backup is managed with the IBM SP client acceptor (CAD).
The CAD provides a simple timer that automatically starts and stops the scheduler process as required.
It is therefore no longer necessary to use exclude/include after changes to the option files "dsm.opt", "dsm.sys" and the file referenced via the option "inclexcl"
option with exclude/include statements, it is no longer necessary to restart the IBM SP scheduler.

If you follow the suggestions of the SCC, you will see the following after starting the CAD in the directory
/usr/local/tsm/log
you will find the following LOG files:

  • dsmerror.log: Error messages from the IBM SP Scheduler
  • dsminstr.log: Instrumentation log file
  • dsmsched.log: IBM SP Scheduler messages
  • dsmwebcl.log: Messages from the IBM SP Client Acceptor (CAD)

However, the CAD may only be started after the IBM SP password has been set.
Setting the IBM SP password (saving the IBM SP password in a file in the /etc/adsm directory)
is usually done by starting a backup for the first time.

In principle, the IBM SP client acceptor process can be started in two ways:
init or systemd
Check which start type applies to your computer.
You can use the ps -p 1 command to do this.

init start
To automatically start the CAD on your machine, save the file dsmcad to the file
/etc/init.d/dsmcad.

Set the rights for this file as follows:
chmod 500 /etc/init.d/dsmcad
chown root.root /etc/init.d/dsmcad

In this file, please adjust the value of the environment variables LANG, LC_CTYPE
and the path for -errorlogname and -instrlogname to suit your requirements.
Activation of the service for automatic start during the boot process:

/usr/sbin/update-rc.d dsmcad defaults

The CAD can then be started manually with the following command:

/etc/init.d/dsmcad start


systemd start
To start the CAD automatically on your machine, save the file dsmcad.service to the file

/etc/systemd/system/dsmcad.service.

In this file, please adjust the value of the environment variables LANG, LC_CTYPE
and the path for -errorlogname and -instrlogname to suit your requirements.
Activation of the service for automatic start during the boot process:

/usr/bin/systemctl enable dsmcad.service

The CAD can then be started manually with the following command:

/usr/bin/systemctl start dsmcad.service

WINDOWS

Installing the "IBM SP Scheduler" and "IBM SP Client Acceptor" services
You must install two services on your computer for the automatic backup:

  • IBM SP Scheduler
  • IBM SP Client Acceptor

The services may only be installed after the IBM SP Client has been started for the first time and the IBM SP password provided has been successfully entered. (see section "Making contact")
The IBM SP Scheduler is managed by the IBM SP Client Acceptor (CAD). The CAD serves as an external timer for the Scheduler. When the scheduler is started, it asks the IBM SP server for the next scheduled event. The event is either executed immediately or the scheduler is terminated. The CAD starts the scheduler again when the time has come for the scheduled event to be executed. This reduces the number of background processes on your workstation and avoids memory retention issues that can occur when the scheduler is running without CAD management. The services can be installed as follows:

1. option) Execute a batch file
Save the file tsm_services_install on your computer: e.g. in the directory c:\temp\tsm_services_install.bat
Execute this file. Please note the messages displayed.

2nd option) Enter the necessary commands in a "Command prompt window"
Open a "Command prompt window".
Then change to the directory "c:\Program Files\Tivoli\TSM\baclient", e.g:

cd /d %ProgramFiles%\Tivoli\TSM\baclient

In this directory you will find the utility program dsmcutil and the corresponding help file "dsmcutil.chm".

Step 2a) Installation of the IBM SP Scheduler
dsmcutil install /name:TSM-Backup-Scheduler /node:<tsm-nodename> /autostart:NO /startnow:NO /password:tsm-password

Step 2b) Installation of the IBM SP Client Acceptor (CAD)
dsmcutil install CAD /name:TSM-Client-Acceptor /node:<tsm_nodename> /cadschedname:TSM-Backup-Scheduler /autostart:YES /startnow:YES /password:tsm-password

You will find the following important LOG files in the %ProgramFiles%\Tivoli\TSM\baclient directory:

  • dsmerror.log: Error messages
  • dsminstr.log: Instrumentation log file
  • dsmsched.log: IBM SP Scheduler messages
  • dsmwebcl.log: Messages of the IBM SP Client Acceptor (CAD)


Configuration of the automatic backup via schedules for Unix and Windows systems

UNIX - Backup via a crontab entry

Save the batch file in a suitable directory as a shell script (e.g. dsmc_incr).
In the crontab entry to be defined by you, refer to the shell script sent along.

Example entry:
30 12 * * * /<your_path>/dsmc_incr >/dev/null 2>/dev/null
The files generated by the dsmc call

  • dsmerror.log: Error messages from the backup
  • dsminstr.log: Instrumentation log file
  • dsminstr.log.lock
  • dsmcincr.log: Log file of the backup

are stored in the /var/tmp directory.

You can adapt this location to your requirements at any time in the shell script provided.
The variable path_tsm_log_files is used for this purpose.

WINDOWS - Backup with a schedule

Save the batch file in a suitable directory as a .bat file (e.g. dsmc_incr.bat).
This batch file is then referenced in the task schedule you define.

The files generated by the dsmc call

  • dsmerror.log: Error messages from the backup
  • dsminstr.log: Instrumentation log file
  • dsminstr.log.lock
  • dsmcincr.log: Log file of the backup

are stored in the directory c:\\Users\\AppData\Local\Temp.
You can adapt this location to your requirements at any time in the script provided.
The variable path_tsm_log_files is used for this purpose.