>Hi, with the good guidance of the SSSI people on this list (Kelly Lipp and
>John Sorenson) we've just had some good results by declaring the ADSM
>scheduler service as a generic service to MSCS and getting MSCS to restart
>it on failover so it sees the newly arrived drives. If we do this in the
>middle of a backup hey presto the backup restarts. This is using the same
>nodename on both boxes. Thanks SSSI!!
>
>Still need to look into the registry backup issues and how to deal with the
>ADSM password changing and letting the other box know about it.
>
>Most concrete indication I've had from IBM yet is 2nd quarter 1999 for the
>baclient being cluster aware (wish they'd do it for the UNIX clients too).
>Maybe then we can use the webclient on clusters and all that later PTF
level
>stuff which we're having to miss out on.
>
>Quick public gripe - this doesn't look too much like being 'in lockstep
with
>MS' developments.
>
>Alan
>
>-----Original Message-----
>From: Nichols, Linnea <linnea.nichols AT CO.FAIRFAX.VA DOT US>
>To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
>Date: Wednesday, January 06, 1999 17:32
>Subject: FW: Microsoft Cluster Server
>
>
>>Mea Culpa!!! I was so excited about getting an answer that I didn't
>>read down through all the rest of my mail to find it --- but there it
>>was -- we are going to give this a try -- getting ADSM (or almost
>>any backup system) to work with an NT Cluster has been a real
>>challenge for us.
>>
>>Linnea Nichols
>>
>>Fairfax Co. Govt, Fairfax, VA    Linnea.Nichols AT co.fairfax.va DOT us
>>Phone:703/324-2708                FAX: 703/324-3931
>>
>>-----Original Message-----
>>From: Nichols, Linnea [mailto:linnea.nichols AT CO.FAIRFAX.VA DOT US]
>>Sent: Wednesday, January 06, 1999 12:08 PM
>>To: ADSM-L AT VM.MARIST DOT EDU
>>Subject: Re: Microsoft Cluster Server
>>
>>
>>What's the fix? And where can I find the note?
>>
>>Linnea Nichols
>>
>>Fairfax Co. Govt, Fairfax, VA    Linnea.Nichols AT co.fairfax.va DOT us
>>Phone:703/324-2708                FAX: 703/324-3931
>>
>>-----Original Message-----
>>From: Kelly J. Lipp [mailto:lipp AT STORSOL DOT COM]
>>Sent: Tuesday, January 05, 1999 11:59 AM
>>To: ADSM-L AT VM.MARIST DOT EDU
>>Subject: Re: Microsoft Cluster Server
>>
>>
>>A note from late yesterday addresses this very issue with a fix.
>>
>>Kelly Lipp
>>Storage Solutions Specialists, Inc.
>>lipp AT storsol DOT com
>>www.storsol.com
>>(719) 531-5926
>>
>>-----Original Message-----
>>From:   Nathan King [SMTP:nathan.king AT USAA DOT COM]
>>Sent:   Tuesday, January 05, 1999 9:27 AM
>>To:     ADSM-L AT VM.MARIST DOT EDU
>>Subject:        Microsoft Cluster Server
>>
>>Is anyone aware of any backup products which interface with ADSM which are
>>MS Cluster Server aware.
>>
>>We currently have installed the ADSM Backup Archive Client on two NT
>Servers
>>clustered together.
>>
>>Both these servers share one MSA made up of 3 logical drives. When a
>>failover occurs the drives failover to the other server.
>>
>>However the ADSM Scheduler is unaware of the failover and fails to backup
>>the failed over drives and we miss a backup.
>>
>>This is only the tip of the iceberg.
>>
>>Failovers may occur regularly - this means that we are effectively
>>duplicating all our data since both nodes have backed up all filespaces at
>>one time or other when the particular drive was available to the node.
Each
>>of these logical drives is over 100Gb in size! It's a lot of data to
backup
>>each time a failover occurs.
>>
>>Restores are also very cumbersome since it is difficult to ascertain where
>>to restore a document from - Node A or Node B??? The only current
foolproof
>>method is to run a picklist for both, but this is hardly ideal.
>>
>>
>>
>>
>>Nathan King
>>Storage & Automation Management
>>*  (210) 913-5755
>>* Pager: 753-5755
>>* E-mail: nathan.king AT usaa DOT com
>>
>>The opinions herein are solely author's  and are not necessarily the
>opinion
>>of USAA.
>