July 11, 2008 at 2:33 am
I agree with Jeffery. I was wrong, but close!
I thought that you had installed SQL server into the cluster group, but from the output you have given, it appears you have done the reverse by setting up the Quorum in the SQL group.
The reason you have the difference between QA1 & PR1 is (I think!) because CL2 is picking up the network name of the cluster, instead of the SQL network name. This could (have never done this before) be fixed by taking the group offline, and modifying the SQL Server dependencies to use the SQL network name instead of the cluster (no idea if this will work sorry...)
I don't have much experience with modifying the Quorum, but I think it is possible to move the Quorum resources into the cluster group (CL#), without the need for a rebuild.
You should research this before proceeding, but the method might go something like:
1) Take all groups offline
2) Ensure that no resources are dependent on the cluster resources (cluster name and cluster ip).
3) Move Quorum resources to cluster group CL#
4) Set dependencies on the Quorum resources
5) Start quorum and perform failover testing.
6) Start SQL and perform failover testing.
It may be better (and easier!) to rebuild the cluster, but I know this is not usually possible due to outage requirements.
Good luck!
July 15, 2008 at 2:06 pm
Thank you ALL!!!!!!!
I'll try that.
December 9, 2008 at 3:02 pm
problem has been resolved
we have 3 SAN drives and they were assigned as a resource
to cluster group ip address.
as soon as all these 3 drives were assigned to sql virtual name ip -
sql server name got 'magically' changed from cluster name to actual sql name
my G-t, it was driving me craaaazy all this time 🙂
THANK YOU ALL FOR YOUR HELP!!!!!!!!!
BEST WEBSITE EVER!!!!!!!!!!!!!
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply