12.07.2015 Views

IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Syntax <strong>for</strong> stanza settings:JournalSettings=value|||||||||||||||||||||You can specify the following JournalSettings values:ErrorLogSpecifies the log file where detailed error messages generated by thejournal daemon are written. The default value is jbberror.log in thedirectory of the daemon executable. For example:ErrorLog=/logs/jbberror.logJournalDirDirectory where journal database files are stored <strong>and</strong> written.If the path given is an absolute (<strong>for</strong> example, it begins with a dirdelimiter) pathname, this is the directory used. If the path given is a relativedirectory name, then this path is appended to each file system name <strong>and</strong>the resulting path name is used.The default is a directory named .tSm_JoUrNaL (used within each filesystem being journaled).The advantage of having the journal database on the file system beingmonitored is that the database stays with the file system. The disadvantageis that the updates to the database must be processed <strong>and</strong> discarded. Thatis, directing the database to a non-journaled file system is more efficient<strong>and</strong> is strongly recommended, unless this file system is shared in a clusterenvironment.This setting applies to all journaled file systems but may be overridden viaan override stanza <strong>for</strong> each journal file system.JournalExcludeListstanzaThis list of exclude statements filters changes from being recorded in the journaldatabase. Changes to objects which match statements in this stanza are ignored<strong>and</strong> are not recorded in the journal database.Note: Excluding files from the journal has no bearing on those files being excludedby the backup client, other than preventing the file names from being sent tothe backup client to be processed during journal-based backup. A file that isnot excluded from the journal should still be excluded by thebackup-archive client, if there is a matching exclude statement in the clientoptions file.There is no correlation between the journal exclude list <strong>and</strong> the backup-archiveclient exclude list.Note: The journal daemon only provides a subset of the INCLUDE/EXCLUDEfunction provided by the backup-archive client. The journal daemon doesnot support INCLUDE statements <strong>and</strong> it does not support the exclude.diroption.The following pattern matching meta characters are supported:% Matches exactly one character.* Matches zero or more characters.518 <strong>IBM</strong> <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> <strong>for</strong> <strong>UNIX</strong> <strong>and</strong> <strong>Linux</strong>: <strong>Backup</strong>-<strong>Archive</strong> Clients Installation <strong>and</strong> User’s Guide

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!