ADSM-L

Re: journaling on a cluster

2002-10-31 13:58:34
Subject: Re: journaling on a cluster
From: Pete Tanenhaus <tanenhau AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 31 Oct 2002 13:55:05 -0500
I'm a bit disappointed word hasn't gotten out, but support for clustering
 was implemented in client release 5.1.0.

Several new configurations settings were added to allow resources to be
journaled on multiple nodes within a cluster.

The new settings are DeferFsMonStart, DeferRetyInterval, and logFsErrors.

The JouralDir also now (as of 5.1) may be specified for individual
journaled file systems.

The DeferFsMonStart setting allows the journal service to bring journaled
resources
online or offline dynamically when the availability of the resource
changes.

If this setting is on and a resource being journaled becomes unavailable
(as in the case of a
cluster failover or moving the resource to another node in the cluster) the
resource will be
taken offline and placed in defer mode.

If the resource becomes available it will be brought online and journaling
of it will continue
(and if the PreserveDbOnExit setting is on it will remain valid and a
Journal Based Backup
can continue with first doing a full incremental).

Journaled resources with the DeferFsMonStart specified are checked at the
interval specified
by the DeferRetryInterval setting (the value of this setting is in
seconds).

The logFsErrors setting suppresses errors generated due to  resources being
unavailable
from being logged to both the TSM error log and the NT application
eventlog.

In a cluster environment, one journal service should be running on each
node in the cluster,
and shared resources to be journaled should be configured the same on both
services
(with the defer settings).

Also the journal of the shared resources must reside in a location which is
accessible by all
nodes in the cluster, which is why the JournalDir setting now may be
specify a different location
for each resource via an override stanza.

If the global JouralDir setting under the JournaledSettings stanza
specifies a drive letter (i.e c:\tsmjournal)
all journals will reside in the drive letter\directory specified by the
setting.

If the global setting does not contain a drive letter (i.e \tsmjournal) the
journal for each
journaled resource will be located in the specified directory on each
journaled resource.

Below are sample configuration stanza's  for a cluster environment:


[JournalSettings]
; directory where journals for local resources are located
JournalDir=c:\tsmJournal.local

;  Override settings for shared journaled filesystem D:
;
;  This setting overrides settings in JournaledFileSystemSettings stanza
;
[JournaledFileSystemSettings.D:\]
; directory where journals for shared resources are stored
JournalDir=d:\tsmjournal.shared
; Keep journal valid if goes offline
PreserveDBOnExit=1
; Allow resource to go offline and come back online
DeferFsMonStart=1
; Check resource availability every 30 seconds
DeferRetryInterval=30
; Don't log errors generated while check resource availability
logFsErrors=0


Hope this helps and please post again if there are additional questions
....



Pete Tanenhaus
Tivoli Storage Solutions Software Development
email: tanenhau AT us.ibm DOT com
tieline: 320.8778, external: 607.754.4213

"Those who refuse to challenge authority are condemned to conform to it"

---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on
10/31/2002 01:12 PM ---------------------------

Etienne Brodeur <ebrodeur AT SERTI DOT COM>@VM.MARIST.EDU> on 10/31/2002 
11:02:46
AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:    "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:    ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:    Re: journaling on a cluster



If I remember corectly journaling is not supported on W2K Cluster
server... or was not until recently (I found this on the list when I was
looking for the same info):

You should be aware that the TSM Journaling Engine service is not
supported in MS Cluster server. Only one TSm Journaling Engine Service may
be installed on a machine and the TSM Journaling Engine Service can not
dynamically start/stop monitoring shared disk.

Etienne







chris rees <rees_chris AT HOTMAIL DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/31/2002 08:23 AM
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        journaling on a cluster


Hi all

Can anyone point me in the right direction for documentation on
implementing
journaling on an active/active file and print win2k cluster.  Is this even
supported??

Regards

Chris



Have a look at http://www.geocities.com/rees_chris




_________________________________________________________________
Surf the Web without missing calls! Get MSN Broadband.
 http://resourcecenter.msn.com/access/plans/freeactivation.asp

<Prev in Thread] Current Thread [Next in Thread>