[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::winnt-clusters

Title:WinNT-Clusters
Notice:Info directories moved to DECWET::SHARE1$:[NT_CLSTR]
Moderator:DECWET::CAPPELLOF
Created:Thu Oct 19 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:863
Total number of notes:3478

280.0. "Failover for Macintosh clients, Macintosh volumes?" by CSCMA::HODGE () Fri Aug 02 1996 15:22

T.RTitleUserPersonal
Name
DateLines
280.1MSE1::PCOTEDigital on a shoestringFri Aug 02 1996 17:076
280.2Mac volume failover okay?LURE::lurent.mpo.dec.com::CerlingGrace HappensMon Aug 05 1996 12:208
280.3Some bizzare behavior with Macintosh shared volumesMQOOA::ras022p13.mqo.dec.com::courchesneBon renom et loyaut�Wed Mar 19 1997 11:4427
I'm, right now, configuring an NT cluster with an attached MAC on it.

The cluster is running V1.0 with no service pack on it.

Both servers are running NT3.51 and are configured in the network 
environment to support Macintosh volume.  I'm experiencing some real bizzare 
behavior.

1- The caching on the client is not consistent with the volume failing from 
one server to the other.

2- When, from the client, I create extra entry in the volume, I see it on the 
server directory structure, when the cluster moves from one server to the 
other, I don't see the directory structure that was created.

3- On the NT servers, in the disk administrator, I get fantom drives added 
each time the cluster fails over.  The list of drives went fror the original 
3 drives to 5 drives after a couple of failovers.  It is allways the MAC host 
drive that offers the MAC volume that creates the fantom drive.


I'm really not sure if I can demo the capacity of putting a volume back on 
line (with a manual reconnect from the MAC client) to my customer.  The $$$ 
is potential and I'd appreciate all the help available.

Andre J. Courchesne
DIGITAL Montr�al