Journal daemon configuration

Journal-Based Backup is enabled by installing and configuring the IBM Spectrum Protect™ journal daemon.

Configure the journal daemon by editing the journal daemon configuration sample file, tsmjbbd.ini.smp, and saving it as tsmjbbd.ini. Both files should be in the default installation directory.

After you configured the tsmjbbd.ini file, start the journal daemon by starting the tsmjbbd executable file.

AIX operating systems On AIX®, run the jbbinittab script file to add an entry to the /etc/inittab file, to start the journal daemon after you restart your system. The tsmjbbd executable file and the jbbinittab script file should be in the default installation directory.

On Linux, the installer creates the tsmjbbd service in /etc/init.d. To control the service, run the following command as root to stop, start, or restart the service, or to check its status:


>>-service tsmjbbd--+-start---+--------------------------------><
                    +-stop----+   
                    +-restart-+   
                    '-status--'

If the Linux operating system runs the systemd initialization service, complete the following steps to start the journal daemon:

Copy the provided systemd unit file /opt/tivoli/tsm/client/ba/bin/tsmjbbd.service to the /etc/systemd/system/ directory.
Run the following command to refresh the systemd unit list:
```
systemctl daemon-reload
```
Run the following command to start the journal daemon at system boot time:
```
systemctl enable tsmjbbd.service
```
Run the following command to start the journal daemon:
```
systemctl start tsmjbbd.service
```

Note:

Network and removable file systems are not supported.
Periodic full incremental backups should be performed to complement daily journal-based backups. Full progressive incremental backups can take longer to run than a journal-based backup. Take this information into account when you schedule them, perhaps scheduling the incremental backups during off-peak times. Balance these two backup techniques according to your business needs. For example, you might decide to schedule nightly journal-based backups and also schedule a weekly full progressive incremental backup.
Journal-based backup uses the filepath kernel extension to monitor file system changes. To improve the performance of journal-based backups, directories that do not contain user files are not monitored for changes and are not included in journal-based backups. The following lists the directories that are not included in journal-based backups on AIX and Linux systems. Changes to these directories are processed if you perform periodic full incremental backups by using the incremental command with the -nojournal option.
AIX Linux
/bin /dev /etc /lib /usr/bin /usr/lib /usr/share
/bin /boot /dev /etc /lib /proc /sbin /sys /usr/bin /usr/lib /usr/share /var

AIX	Linux
`/bin /dev /etc /lib /usr/bin /usr/lib /usr/share`	`/bin /boot /dev /etc /lib /proc /sbin /sys /usr/bin /usr/lib /usr/share /var`

The journal daemon configuration file is periodically checked for updates to the list of journaled file systems. You can add or remove file systems from the list of monitored file systems without stopping the journal daemon.

Attention: If you bring a file system that is being monitored by the journal daemon offline, the journal database for that file system is deleted. To preserve the database, set PreserveDbOnExit=1 in the journaled file systems settings stanza. This setting preserves the journal database when it is taken offline and ensures that the journal database is valid when the file system comes back online. For more information, see JournaledFileSystemSettings stanza.

The syntax for stanza and stanza settings is as follows:

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.
These journaled file system settings do not correlate to any settings in the client options file. The journal daemon is an independent process; it does not process any options in the client options file.