April 28, 2011 at 1:27 pm
Hi Experts,
While installing SQL Server 2008 R2 in the Failover multi-node environment, getting the below error -
"The SQL Server failover cluster instance name 'server01' already exists as a Clustered resource. Specify a different failover cluster instance name".
I am using the below details in the "Instance Configuration" page in the Failover Cluster Mgmt -
SQL Server Network Name: server01
Named Instance: SQL01.
what might be the cause? I am scared to update anything in the Windows Cluster Registry..
Thanks.
April 28, 2011 at 4:32 pm
In the failover cluster at windows level a resource group called server01 has already been created. go into Failover Cluster Manager and if it has been set up with the intention of using it for SQL, remove it, let the SQL install create it.
---------------------------------------------------------------------
April 29, 2011 at 3:11 am
you may also need to cleanse AD and DNS too
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 29, 2011 at 4:04 am
Hi George Sibbald,
In the SQL Server Failover Cluster Admin, under 'Services and Applications' section I can see the SQL Instance - 'SQL01' available and also under nodes section I can see the new Cluster node CL01 which is the preferred owner of the SQL Instance.
Do I need to delete the service 'SQL01' under the Services and Applications and need to install SQL Server using 'New SQL Server Failover Cluster Installation' setup file? Please suggest.
Also, for multi node active-active cluster, to the other node we again need to 'Add node to a SQL Server Failover Cluster'.
Can you please confirm on the above furnished two points?
Also, if you are aware about any specific good article on SQL Server 2008 installation on windows 2008 Cluster please let me know for multi-node installation do let me know?
Regards,
Thanks.
April 29, 2011 at 11:37 am
What is ACTIVE / ACTIVE failover node,is there any thing providing by microsoft,according to my knowledge there is no any active/active failover node in SQL Server.
ACTIVE/ACTIVE means 2 separate instances in a cluster,there is no load balancing
If you are installing Active/Passive and Active/Active multi instances Failover node then go to Cluster Management and check is this resource exist or not because SQL Server create sql server resource at the time of installation,if you are installing second instance then you should have to give separate resource
Regards,
Syed Jahanzaib Bin Hassan
MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
April 29, 2011 at 12:08 pm
Syed Jahanzaib Bin hassan (4/29/2011)
ACTIVE/ACTIVE means 2 separate instances in a cluster,there is no load balancing
Active\Active means more than one instance of SQL server active on more than 1 cluster node 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 29, 2011 at 4:58 pm
Sourav-657741 (4/29/2011)
Hi George Sibbald,In the SQL Server Failover Cluster Admin, under 'Services and Applications' section I can see the SQL Instance - 'SQL01' available and also under nodes section I can see the new Cluster node CL01 which is the preferred owner of the SQL Instance.
Do I need to delete the service 'SQL01' under the Services and Applications and need to install SQL Server using 'New SQL Server Failover Cluster Installation' setup file? Please suggest.
Also, for multi node active-active cluster, to the other node we again need to 'Add node to a SQL Server Failover Cluster'.
I cannot see your setup and I don't have a 2008R2 multi-instance cluster to compare against but yes I would say delete the service under services and applications named the same as the SQL instance you want to create. Presumably this does not yet contain the SQL instance you are trying to create as a resource
Yes you will have to run 'New SQL Server Failover Cluster Installation' followed by 'Add node to a SQL Server Failover Cluster' to create the second node in the pair for this instance.
-- or call the new instance something different, it is hard to be 100% sure of the root cause without sight of the cluster and a complete history of what led up to this situation. But the error is quite explicit.
---------------------------------------------------------------------
May 18, 2011 at 2:43 am
Sourav-657741 (4/28/2011)
Hi Experts,While installing SQL Server 2008 R2 in the Failover multi-node environment, getting the below error -
"The SQL Server failover cluster instance name 'server01' already exists as a Clustered resource. Specify a different failover cluster instance name".
I am using the below details in the "Instance Configuration" page in the Failover Cluster Mgmt -
SQL Server Network Name: server01
Named Instance: SQL01.
what might be the cause? I am scared to update anything in the Windows Cluster Registry..
Hi Did you get a resolution for this? I'm Just going to attempt the same "multiple active
instance failover cluster" 2008R2 with SQL 2005 64bit any Advise?
May 18, 2011 at 2:50 am
btw, I cannot find any god docs on this setup anywhere. I've been pointed at these links but they have nothing specific:
http://search.4shared.com/q/1/SQL%20Server%20cluster
http://www.4shared.com/file/TqMEKZYZ/ApressProSQLServer2005HighAvai.htm
Does anyone have any docs please?
May 18, 2011 at 3:51 am
remember that when deploying multiple clustered instances of SQL Server that they all require their own unique resources for
disk
IP Address
Network name
You do not use the same network for multiple clustered instances of SQL Server
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 18, 2011 at 3:57 am
perry, can the instances share a backup drive? would this be set up as a file share?
---------------------------------------------------------------------
May 18, 2011 at 4:04 am
do you know what, it's something i have never tried. If you set up a share and add this as a resource into a cluster group i wouldn't be tempted to then broadcast it as a failover resource in another cluster group. I prefer to keep them separate myself. Worth testing though, I'll have a look at that
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 18, 2011 at 4:33 am
good point, what to do when a failover occurs. As a share it could be visible from both nodes?
I am sure I saw this setup on a 2000 cluster years ago, about 5 instances, 1 drive per instance (all data) and 1 backup drive.
---------------------------------------------------------------------
May 18, 2011 at 5:05 am
Thanks for the responce:
So you have 2 unique cluster name's? seperate disk resources that are accessable from all nodes, Seperate Private and Public Nics and just one Quorum in both Cluster groups?
Why is there no documentation is this not usually done??
May 18, 2011 at 5:57 am
j.jj (5/18/2011)
So you have 2 unique cluster name's?
You have unique network names!
j.jj (5/18/2011)
seperate disk resources that are accessable from all nodes,
Yes, otherwise how would failover occur
j.jj (5/18/2011)
Seperate Private and Public Nics
I'm assuming you are referring to the physical NICs. No you dont have separate NICs
j.jj (5/18/2011)
and just one Quorum in both Cluster groups?
You have one quorum for the Windows cluster whether it be a disk or file share (MNS) based quorum. You do not have a quorum for each application cluster group
j.jj (5/18/2011)
Why is there no documentation is this not usually done??
If you search a little you should find plenty
You need to separate out the Windows cluster level from the clustered application level in your thoughts. Realise what resources are necessary to create a Windows cluster before even installing a clustered application such as SQL Server or Exchange Server!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply