SUCCESS... using 3.1.0.7 f2 fixtest package; the added parameters
(/clusternode:yes and /group:xxx) enable registry replication upon
fail-over, and it works... haven't tried to force fail-over during
in-progress schedule, yet.

Notwithstanding reports of difficulty using TSM 3.7; ie, (1) failure to
restart in-progress schedule if fail-over occurs, and (2) 6-minute delay in
transferring services during failover, all is okay.  I found a keystroke
error in "dsmcutil" set up of the group that was failing... the /node:
incorrectly contained the other group, which (of course) was being handled
by its own schedule, so even the error message was correct --- just didn't
include the node name value.

Thanx,
Don

Don France

Technical Architect, P.A.C.E.
San Jose, CA
mailto:dfrance AT pacbell DOT net
PACE - http://www.pacepros.com
Bus-Ph:   (408) 257-3037





> -----Original Message-----
> From: Joshua S. Bassi [mailto:jbassi AT GLORYWORKS DOT COM]
> Sent: Friday, December 31, 1999 12:03 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Backup an NT Cluster
>
>
> Don,
>
> I haven't actually set it up myself, but I remember hearing about an
> error in the documentation for backing up an NT cluster.  Take a look
> at the ADSM archive from a couple of months ago.
>
>
> --
> Joshua S. Bassi
> Senior Technical Consultant
> Symatrix Technology, Inc.
> jbassi AT gloryworks DOT com
> (503) 702-3371
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On
> Behalf Of
> France, Don (Pace)
> Sent: Friday, December 31, 1999 11:49 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Backup an NT Cluster
>
>
> HAS ANY ONE GOTTEN THIS TO WORK?!?
>
> I have, recently, been trying to do the same thing;  the
> readme files are
> (mostly) clear on creating the services with dsmcutil, etc.
> The problem is:
> it still didn't work.  I have specified the IP-name of the
> cluster for the
> /group: parm, and the /clusternode:yes parm, on the dsmcutil
> cmd for the
> cluster services created on each node;  the b/a clients work
> fine for the
> local drives on their associated nodes... it's one of the
> clusters that
> hasn't worked (one did, one didn't,,, one did work *before* I
> re-established
> the cluster node services specifying the /group: and
> /clusternode: parms;
> last night neither of them worked!)