Verify a Tivoli Storage Manager Backup is Using the Journal DB

Answer

When a Tivoli Storage Manager Journal service engine is first activated, the first full incremental backup of the volume (that the journal service must monitor) establishes the journal database. The following message will be displayed in the backup text to indicate that journaling of the volume has begun and that it will become valid upon successful completion of the drive backup:

ANS1761I Journal for '\\duot60ckw\z$' will be enabled upon successful completion of the backup.

With subsequent backups of this volume, the Tivoli Storage Manager client will report this message at the beginning of the backup indicating that journaling is active and in use:

Using journal for '\\machinename\volume$'

This is recorded to the screen during client command line based backups, and to the dsmsched.log during scheduled client backups. In addition, the number of objects inspected and backed up in the result statistics should be significantly less than a traditional incremental volume backup.

If the journal engine stops, experiences a problem, or a user indicates that journaling is not to be used (ie. Tivoli Storage Manager is started with the -nojournal option), then the statistics should reflect a normal incremental backup operation. Also, the above message will not appear.