Greg,

I'm way behind on reading this news list, but to answer your questions.
We have software distribution in place to rebuild a base NT server, installing
and configuring the clustering software is indeed done manually, followed by a
restore of the shared disks.
Yes setting unique labels would solve the problem (I don't no how things will
change when NT PTF5 UNC names will be used).

Walter Ridderhof  (Mainland Sequoia, ridderw AT xs4all DOT nl)


Greg Heis wrote:

> Mr. Ridderhof,
>
> How do you plan to handle disaster recovery for your clustered machines?  Do
> you plan to rebuild each member of the cluster manually, then restore the
> shared volume?  How would changing to label of the system drive facilitate
> the backup of the system drives?

>
>
> Thanks,
>
> Greg Heis
> Fedex
>
> -----Original Message-----
> From: Walter Ridderhof <ridderw AT XS4ALL DOT NL>
> To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
> Date: Friday, July 31, 1998 1:10 PM
> Subject: Re: ADSM v3 trying to Backup/Restore to Microsoft Cluster
>
> >Jim,
> >about the clustering bit, it works as a charm. We worked on Compaq
> >clustering hardware, 2 NT machines with both a local hard disk and shared
> >RAID box. We installed ADSM NT client on both machines (one at a time) with
> >exactly the same options file, same NODE name, same TCPCLIENTADDRESS (using
> >the shared TCP address, i.e. the one that is taken over by either machine
> >after a failover) etc. etc.. We then installed the scheduler as a service
> >(on both machines) with autostart=no.
> >On the clustering side we let the clustering software take control of
> >stopping and starting the scheduler service by adding the scheduler as a
> >resource of type generic service. The scheduler is then added to the rest
> of
> >the services that are under control of clustering startup and failover. It
> >all worked perfectly, without a hitch.
> >One detail though, we don't backup the local disks only the shared RAID box
> >drives, reason for this is that the local drives have the same label. Add
> to
> >this that NT (and  it's registry) is installed on the local drive,  doing a
> >restore of the local disk to the wrong machine will probably spell the blue
> >screen of death. A simple relabel will solve the problem, but we're not
> >interested in system backup's (we have software distribution for that) just
> >the user data.
> >One nice detail, while testing the failover during a backup, to our suprise
> >the backup was re-initiated seconds after failover on the failover machine
> >and ADSM just continued backing up the shared drives. This did not happen
> on
> >a restore but we could do a restart restore.
> >
> >Have fun,
> >
> >Walter Ridderhof  (Mainland Sequoia, ridderw AT xs4all DOT nl)
> >
> >> We have just recently installed a Microsoft Cluster, Wolfpack.  We are
> >> using ADSM v3 on MVS to do backups and restores to Microsoft Windows NT
> >> servers.  Has anybody setup ADSM to do backups in a clustered
> >> environment??  We can backup the primary partitions on each server but
> >> we have other partitions that switched back and forth from one server to
> >> the other server when the cluster software fails over.  So what I am
> >> looking for is a way to setup the client so that I can backup/restore
> >> the other partitions to the same filespace on the ADSM server.  Any
> >> ideas would be appreciated!!
> >>
> >> Jim Sellars
> >> Lane County
> >> Regional Information Systems
> >> 125 E. 8th Ave.
> >> Eugene, OR 97401
> >