Backing up and restoring the database

To minimize downtime during disaster recovery, back up your master data files frequently to either offline storage or a backup master domain manager.

Using a backup master domain manager with a backup database

Set up a backup master domain manager that accesses a different database than the master domain manager, and get your database administrator to set up a mirror of the master domain manager's database onto the backup master domain manager's database. In this way your backup master domain manager not only receives copies of all the processing messages, as is provided for by the setting of the FullStatus attribute on the backup master domain manager, but is also able to access the mirrored database. The mirror frequency must be set high enough to match the frequency with which you change the database.

For more information about how to use a backup master domain manager, see Switching the master to a backup.

Backing up the configuration files

The configuration files used by IBM Workload Scheduler are found in the following places:
useropts
<user_home_dir>/TWS
For the localopts, Sfinal, Security and *.msg files
On Windows operating systems
<TWA_home>
On UNIX operating systems
<TWA_DATA_DIR>
IBM Workload Scheduler configuration files
On Windows operating systems
<TWA_home>\TWS\mozart\*.*
On UNIX operating systems
<TWA_DATA_DIR>/TWS/mozart/*.*
This directory might contain the following files:
runmsgno
This is used for the allocation of unique prompt numbers. On the master domain manager, this file should not be edited manually. On other workstations it can be edited only in the circumstances described in the Troubleshooting Guide. This file does not need to be backed up.
globalopts
This is used to store a copy of three of the global properties stored in the database. It must be edited only in the circumstances described in Switching the master to a backup. This file should be backed up if it is edited.
Application server configuration files, such as TWSConfig.properties
On Windows operating systems
<TWA_home>\usr\servers\engineServer\resources\properties
On UNIX operating systems
<TWA_DATA_DIR>/usr/servers/engineServer/resources/properties
Forecast plan files
On Windows operating systems
<TWA_home>\TWS\schedForecast
On UNIX operating systems
<TWA_DATA_DIR>/TWS/schedForecast
Archived plan files.
On Windows operating systems
<TWA_home>\TWS\schedlog
On UNIX operating systems
<TWA_DATA_DIR>/TWS/schedlog
Trial plan files
On Windows operating systems
TWA_home\TWS\schedTrial
On UNIX operating systems
<TWA_DATA_DIR>/TWS/schedTrial
A detailed list of all files is not supplied, as there are too many files. Back up all the files in these directories.
Note: The wa_pull_info tool is provided for sending information to support, but can also be used to perform a backup of a DB2® database and some of the configuration files. For more information, see Data capture utility.

Backing up log files

Make a regular offline backup of all log files, identifying them from the information given in Logging and tracing.

If you use wa_pull_info for backup, you do not need to separately backup these files. For more information, see Data capture utility.