July 3, 2008 at 1:42 pm
Windows 2003, sql 2005 sp2 cluster
when you open up a sql server properties....
one of my systems shows virtual sql server name
second one shows the cluster name
when i'm connecting to those systems, i have no problems to connect to them
by specifying the sql virt name.
what is the right way for clusterd sql server...?
should it show the cluster name or sql virt name in the server properties?
BTW, the one that shows the clustername wqas not working properly.... like i couldn't open the error log files
fix was to create an alias in sql server configuration window
alias had the clustername as an allias and the virtual sql server name as a server, also named pipes type of connection has been used
July 5, 2008 at 10:55 am
you should connect using SQL Virtual server name not windows cluster name.
July 5, 2008 at 10:55 am
you should connect using SQL Virtual server name not windows cluster name.
July 6, 2008 at 7:15 pm
i understand that...
I'm just trying to find an answer why even though i follow the same
installation configuration, one of my clustered sql server shows in properties name
the same name that we chose for vitrual sql name
and second clustered sql shows the clustername in properties name for sql server
but i still have no problems connecting to it by sql server virtual name.
like i said before, i had to create an alias for that second cluster
where alias name is a cluster name and server is a virtual sql name, using named pipes connection.
So my question is why when you going to properties for clustered sql server,
in the name line it shows me a cluster group name instead of virt sql name???
July 6, 2008 at 8:49 pm
The only thing I can think of is that maybe you have SQL Server setup in the cluster group on that server instead of in the SQL group.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
July 6, 2008 at 10:14 pm
Hi,
I'm a bit confused, however it does sound like the 2nd instance was installed in the cluster group.
Do you have access to Cluster Admin (Start -> Run -> Cluadmin )? What do you see when you run this? How many groups do you see?
From the sounds of it, you should have about 4 groups
1. Cluster Group
2. Virtual SQL Server 1
3. Virtual SQL Server 2
4. MSDTC
The 'Cluster Group' usually only contains 'Cluster Name', 'Cluster IP Address' & and a cluster disk for the Quorum.
July 7, 2008 at 6:55 am
Here is more details:
Windows 2003 standard, sql 2005 sp2,
QA environment:
1. Cluster group name - CL1
2. Consist of two active/passive nodes
ND1 and ND2
3. Virtual sql server name SQLQA01
Right click on sql server properties:
Server name - SQLQA01 - Looks good!
Now second installation,
PR environment:
1. Cluster group name – CL2
2. Consist of two active/passive nodes
ND3 and ND4
3. Virtual sql server name SQLPR01
Right click on sql server properties:
Server name - CL2 - ?????????
The vierd part is that I was able to connect to this virtual sql server by specifying the sql virt name.
Some of the sql fetures like error log or dbmail were not working.
So the way around was: create an alias in sql configuration manager.
Where alias name CL2, net protocol Named Pipes, server SQLPR01.
Working just great.
It just bothers me, WHY it has different properties name if the same installation procedure was followed during both setups.
Also please someone explain, what is the difference between instance name and virtual sql name?
Is the default instance name has the same name as a cluster group name?
July 7, 2008 at 6:04 pm
I can only think of 2 reasons why you have this problem.
1. SQL Server was installed into the cluster group 'CL2' on your PR server.
2. The 'SQL Network Name' was setup / configured incorrectly within the SQL Server cluster group
To confirm this, we will need a bit more information from Cluster Administrator.
What are the group names?
And more importantly, what resources are within each group?
e.g.
Group: CL1
Resources:
- Cluster Name
- Cluster IP
- Disk X
Also, could you please run the below query on both QA & PR and post the output? I am happy for you to change the server names as long you keep it consistent.
SELECT CAST( SERVERPROPERTY('InstanceName') AS NVARCHAR(128)) AS 'InstanceName'
SELECT CAST( SERVERPROPERTY('IsClustered') AS NVARCHAR(128)) AS 'IsClustered'
SELECT CAST( SERVERPROPERTY('MachineName') AS NVARCHAR(128)) AS 'MachineName'
SELECT CAST( SERVERPROPERTY('ServerName')AS NVARCHAR(128)) AS 'ServerName'
SELECT CAST( SERVERPROPERTY('ComputerNamePhysicalNetBIOS')AS NVARCHAR(128)) AS 'ComputerNamePhysicalNetBIOS'
I am hoping the output of the query will help explain the difference between instance name, virtual SQL server & server name
July 8, 2008 at 7:55 am
QA
SQL VIRT Name QA1
InstanceName
NULL
IsClustered
1
MachineName
QA1
ServerName
QA1
ComputerNamePhysicalNetBIOS
ND1
===================================
PR
SQL VIRT Name PR1
InstanceName
NULL
IsClustered
1
MachineName
CL2
ServerName
CL2
ComputerNamePhysicalNetBIOS
ND3
-----------------------------------------------
most likely the cluster\windows configuration was done differently.
during the installation we chose default for instance name (so it should be a machine name)
the solution might be to give to a cluster and to a virt sql the same name
because now we have clustername cl1, nodename nd1, clustergrpoupe name sql and virtual sql name QA1
this is all tooooooo confusing
July 8, 2008 at 4:37 pm
It certainly looks like the installation was different between QA & PR.
The information you gave is still suggesting that the SQL Server instance was not installed in the Virtual Server named 'PR1'. Instead it has been installed into the cluster group CL2.
If you would like to confirm this, please check Cluster Admin as mentioned in my previous 2 posts...
Where to from here?
It might be possible to move a Clustered SQL Server instance into a different cluster group (e.g. Move all the SQL resources from CL2 into PR1), however unless you can find a solid reference on how this can be done I highly recommend you do not follow this path.
Even if you do manage to move the SQL resources into PR1, you will always have a difference between QA & PR. This difference may not be visible straight away, but somewhere in the registry there could be a difference, and when it comes time to install a hotfix, service pack, or upgrade to SQL 2008, that’s when the problems will arise...
If it were my cluster, I would rebuild it (including OS). If that was not possible then uninstall / reinstall the SQL instance only.
July 9, 2008 at 1:12 pm
I did checked the options and settings for both environments, like
Group:
Resources:
- Cluster Name
- Cluster IP
- Disk X
they are absolutely identical ( ofcourse the have dif sql names and cluster names)
The information you gave is still suggesting that the SQL Server instance was not installed in the Virtual Server named 'PR1'. Instead it has been installed into the cluster group CL2.[/u]
can you please elaborate on this one?
or tell me where i can find more detailes?
thanks
July 9, 2008 at 5:41 pm
Below is an example of how I think your cluster should be setup (what you would see in Cluster Admin)
Groups
CL2
Cluster IP Address
Cluster Name
Disk X:
PR1
SQL IP Address 1 (PR1)
SQL Network Name (PR1)
SQL Server
SQL Server Agent
SQL Server Fulltext
Disk Y:
Below is how I think your cluster has been setup. Notice all the resources are in CL2
Groups
CL2
Cluster IP Address
Cluster Name
Disk X
SQL IP Address 1 (PR1)
SQL Network Name (PR1)
SQL Server
SQL Server Agent
SQL Server Fulltext
Disk Y
PR1
However, I still could be wrong.
Could you please run the below command on both of your clusters in a cmd prompt (start -> run -> cmd) and post the output?
cluster /CLUSTER:CL2 RESOURCE
July 10, 2008 at 12:07 pm
thank you very much for your time and help!!!!!
we have 3 groups:
CL1
1. cluster group
2. msdtc
3. sql
actually both systems have sql installed on sql group, not on the cluster group
during the installation we specified SQL group , sql virtual name PR1 and default instance
why is it showing server name in one case as CL1 and
on the second system as PR1...... I have no idea:w00t::w00t:
July 10, 2008 at 12:28 pm
system 1
Resource Group Node Status
-------------------- -------------------- --------------- ------
Disk %: Cluster Group nd1 Online
M Drive MSDTC nd1 Online
MSDTC IP MSDTC nd1 Online
MSDTCPR1 MSDTC nd1 Online
MS_DTC MSDTC nd1 Online
Cluster IP Address SQL nd1 Online
CL1 SQL nd1 Online
Drive:% SQL nd1 Online
Drive:% SQL nd1 Online
Drive:% SQL nd1 Online
Drive:% SQL nd1 Online
SQL Network Name (pr1) SQL nd1 Online
SQL IP Address 1 (pr1) SQL nd1 Online
SQL Server SQL nd1 Online
SQL Server Agent SQL nd1 Online
SQL Server Fulltext SQL nd1 Online
QAM Launcher Resource XXXX SQL nd1 Online
system 2
Resource Group Node Status
-------------------- -------------------- --------------- ------
Disk %: SQL nd3 Online
Disk %: SQL nd3 Online
Disk %: SQL nd3 Online
Disk %: SQL nd3 Online
Cluster IP Address SQL nd3 Online
CL2 SQL nd3 Online
SQL Network Name (QA1) SQL nd3 Online
SQL IP Address 1 (QA1) SQL nd3 Online
SQL Server SQL nd3 Online
SQL Server Agent SQL nd3 Online
SQL Server Fulltext SQL nd3 Online
QAM Launcher Resource XXXX SQL nd3 Online
Disk %: Cluster Group nd3 Online
Disk %: MSDTC nd3 Online
MSDTC_IP MSDTC nd3 Online
MSDTCQA1 MSDTC nd3 Online
MS_DTC MSDTC nd3 Online
July 10, 2008 at 1:43 pm
slava davidchuk (7/10/2008)
system 1Resource Group Node Status
-------------------- -------------------- --------------- ------
Disk %: Cluster Group nd1 Online
Cluster IP Address SQL nd1 Online
CL1 SQL nd1 Online
Drive:% SQL nd1 Online
Drive:% SQL nd1 Online
Drive:% SQL nd1 Online
Drive:% SQL nd1 Online
system 2
Resource Group Node Status
-------------------- -------------------- --------------- ------
Disk %: SQL nd3 Online
Disk %: SQL nd3 Online
Disk %: SQL nd3 Online
Disk %: SQL nd3 Online
Cluster IP Address SQL nd3 Online
CL2 SQL nd3 Online
Disk %: Cluster Group nd3 Online
I think the problem is how the clusters have been configured. In both cases, you have the CL# resource and the Cluster IP Address resource in the SQL Group instead of in the Cluster Group. You also have the quorom drive configured in the SQL group on one cluster, but not on the other (highlighted above, note: I removed the SQL, QAM and MSDTC resources).
This means you have two IP addresses assigned to the SQL cluster group (Cluster and SQL). What you should have is:
Groups
Cluster Group
MSDTC Group
SQL Group
Cluster Group (resources)
Cluster IP Address
Cluster Name (dependent on Cluster IP Address)
Disk Q (Quorom)
MSDTC Group
Disk M
MSDTC (dependent on Disk M and MSDTC Name)
MSDTC IP
MSDTC Name (dependent on MSDTC Name)
SQL Group
[SQL disk resources]
SQL IP Address 1 (servername)
SQL Network Name (servername) (dependent on SQL IP Address 1)
SQL Server (dependent on SQL Network Name and disk resources)
SQL Server Agent
[other SQL services]
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply