See answers below:

At 04:07 PM 7/11/2003 +0100, you wrote:

*SMers,

I understand from searching back on the list that this one might be a
bit of a hot potato, but here goes anyway:

We'd ideally like to set up TSM Journaling on a Win2K MSCS Cluster using
TSM 4.2 Client with SAN attached disk.

So, my questions are:

        o) Does the TSM Journal Engine support SAN-attached disks - I
recall something about the Win32 api ReadDirectoryChangesW only
monitoring 'local' file system changes - does this preclude SAN attached
disk?

        A SAN-attached disk is considered a local file system. Yes, this
would be "journalable". (Is that even a word?)

        o) Would this work in an MSCS cluster?

        I'm going to defer to Andy Raibeck on the official answer on this
one.Does it work? The answer I got was
that this was not supported, because the TSM Journal Service cannot be
restarted on the second
half of the cluster if a failover occurs. But if you are willing to live
with this limitation, it does work. You
can have the journal service monitor the shared resources, and it will
journal them. It just won't work in
the event of a failover. The journal will not be valid, and you will have
to resort to a "normal" incremental backup.

Has anyone done this, or tried to? Any advice?

Any help greatly received, as always!

Rgds,

David McClelland
Global Management Systems
Reuters Ltd


--------------------------------------------------------------- -
        Visit our Internet site at http://www.reuters.com

Get closer to the financial markets with Reuters Messaging - for more
information and to register, visit http://www.reuters.com/messaging

Any views expressed in this message are those of  the  individual
sender,  except  where  the sender specifically states them to be
the views of Reuters Ltd.

Dave Canan
TSM Performance
IBM Advanced Technical Support
ddcanan AT us.ibm DOT com