Determining if a backup will be journal-based

Before implementing a backup, you need to determine if it is going to be journal-based.

1. Configure the journal daemon to journal the file system that is being backed up. The journal daemon journalizes a file system after you list the file system in the tsmjbbd.ini configuration file.
   See the following configuration information:

   [JournaledFileSystemSettings]
   ;
   ; List of journalized file systems
   JournaledFileSystems=c:

2. Perform a full incremental backup on the corresponding file system while the file system is actively being journalized. This full incremental backup must set the Last Backup Completed date on the IBM Storage Protect server file space in order for the journal to be set to valid. You can view the Last Backup Completed date by issuing the QUERY FILESPACE server command. After the journal is set to the valid state, subsequent backups by the same node to the same server will be journal-based. If a backup uses a different node or a different server, the backup will be non-journal-based but the journal will remain valid for the original node and server, and backups to the original node and server will be journal-based.
   The following message is an example of what is written to the Windows Application Event Log when a journal is initially set to valid:

   Journal set to valid for fs 'H:' and will be used for backup by 
   node GSHLAGER3 to server GSHLAGER2_SERVER1.

3. Ensure that the IBM Storage Protect node and server that the backup is using matches the node and server for which the journal is valid.
4. Use the Journal Database Viewing utility to determine the current state of a journal. If a valid journal is restarted, backups will be non-journal based until the journal is re-validated.
   The following message is written to the Windows Application Eventlog when a journal is restarted:

   Journal database 'c:\tsmjournal\tsmH__.jdb' for fs 'H:' has been 
   deleted and reset to the invalid state.