P
Phil
I have 2 servers with wwindows 2000 clustering and a
shared disk array. In most cases (see other question
on "inconsistent clustering") the active node of the
cluster sees the drives on the shared disks and the
passive node does not. We have set up share names (on
each server) for the drives on the shared disk array so
that we can always access files on the drives by
referencing the \\<cluste_name>\<share_name>. This works
fine when we have testit out and even when the cluster
fails over.
However, a couple of times now we have found that the
share name for the drives has disapeared and so the files
on the drive can not be accessed as above.
My suspicion is that this is as a result of a failover
having taken place, but this seems OK when I test it out.
Should I expect the share name to still exist after a
cluster failover ?
shared disk array. In most cases (see other question
on "inconsistent clustering") the active node of the
cluster sees the drives on the shared disks and the
passive node does not. We have set up share names (on
each server) for the drives on the shared disk array so
that we can always access files on the drives by
referencing the \\<cluste_name>\<share_name>. This works
fine when we have testit out and even when the cluster
fails over.
However, a couple of times now we have found that the
share name for the drives has disapeared and so the files
on the drive can not be accessed as above.
My suspicion is that this is as a result of a failover
having taken place, but this seems OK when I test it out.
Should I expect the share name to still exist after a
cluster failover ?