>>> My only concern about this is what happens if a failover occurs and a
file
>>> is modified within the DeferRetryInterval. I guess if it is not
>>> subsequently modified, it never gets backed up?

Basically it depends on whether or not the PreserveDbOnExit setting
is on or not.

This setting allows a journal to remain valid when the drive being
journaled goes offline and comes back online in the journal service.

If the setting is off (the default) the journal will be deleted when
the drive goes offline and a full non-journal backup of the drive
must be done when the journal comes back online in order for backups
to use the journal.

If the setting is on than any changes the journal will remain valid
when the journal goes offline and backups will continue to use the
journal when the drive comes back online, but any changes which
occur while the drive is offline won't be reflected in the journal.

So it is trade-off between foregoing the pain of having to do a full
non-journal incremental
and risking missing file system changes while the drive is offline.

Hope this answers your question ....


Pete Tanenhaus
Tivoli Storage Manager Client 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
12/14/2005 05:15 PM ---------------------------
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: journal service in a MS clustered environment


Rainer

We have done journal-based backups on MSCS. There is no need for multiple
journal services - one per cluster node is sufficient. The idea is to have
each one configured to journal any file system on which you desire JBB,
but
suppress the errors if the resource is not actually on line on that node.

The sample tsmjbbd.ini describes how the parameters DeferFSMonStart,
DeferRetryInterval and LogFsErrors can be configured to support this.

This extract from our tsmjbbd.ini shows support for journaling on two
shared files systems - G: and H:.

[JournaledFileSystemSettings]
JournaledFileSystems=G: H:
...

[JournaledFileSystemSettings.G:\]
DeferFsMonStart=1
DeferRetryInterval=30
logFsErrors=0

[JournaledFileSystemSettings.H:\]
DeferFsMonStart=1
DeferRetryInterval=30
logFsErrors=0

My only concern about this is what happens if a failover occurs and a file
is modified within the DeferRetryInterval. I guess if it is not
subsequently modified, it never gets backed up?

Regards
Neil Schofield
Yorkshire Water Services Ltd.



Let us know when you're moving house on-line at www.yorkshirewater.com

YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD

The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Yorkshire Water Services Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682