Cluster name taking a long time to become online....

overworkedops
overworkedops used Ask the Experts™
on
I am using the "change group" function on the cluster administrator... it takes quite a long time for "Cluster Name" to get back online.

Any reason this might be?

I can wipe the boxes if need be, but I'd like to understand the reasoning for the problem first! :)

Thanks!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
Oh and to quantify, a "Long time", it's like 3 minutes or so.

Thanks again!
Top Expert 2006

Commented:
How many instances in the cluster? Is it active/passive?
change group will make the node failover to the other one, swaping the resources over.
If the required memory is high or if long transactions needs to be rolled forward or backwards, it can increase the time taken.
The SQL service should restart in less than a minute most times (if failed by hand), asside from transactions.

Author

Commented:
Single instance, active/passive. I'm going to wipe and see what happens... I'm sure it will fix it.
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

Author

Commented:
Okay, I've wiped... no fix. The cluster name is still taking a long time to fail over. I wiped EVERYTHING -- this is a cluster that's set up from scratch. Any ideas what it might be? I am thinking something on the domain controller, but I'm not sure.

Commented:
What is the load like? If any?

Author

Commented:
None... there's nothing on the box except SP1 and the cluster services.

I think it's a DNS issue, but I only find 1 entry for the cluster in DNS and I deleted that before I rebuilt... just weird :\

Commented:
Available memory on each node?
Any load on the SAN?

Author

Commented:
8 GB of RAM, plenty free... it's not a SAN, just DAS, an HP msa 500, using the shared bus.

Mind you, the disk group fails over perfectly and fast, so does the cluster IP... just the cluster name takes a long time.

Commented:
Have a look in the SQL server logs to see the sequence of events - perhaps they will indicate a particular process that is taking time.

Author

Commented:
It was reverse DNS... works fine now :)
Top Expert 2006

Commented:
Cool :)
PAQed with points refunded (500)

Computer101
EE Admin

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial