We have a windows 8 R2 2-node cluster running a few shared folders & print server resources on a MSA (DAS) storage and it has been working ok, and no changes have been made. Server/storage have redundant power supply and is on a 42U rack with PDUs. Equipment connects to PDU, PDUs connect to (2) R5500 & 2 R3000 UPS with enough redundancy, and the bldg. is on a generator. With all this power redundancy, for last few months we have been experiencing power surges which cause cluster fail over. The cluster quorum node looses connection, quorum fails over to node 2, however, neither node is able to load the disk for the shared resource that fail over too (errors are, disk cannot be found, etc).
Properties for resources are as follows:
"If resource fails, restart on current node, restarts value is 15:00"
"max restarts is 1"
"If restart is unsuccessful, fail over all resources in the service or app" (is checked)
"If all the restart attempts fail, begin restarting again after the specified period, value is 01:00"
"Pending time value is 03:00"
I ran a cluster validation process, configuration was all good. However, there was a warning that the "print spooler" resource "was not configured to the standard "pending timeout" value. All resources as well as the "print server" itself have the default setting pending timeout value of "03:00", but the "print spooler" is set to "05:00". Don't remember if we changed value at setup, or if this is default for a"print spooler". Appreciate if someone can shed some light on this. Should it be set to default of 03:00 like other resources? Should anything in the cluster policies be changed? any advice what else to look for? bad ups even though they all light up green? do PDUs go bad?
Appreciate your advice. Thank you.
-CocoFlor
HR