IBM Tivoli Storage Manager, Version 7.1

Configuring the journal engine service

Journal-based backup can be used for all Windows clients. If you install the journal engine service and it is running, then by default the incremental command automatically performs a journal-based backup on selected file systems that are being monitored by the journal engine service.

Journal-based backup is enabled by installing and configuring the Tivoli® Storage Manager journal service. The Tivoli Storage Manager journal service can be installed with the GUI Setup wizard or with the dsmcutil command. Basic journal service configuration can be done with the GUI Setup wizard, more advanced configuration can be done by editing the journal service configuration file, tsmjbbd.ini.

Tip: The default location for journal service configuration file is C:\Program Files\Tivoli\TSM\baclient\tsmjbbd.ini. If this is the first time you are configuring the journal engine service and a copy of tsmjbbd.ini does not already exist, copy the sample file C:\Program Files\Tivoli\TSM\config\tsmjbbd.ini.smp to C:\Program Files\Tivoli\TSM\baclient\tsmjbbd.ini.

To install and configure this service using the client Java™ GUI setup wizard, perform the following steps:

From the main window, open the Utilities menu and select Setup Wizard.
Select the Help me configure the TSM Journal Engine check box.
Select the task you want to perform. You can install a new journal engine, update a previously installed journal engine, or remove a previously installed journal engine from your system.
Complete each panel in the wizard and click the Next button to continue. To return to a previous panel, click the Back button. To display help information for a panel, click the Help button.

Journal service configuration settings are stored in the journal configuration file tsmjbbd.ini. This file can be installed and configured with the GUI setup wizard or be manually edited.

Follow these steps to set up multiple journal services:

Create and set up a separate journal configuration file (tsmjbbd.ini) for each journal service to be installed. Each configuration file must specify a different JournalPipe value, and must also specify different drives to journal, so that the two services do not interfere with each other. Multiple journal services journaling the same drive causes problems. The different services attempts to write to the same journal database unless this is specifically overridden by specifying different journal directories in the different configuration files.
Install the multiple journal services using the dsmcutil.exe tool. Use distinct names for each service, and specify the /JBBCONFIGFILE option to identify the tsmjbbd.ini to be used for that particular journal instance. For example:
```
dsmcutil install journal /name:"TSM Journal Service 1" /JBBCONFIGFILE:c:\journalconfig\tsmjbbd1.ini  
```
```
dsmcutil install journal /name:"TSM Journal Service 2" /JBBCONFIGFILE:d:\journalconfig\tsmjbbd2.ini
```
Note: In Uniform Naming Convention (UNC) format, the jbbconfigfile path must contain a drive letter. In the following UNC format example, the path contains the drive letter D$: \\computer7\D$\journalconfig\tsmjbbd1.ini
Different backup clients (based on the distinct dsm.opt file used) can now connect to the desired journal service by specifying the appropriate JournalPipe option in the appropriate dsm.opt, which corresponds to the JournalPipe journal service setting.

Note:

Each journal service instance is associated to only one Tivoli Storage Manager client node name. Changing the association requires a restart of the journal service to recognize the new association.
You cannot use network and removable file systems.

Configuration settings that you apply when the journal service is started and any changes you make while the journal service is running are applied without having to restart the service. This also applies to the journal exclude list. However, some settings for journaled file systems do not take effect until the file system is brought offline and then back online.

File systems can be taken online (added) or offline (removed) without stopping and restarting the journal service. You can bring a file system offline by removing it from the list of journaled file systems in the journal configuration file tsmjbbd.ini, or by shutting down the journal service. You can bring a file system back online by adding it to the list of journaled file systems in the journal configuration file tsmjbbd.ini or by starting (restarting) the journal service.

Attention: If you take a file system offline without setting the PreserveDbOnExit value of 1, the journaled file system journal database is deleted. PreserveDbOnExit=1 specifies that the journaled file system journal database is not deleted when the journal file system goes offline. The database is also valid when the journal file system comes back online.

The following is the syntax for stanza and stanza settings:

Syntax for stanzas:: [StanzaName]
Syntax for stanza settings:: stanzaSetting=value

Note:

You can specify comments in the file by beginning the line with a semicolon.
Stanza and value names are not case sensitive.
Numeric values can be specified in hexadecimal by preceding the value with 0x otherwise they are interpreted as decimal.
There is no correlation between these settings and any settings in the backup-archive client options file. The journal service is a completely independent process and does not process backup-archive client options.

Feedback