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...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

|||||||||||||||||||||||||||||||||directory delimiter) or a relative path name. In the later case, the location of thejournal directory is <strong>for</strong>med by using the name of the file system being journaled<strong>and</strong> appending the relative path name.v PreserveDbOnExit - The PreserveDbOnExit setting can be used to allow journals<strong>for</strong> shared resources to remain valid when a resource moves to a different nodein the cluster.v DeferFsMonStart - The DeferFsMonStart should be set to 1 to causejournal-based backup to periodically (DeferRetryInterval) check <strong>for</strong> a file systemcoming online or going offline.v DeferRetryInterval - This controls how often the journal checks <strong>for</strong> a change infile system status.v logFsErrors - This is used to eliminate excessive ″File System unavailable″messages from being written to the log.The previously listed options can be set <strong>for</strong> all file systems being journaled. Then,if desired, you can override any given file system with a file system overridestanza.When the journal daemon is set up to monitor file systems as they go online <strong>and</strong>offline, this is done in a periodic loop. The following actions occur during resourcefailover <strong>and</strong> fallback conditions:v nodeA <strong>and</strong> nodeB share a resource <strong>and</strong> nodeA has a failure <strong>and</strong>, there<strong>for</strong>e, afailover occursv nodeB will detect the shared resource <strong>and</strong> start monitoringv When nodeA takes the resource back (fallback), if nodeB has an open filedescriptor to the shared journal database, it will receive a SIGKILL interrupt.This interrupt cannot be caught or ignored.v nodeB must be in<strong>for</strong>med of the resource fallback be<strong>for</strong>e the event, by removingthe shared file system names from the journal list of file systems to monitorcontained in the options file - tsmjbbd.ini. This can be done manually or it canbe automated by using HACMP start <strong>and</strong> stop scripts.Two sample perl scripts are provided with the journal: jbbadd.pl <strong>and</strong>jbbdelete.pl. The invocation of these scripts can be added toStartClusterTsmClient.sh <strong>and</strong> StopTsmClient.sh. The arguments <strong>for</strong> these scriptsare just the file system names of the shared resources.516 <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!