Re: Cluster Freezes

I think you need to time it more carefully, so you know where the actual
time is taken

there are 3 times involved

1) the offline time of the group
2) the move of ownership of the group to the other node
3) the online time of the group

In regards to 1) the offline time of the group

you need to determine the offline time of each of the resource depending on
their dependency structure, e.g. how long does it take to take *just* the
File Share Resources, and leave IP / Name and Disk online, just to see if
offlining the Shares are taking the time or that it is something else.

Once you know the offline timings, do the same for 3) the online timings

usually the 2) move of ownership is reasonably fast and does not take a long
time.

In other words, you need to be more detailed in "group move is slow" and
determine what resource or resources is slow and doing what action
(off/on/move)

Rgds,
edwin.



"Rog" <Rog@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BA9BA565-5E11-4C48-B6D5-FFCDE3584FD3@xxxxxxxxxxxxxxxx
All,

I have a W2k3 R2 cluster that had about 10 disk and 150 file share
resources. When I attempt to failover the group it will take about 15
minutes
minimum to failover if successful. But, most recently it completly locks
up
both servers and you have to shut them both down and bring one up at a
time
to get the cluster back online.

If I take about a third of the file share resources offline, then I can
failover in about 10 minutes. I was first thinking that I might be dealing
with a timeout issue, but I didn't think it would cause the server to
freeze.

Is there a limit to the number of disk and file share resources you should
have in a single cluster group?

Anyone have any suggestions?

Thanks!


.