Clearing LOG Files: active

Showing posts with label active. Show all posts

Thursday, March 29, 2012

Cluster SQL Active-Active

My friends:
I need document information about the installation process of SQL in Cluster
with two instances, both active, one in each Server. In summary I want to
install a Cluster of SQL Active-Active, for take greater benefit of both
Cluster nodes.
Even though I have looked for in BOL (follow the recommendations of Maxi), I
had investigate and knock the same trouble, there are only information about
the Active-Pasive installation, and I'll wish a procedure or document about
Active-Active setup and installation.
If someone knows where I can find the information, or somebody understand
about Active-Active installation, please give it me know. Thanks a lot.
Regards,
Carlo Sorrel
Hello Carlo,
Once you have installed the first instance of virtual SQL Server 2000 then the steps for installing the second instance of virtual SQL Server 2000 is exactly the same. The second virtual instance of SQL Server 2000
will need a seperate shared drive (you cannot use the shared drive that you used for the first instance), unique SQL IP Address (again you cannot use the one you used for your windows cluster ip or the first sql
server ip) and unique SQL network name. Also, if the first virtual instance is a default instance then the second instance can ONLY be a named instance. You CANNOT have two default virtual SQL Server 2000
instance on the same cluster. To have both the instances similar, many customers install both instances of virtual SQL Server 2000 as named instances.
Since you have multiple instances (2 in your case), you will need to ensure that all server nodes have the same resources (processor, memory) and it is enough to handle the instances that could potentially fail to
that node. Another important consideration is to cap memory usage of the instance of SQL Server 2000 with max server memory. Especially if AWE memory is enabled, max server memory must be set in a
multiple-instance cluster to prevent starving the server node.
If you have a Windows Server 2003 EE cluster then you may find the following webcast useful
TechNet Support WebCast: How to install a Microsoft SQL Server 2000 virtual server on a Microsoft Windows Server 2003 cluster
Discusses how to install Microsoft SQL Server 2000 clustering on Microsoft Windows Server 2003 and differences between Microsoft Windows 2000 Server and Windows Server 2003.
http://support.microsoft.com/default...b;en-us;888121
For Win2K Adv Server cluster, you may find the following whitepaper useful
SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
Review the above and feel free to post any other qs that you may have.
Additional Information
=======================
Here is some other related links that you may find useful
INF: Clustered SQL Server Do's, Don'ts, and Basic Warnings
http://support.microsoft.com/?kbid=254321
Introduction to Microsoft SQL Server 2000 Clustering
http://support.microsoft.com/default...lurb051001.asp
Microsoft SQL Server 2000 Virtual Server: Things You Should Know
http://support.microsoft.com/default...lurb032602.asp
Microsoft SQL Server 2000 Virtual Server Basic Setup, Maintenance, and Service Pack http://support.microsoft.com/default...lurb061002.asp
Microsoft SQL Server 2000 Failover Clustering Disaster Recovery Procedures
http://support.microsoft.com/default...lurb101802.asp
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Hi
Just be aware, Active-Active does not mean load balancing. It means 2
instances of different databases, each running by default on one of the
nodes of a cluster.
The references Uttam has supplied are great and will help you along.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Carlo Sorrel" <csorrel@.hotmail.com> wrote in message
news:#nPFJo7AFHA.3576@.TK2MSFTNGP11.phx.gbl...
> My friends:
>
> I need document information about the installation process of SQL in
Cluster
> with two instances, both active, one in each Server. In summary I want to
> install a Cluster of SQL Active-Active, for take greater benefit of both
> Cluster nodes.
>
> Even though I have looked for in BOL (follow the recommendations of Maxi),
I
> had investigate and knock the same trouble, there are only information
about
> the Active-Pasive installation, and I'll wish a procedure or document
about
> Active-Active setup and installation.
>
> If someone knows where I can find the information, or somebody understand
> about Active-Active installation, please give it me know. Thanks a lot.
>
> Regards,
>
> Carlo Sorrel
>
|||first, sorry my english..., apears this error during instalattion the second instance on Cluster Windows 2003.
The description for Event ID ( 17052 ) in Source ( MSSQL$LASCAR ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 35; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Tahnk's.
Carlo Sorrel.
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> escribi en el mensaje news:uX597q8AFHA.1680@.cpmsftngxa10.phx.gbl...
> Hello Carlo,
> Once you have installed the first instance of virtual SQL Server 2000 then the steps for installing the second instance of virtual SQL Server 2000 is exactly the same. The second virtual instance of SQL Server 2000
> will need a seperate shared drive (you cannot use the shared drive that you used for the first instance), unique SQL IP Address (again you cannot use the one you used for your windows cluster ip or the first sql
> server ip) and unique SQL network name. Also, if the first virtual instance is a default instance then the second instance can ONLY be a named instance. You CANNOT have two default virtual SQL Server 2000
> instance on the same cluster. To have both the instances similar, many customers install both instances of virtual SQL Server 2000 as named instances.
> Since you have multiple instances (2 in your case), you will need to ensure that all server nodes have the same resources (processor, memory) and it is enough to handle the instances that could potentially fail to
> that node. Another important consideration is to cap memory usage of the instance of SQL Server 2000 with max server memory. Especially if AWE memory is enabled, max server memory must be set in a
> multiple-instance cluster to prevent starving the server node.
> If you have a Windows Server 2003 EE cluster then you may find the following webcast useful
> TechNet Support WebCast: How to install a Microsoft SQL Server 2000 virtual server on a Microsoft Windows Server 2003 cluster
> Discusses how to install Microsoft SQL Server 2000 clustering on Microsoft Windows Server 2003 and differences between Microsoft Windows 2000 Server and Windows Server 2003.
> http://support.microsoft.com/default...b;en-us;888121
>
> For Win2K Adv Server cluster, you may find the following whitepaper useful
> SQL Server 2000 Failover Clustering
> http://www.microsoft.com/technet/pro.../failclus.mspx
> Review the above and feel free to post any other qs that you may have.
> Additional Information
> =======================
> Here is some other related links that you may find useful
> INF: Clustered SQL Server Do's, Don'ts, and Basic Warnings
> http://support.microsoft.com/?kbid=254321
> Introduction to Microsoft SQL Server 2000 Clustering
> http://support.microsoft.com/default...lurb051001.asp
> Microsoft SQL Server 2000 Virtual Server: Things You Should Know
> http://support.microsoft.com/default...lurb032602.asp
>
> Microsoft SQL Server 2000 Virtual Server Basic Setup, Maintenance, and Service Pack http://support.microsoft.com/default...lurb061002.asp
> Microsoft SQL Server 2000 Failover Clustering Disaster Recovery Procedures
> http://support.microsoft.com/default...lurb101802.asp
> Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
> http://support.microsoft.com/default...lurb020703.asp
>
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>

Cluster SQL 2000 errorlog problem

Tuesday, March 27, 2012

Cluster SQL 2000 errorlog problem

We've recently installed a couple of Windows Server 2003 Ent Ed servers with
SQL 2000 Ent Ed and one of the active/active nodes continually gives the
error below in the Application Event log.
The NT user which was used to install the server and owns the directories
and files below has full rights so this should not be an issue.
I've checked MSDN, etc. but nothing which seems to help.
Thanks.
Ron
--
17050 :
initerrlog: Could not open error log file 'D:\Program Files\Microsoft SQL
Server\MSSQL\log\ERRORLOG'. Operating system error = 3(The system cannot find
the path specified.).
--Ron,
Is drive D local to the server or on the cluster's shared drives? The error
message could be implying that the node in question was installed with the
data files on a local drive.
Hope this helps,
Ron
--
Ron Talmage
SQL Server MVP
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:7BABBA49-964A-4422-ACB8-B559661A5F05@.microsoft.com...
> We've recently installed a couple of Windows Server 2003 Ent Ed servers
with
> SQL 2000 Ent Ed and one of the active/active nodes continually gives the
> error below in the Application Event log.
> The NT user which was used to install the server and owns the directories
> and files below has full rights so this should not be an issue.
> I've checked MSDN, etc. but nothing which seems to help.
> Thanks.
> Ron
> --
> 17050 :
> initerrlog: Could not open error log file 'D:\Program Files\Microsoft SQL
> Server\MSSQL\log\ERRORLOG'. Operating system error = 3(The system cannot
find
> the path specified.).
> --|||BTW, there's a webcast on troubleshooting a SQL Server 2000 cluster install
that contains a lot of detail not available elsewhere:
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd020703/wcdblurb020703.asp
Ron
--
Ron Talmage
SQL Server MVP
"Ron Talmage" <rtalmage@.prospice.com> wrote in message
news:%23c46wJI%23EHA.3368@.TK2MSFTNGP15.phx.gbl...
> Ron,
> Is drive D local to the server or on the cluster's shared drives? The
error
> message could be implying that the node in question was installed with the
> data files on a local drive.
> Hope this helps,
> Ron
> --
> Ron Talmage
> SQL Server MVP
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:7BABBA49-964A-4422-ACB8-B559661A5F05@.microsoft.com...
> > We've recently installed a couple of Windows Server 2003 Ent Ed servers
> with
> > SQL 2000 Ent Ed and one of the active/active nodes continually gives the
> > error below in the Application Event log.
> >
> > The NT user which was used to install the server and owns the
directories
> > and files below has full rights so this should not be an issue.
> >
> > I've checked MSDN, etc. but nothing which seems to help.
> > Thanks.
> > Ron
> >
> > --
> > 17050 :
> > initerrlog: Could not open error log file 'D:\Program Files\Microsoft
SQL
> > Server\MSSQL\log\ERRORLOG'. Operating system error = 3(The system cannot
> find
> > the path specified.).
> >
> > --
>|||Ron,
I'll review the webcast...thanks!
SQL Server is installed on the C: drive, the data files are installed on D:
which is a SAN drive share.
I've rebooted both nodes and only started node1...with node2 offline, there
errors are not appearing in the event logs...? Seems odd as it's node1 which
is logging the errors...any other ideas?
Thanks.
Ron
"Ron Talmage" wrote:
> BTW, there's a webcast on troubleshooting a SQL Server 2000 cluster install
> that contains a lot of detail not available elsewhere:
> http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd020703/wcdblurb020703.asp
> Ron
> --
> Ron Talmage
> SQL Server MVP
> "Ron Talmage" <rtalmage@.prospice.com> wrote in message
> news:%23c46wJI%23EHA.3368@.TK2MSFTNGP15.phx.gbl...
> > Ron,
> >
> > Is drive D local to the server or on the cluster's shared drives? The
> error
> > message could be implying that the node in question was installed with the
> > data files on a local drive.
> >
> > Hope this helps,
> > Ron
> > --
> > Ron Talmage
> > SQL Server MVP
> >
> > "Ron" <Ron@.discussions.microsoft.com> wrote in message
> > news:7BABBA49-964A-4422-ACB8-B559661A5F05@.microsoft.com...
> > > We've recently installed a couple of Windows Server 2003 Ent Ed servers
> > with
> > > SQL 2000 Ent Ed and one of the active/active nodes continually gives the
> > > error below in the Application Event log.
> > >
> > > The NT user which was used to install the server and owns the
> directories
> > > and files below has full rights so this should not be an issue.
> > >
> > > I've checked MSDN, etc. but nothing which seems to help.
> > > Thanks.
> > > Ron
> > >
> > > --
> > > 17050 :
> > > initerrlog: Could not open error log file 'D:\Program Files\Microsoft
> SQL
> > > Server\MSSQL\log\ERRORLOG'. Operating system error = 3(The system cannot
> > find
> > > the path specified.).
> > >
> > > --
> >
> >
>
>sql sql

Cluster Set up Question

Hello,
We are implementing clustering (Active/Passive) in our Production environment.
So we will have two windows server 2003 for SQL SERVER. (ProdDbServer1 and
ProdDbServer2)
I will install SQL Server on both the machine and i will create my database
(FinDB)
on both the machine's SQL SERVER with all the tables,store procs, functions
etc.
So lets say if my Active Server is in action and accepting all the OLTP
transaction
and for some reason if it goes fail...How can passive server can take over,
how
passive server can be at the same point of the fail of active server ?
Bacically how both the Database will be in sink with each other ?
Pls help me
A cluster consists of two machines and a storage system that is physically
connected to both systems. The Cluster software arbitrates ownership of the
disk resource so that only one server can access it at a time. The cluster
software also monitor the sql instance on the active host node for failure.
If the first node fails, ownership of the SQL instance and the corresponding
disk resource is transferred to the other node. From the outside, it looks
like the SQL Server stopped and restarted.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:3F5342B1-3AB6-4CD7-B763-33587B1BED0E@.microsoft.com...
> Hello,
> We are implementing clustering (Active/Passive) in our Production
> environment.
> So we will have two windows server 2003 for SQL SERVER. (ProdDbServer1 and
> ProdDbServer2)
> I will install SQL Server on both the machine and i will create my
> database
> (FinDB)
> on both the machine's SQL SERVER with all the tables,store procs,
> functions
> etc.
> So lets say if my Active Server is in action and accepting all the OLTP
> transaction
> and for some reason if it goes fail...How can passive server can take
> over,
> how
> passive server can be at the same point of the fail of active server ?
> Bacically how both the Database will be in sink with each other ?
> Pls help me
|||Thanks Geoff.
So From your reply, I understand that i will have to install SQL SERVER 2000
on both the windows 2003 server.
I have following questions.
1) After installing SQL SERVER on both the windows m/c, When i create
database on both the machine, Would i have to mentioned same Data files and
Transaction Log Path ( Because we will have storage will be in SAN), when i
create DB ?
2) For example if i create one table in the FinDB of on ServerA and then if
i go to FinDB of ServerB, I will see that table there too, if i will have
Datafiles and Transaction Log Path are same for both the servers ?
"Geoff N. Hiten" wrote:

> A cluster consists of two machines and a storage system that is physically
> connected to both systems. The Cluster software arbitrates ownership of the
> disk resource so that only one server can access it at a time. The cluster
> software also monitor the sql instance on the active host node for failure.
> If the first node fails, ownership of the SQL instance and the corresponding
> disk resource is transferred to the other node. From the outside, it looks
> like the SQL Server stopped and restarted.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "mvp" <mvp@.discussions.microsoft.com> wrote in message
> news:3F5342B1-3AB6-4CD7-B763-33587B1BED0E@.microsoft.com...
>
>
|||Thanks Geoff.
So From your reply, I understand that i will have to install SQL SERVER 2000
on both the windows 2003 server.
I have following questions.
1) After installing SQL SERVER on both the windows m/c, When i create
database on both the machine, Would i have to mentioned same Data files and
Transaction Log Path ( Because we will have storage will be in SAN), when i
create DB ?
2) For example if i create one table in the FinDB of on ServerA and then if
i go to FinDB of ServerB, I will see that table there too, if i will have
Datafiles and Transaction Log Path are same for both the servers ?
"Geoff N. Hiten" wrote:

> A cluster consists of two machines and a storage system that is physically
> connected to both systems. The Cluster software arbitrates ownership of the
> disk resource so that only one server can access it at a time. The cluster
> software also monitor the sql instance on the active host node for failure.
> If the first node fails, ownership of the SQL instance and the corresponding
> disk resource is transferred to the other node. From the outside, it looks
> like the SQL Server stopped and restarted.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "mvp" <mvp@.discussions.microsoft.com> wrote in message
> news:3F5342B1-3AB6-4CD7-B763-33587B1BED0E@.microsoft.com...
>
>
|||Does anyone want to rethink their perspective on why active/active and
active/passive should be used as terminology?
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:3F5342B1-3AB6-4CD7-B763-33587B1BED0E@.microsoft.com...
> Hello,
> We are implementing clustering (Active/Passive) in our Production
> environment.
> So we will have two windows server 2003 for SQL SERVER. (ProdDbServer1 and
> ProdDbServer2)
> I will install SQL Server on both the machine and i will create my
> database
> (FinDB)
> on both the machine's SQL SERVER with all the tables,store procs,
> functions
> etc.
> So lets say if my Active Server is in action and accepting all the OLTP
> transaction
> and for some reason if it goes fail...How can passive server can take
> over,
> how
> passive server can be at the same point of the fail of active server ?
> Bacically how both the Database will be in sink with each other ?
> Pls help me
|||If you install SQL Server twice, you will have 2 physically separate
instances of SQL Server running within a single cluster. If you then create
your database in each of these instances, you will have 2 physically
separate copies of the database. In order to synchronize data between the
two databases, you would have to implement replication, log shipping, or
database mirroring (2005 only). If one of the servers failed, you would
have to change your application connections to point at the other SQL Server
instance.
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:3F5342B1-3AB6-4CD7-B763-33587B1BED0E@.microsoft.com...
> Hello,
> We are implementing clustering (Active/Passive) in our Production
> environment.
> So we will have two windows server 2003 for SQL SERVER. (ProdDbServer1 and
> ProdDbServer2)
> I will install SQL Server on both the machine and i will create my
> database
> (FinDB)
> on both the machine's SQL SERVER with all the tables,store procs,
> functions
> etc.
> So lets say if my Active Server is in action and accepting all the OLTP
> transaction
> and for some reason if it goes fail...How can passive server can take
> over,
> how
> passive server can be at the same point of the fail of active server ?
> Bacically how both the Database will be in sink with each other ?
> Pls help me
|||No. You create the cluster. You then install a single copy of SQL Server
into the cluster. You then create your database inside that instance. You
do not install SQL Server directly to a machine. It is installed to the
cluster.
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:95A55E02-1BCB-47E1-9458-E01080486B3D@.microsoft.com...[vbcol=seagreen]
> Thanks Geoff.
> So From your reply, I understand that i will have to install SQL SERVER
> 2000
> on both the windows 2003 server.
> I have following questions.
> 1) After installing SQL SERVER on both the windows m/c, When i create
> database on both the machine, Would i have to mentioned same Data files
> and
> Transaction Log Path ( Because we will have storage will be in SAN), when
> i
> create DB ?
> 2) For example if i create one table in the FinDB of on ServerA and then
> if
> i go to FinDB of ServerB, I will see that table there too, if i will have
> Datafiles and Transaction Log Path are same for both the servers ?
> "Geoff N. Hiten" wrote:
|||The SQL Installer is cluster-aware. That is, it handles all the details of
cluster-wide installation. It creates the virtual server and installs the
local binaries on all nodes. It also groups all the cluster resources and
sets the dependencies correctly. Once SQL is running and you are connected,
there is almost no difference in SQL operations between clustered and
non-clustered SQL Servers. You end up connecting to a virtual SQL Server
instance that looks identical regardless of which node is actually hosting
it at the moment.
Here is an excellent overview of SQL failover clustering that you may find
helpful:
http://www.microsoft.com/technet/pro.../failclus.mspx
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:95A55E02-1BCB-47E1-9458-E01080486B3D@.microsoft.com...[vbcol=seagreen]
> Thanks Geoff.
> So From your reply, I understand that i will have to install SQL SERVER
> 2000
> on both the windows 2003 server.
> I have following questions.
> 1) After installing SQL SERVER on both the windows m/c, When i create
> database on both the machine, Would i have to mentioned same Data files
> and
> Transaction Log Path ( Because we will have storage will be in SAN), when
> i
> create DB ?
> 2) For example if i create one table in the FinDB of on ServerA and then
> if
> i go to FinDB of ServerB, I will see that table there too, if i will have
> Datafiles and Transaction Log Path are same for both the servers ?
> "Geoff N. Hiten" wrote:
|||Thanks for the reply.
No i do not want two sql server instance in single cluster, I just want one
instance in my cluster. so what should i do, install SQL SERVER 2000 Software
and create my database in just one machine (ProdSqlServerA)?
If i do like this and if i go to another sever (ProdSqlServerB), would i see
SQL SERVER and my created Db on that maching too ?
"Z" wrote:

> If you install SQL Server twice, you will have 2 physically separate
> instances of SQL Server running within a single cluster. If you then create
> your database in each of these instances, you will have 2 physically
> separate copies of the database. In order to synchronize data between the
> two databases, you would have to implement replication, log shipping, or
> database mirroring (2005 only). If one of the servers failed, you would
> have to change your application connections to point at the other SQL Server
> instance.
>
> "mvp" <mvp@.discussions.microsoft.com> wrote in message
> news:3F5342B1-3AB6-4CD7-B763-33587B1BED0E@.microsoft.com...
>
>
|||No thanks! I don't want Mike and Geoff mad at me anymore on this subject.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Z" <z@.z.com> wrote in message
news:%23MIgYMvFGHA.984@.tk2msftngp13.phx.gbl...
> Does anyone want to rethink their perspective on why active/active and
> active/passive should be used as terminology?
>
> "mvp" <mvp@.discussions.microsoft.com> wrote in message
> news:3F5342B1-3AB6-4CD7-B763-33587B1BED0E@.microsoft.com...
>
sql sql

Cluster Server Planning.

I would like some advise on my plan to install an active/active sql cluster.
The plan is to build 2 boxes with W2k3 server and SQL2003. I'll have 13
drives on a shared disk storage (two sets of mirrored drives) (two sets of
Raid 5 [4 drives each]) (1 global hot spare). I'll create a 1 Gig logical
drive (Q & P)on each of the mirrored sets (P will be a right-off but will
keep everything looking the same). The Q drive is for the Quorum. So I'll
have C: and D: on each machine, (Q: E

mirrored drives F: Raid5 (P: G

mirrored drives H: Raid5. SQL1 will own Q: E: and F:, SQL2 will own P: G:
and H:. E: and G: will be for transaction logs while F: and H: are for the
databases. I'll install instances of sql running on each server and spilt
the databases between the two (we have around fifty). Is this a sound plan,
or have I just wasted my time?
That sounds pretty good. I would seriously look at RAID 10 rather than RAID
5. The difference in write performance can be huge.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:9AD5CF79-5664-466C-AB15-F48C4F99972C@.microsoft.com...
> I would like some advise on my plan to install an active/active sql
cluster.
> The plan is to build 2 boxes with W2k3 server and SQL2003. I'll have 13
> drives on a shared disk storage (two sets of mirrored drives) (two sets of
> Raid 5 [4 drives each]) (1 global hot spare). I'll create a 1 Gig logical
> drive (Q & P)on each of the mirrored sets (P will be a right-off but will
> keep everything looking the same). The Q drive is for the Quorum. So I'll
> have C: and D: on each machine, (Q: E

mirrored drives F: Raid5 (P: G

> mirrored drives H: Raid5. SQL1 will own Q: E: and F:, SQL2 will own P:
G:
> and H:. E: and G: will be for transaction logs while F: and H: are for
the
> databases. I'll install instances of sql running on each server and spilt
> the databases between the two (we have around fifty). Is this a sound
plan,
> or have I just wasted my time?
|||I do not understand the Q and P drive assignment.
I have a Q (Quorum) in a seperate cluster resource group (with seperate
ip-address an networkname)
I have a X (MSDTC) in a seperate cluster resource group (with seperate
ip-address an networkname)
The Q and X drive do not come back in the SQL cluster resource group's
You do not mention a seperate cluster resource group for MSDTC. You should
do that.
Gr. G
(more info on MSDTC: http://sswug.org/blogging/gbrander/)
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:9AD5CF79-5664-466C-AB15-F48C4F99972C@.microsoft.com...
>I would like some advise on my plan to install an active/active sql
>cluster.
> The plan is to build 2 boxes with W2k3 server and SQL2003. I'll have 13
> drives on a shared disk storage (two sets of mirrored drives) (two sets of
> Raid 5 [4 drives each]) (1 global hot spare). I'll create a 1 Gig logical
> drive (Q & P)on each of the mirrored sets (P will be a right-off but will
> keep everything looking the same). The Q drive is for the Quorum. So I'll
> have C: and D: on each machine, (Q: E

mirrored drives F: Raid5 (P: G

> mirrored drives H: Raid5. SQL1 will own Q: E: and F:, SQL2 will own P:
> G:
> and H:. E: and G: will be for transaction logs while F: and H: are for
> the
> databases. I'll install instances of sql running on each server and spilt
> the databases between the two (we have around fifty). Is this a sound
> plan,
> or have I just wasted my time?
|||I am not planning going to use and entire physical disk for the Quorum. I'm
going to make a partition on a mirrored set (that will be a physical disk)
that will be the Q: drive. The P: drive is just my way of keeping
everything looking the same. My plan is to have only 2 cluster groups.
Group 1 be will the Cluster IP, Cluster Name, the Physical Disk (E: Q

, the
Physical Disk (F

, the MSDTC, and the first instance of SQL. Group 1 will
be owned by server1. Group 2 be will the Physical Disk (G: P

, the
Physical Disk (H

, and the second instance of SQL. Group 2 will be owned by
server2. Will this work ?
"Gé Brander" wrote:

> I do not understand the Q and P drive assignment.
> I have a Q (Quorum) in a seperate cluster resource group (with seperate
> ip-address an networkname)
> I have a X (MSDTC) in a seperate cluster resource group (with seperate
> ip-address an networkname)
> The Q and X drive do not come back in the SQL cluster resource group's
> You do not mention a seperate cluster resource group for MSDTC. You should
> do that.
> Gr. Gé
> (more info on MSDTC: http://sswug.org/blogging/gbrander/)
> "Wayne" <Wayne@.discussions.microsoft.com> wrote in message
> news:9AD5CF79-5664-466C-AB15-F48C4F99972C@.microsoft.com...
>
>
|||I too and lost by your wording I think, or maybe cause its Monday here. Are
you saying you will split a LUN into 2 or more partitions and then try to
use different partitions with different nodes? Clustering does not deal with
partitions, only drives. So a node or instance will not be able to share a
drive (and one or more partitions) with another node/instance.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:3AA6C951-0E13-4619-906F-BB0B0DB0C463@.microsoft.com...[vbcol=seagreen]
>I am not planning going to use and entire physical disk for the Quorum.
>I'm
> going to make a partition on a mirrored set (that will be a physical disk)
> that will be the Q: drive. The P: drive is just my way of keeping
> everything looking the same. My plan is to have only 2 cluster groups.
> Group 1 be will the Cluster IP, Cluster Name, the Physical Disk (E: Q

,
> the
> Physical Disk (F

, the MSDTC, and the first instance of SQL. Group 1
> will
> be owned by server1. Group 2 be will the Physical Disk (G: P

, the
> Physical Disk (H

, and the second instance of SQL. Group 2 will be owned
> by
> server2. Will this work ?
> "G Brander" wrote:
|||Good catch Rodney.
Clustering looks at physical disks (LUNs in SAN-speak). If you partition
the disk, clustering still sees the underlying physical disk.
Also, you don't want your Quorum disk to be part of your SQL Resource group.
That is a Low-Availability approach. Putting MSDCT in with a SQL instance
is an even worse approach. You need one disk for the Quorum, preferably one
disk for MSDTC (although it can be the same as the Quorum disk), and at
least one (preferably two or more) disks per SQL instance. These must be
physical disks or separate LUNs from a SAN device. Anything else will
compromise availability to the point that a cluster won't buy you any higher
availability.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:3AA6C951-0E13-4619-906F-BB0B0DB0C463@.microsoft.com...
> I am not planning going to use and entire physical disk for the Quorum.
I'm
> going to make a partition on a mirrored set (that will be a physical disk)
> that will be the Q: drive. The P: drive is just my way of keeping
> everything looking the same. My plan is to have only 2 cluster groups.
> Group 1 be will the Cluster IP, Cluster Name, the Physical Disk (E: Q

,
the
> Physical Disk (F

, the MSDTC, and the first instance of SQL. Group 1
will
> be owned by server1. Group 2 be will the Physical Disk (G: P

, the
> Physical Disk (H

, and the second instance of SQL. Group 2 will be owned
by[vbcol=seagreen]
> server2. Will this work ?
> "G Brander" wrote:
should[vbcol=seagreen]
13[vbcol=seagreen]
sets of[vbcol=seagreen]
logical[vbcol=seagreen]
will[vbcol=seagreen]
I'll[vbcol=seagreen]
G

[vbcol=seagreen]
P:[vbcol=seagreen]
for[vbcol=seagreen]
spilt[vbcol=seagreen]
|||Rodney and Geoff, I admit my terminology was bad. I 'AM' going to have 2
physical disks (LUNs in SAN-speak) per instance of SQL. One for databases
and one for transaction logs. I was trying to see if I could cheat and 'NOT'
use an entire disk for the quorum, but looks like that will not work (or not
work very well) in a multiple instance cluster. So it looks like I'll need
14, probably 15 disks on my shared storage to make this work.
So how about plan B:
Setup one physical disk (probably mirrored) for the quorum and the MSDTC.
Setup one physical disk (mirrored) for the transaction logs for each instance
of SQL. Setup one physical disk (Raid 5 or maybe 10) for the databases for
each instance of SQL. And if I can afford it a global hot spare. Better to
get it right in the planning stage than looking like an idiot trying to get a
bad design to work.
Thanks
"Geoff N. Hiten" wrote:

> Good catch Rodney.
> Clustering looks at physical disks (LUNs in SAN-speak). If you partition
> the disk, clustering still sees the underlying physical disk.
> Also, you don't want your Quorum disk to be part of your SQL Resource group.
> That is a Low-Availability approach. Putting MSDCT in with a SQL instance
> is an even worse approach. You need one disk for the Quorum, preferably one
> disk for MSDTC (although it can be the same as the Quorum disk), and at
> least one (preferably two or more) disks per SQL instance. These must be
> physical disks or separate LUNs from a SAN device. Anything else will
> compromise availability to the point that a cluster won't buy you any higher
> availability.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Wayne" <Wayne@.discussions.microsoft.com> wrote in message
> news:3AA6C951-0E13-4619-906F-BB0B0DB0C463@.microsoft.com...
> I'm
> the
> will
> by
> should
> 13
> sets of
> logical
> will
> I'll
> G

> P:
> for
> spilt
>
>
|||I like plan B, and not just cause I fully understand it. Question, are your
SQL applications going to use MSDTC? If so, for performance reasons you may
want to have a mirror just for the log and extend the default log size.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:4B6F25F5-FB78-4023-AE65-6F4335DA4940@.microsoft.com...[vbcol=seagreen]
> Rodney and Geoff, I admit my terminology was bad. I 'AM' going to have 2
> physical disks (LUNs in SAN-speak) per instance of SQL. One for databases
> and one for transaction logs. I was trying to see if I could cheat and
> 'NOT'
> use an entire disk for the quorum, but looks like that will not work (or
> not
> work very well) in a multiple instance cluster. So it looks like I'll need
> 14, probably 15 disks on my shared storage to make this work.
> So how about plan B:
> Setup one physical disk (probably mirrored) for the quorum and the MSDTC.
> Setup one physical disk (mirrored) for the transaction logs for each
> instance
> of SQL. Setup one physical disk (Raid 5 or maybe 10) for the databases for
> each instance of SQL. And if I can afford it a global hot spare. Better
> to
> get it right in the planning stage than looking like an idiot trying to
> get a
> bad design to work.
> Thanks
> "Geoff N. Hiten" wrote:
|||Rodney, yes I plan on the SQL applications using the MSDTC. Where can I find
info on how to extend the default log size.
Thanks for the heads up.
"Rodney R. Fournier [MVP]" wrote:

> I like plan B, and not just cause I fully understand it. Question, are your
> SQL applications going to use MSDTC? If so, for performance reasons you may
> want to have a mirror just for the log and extend the default log size.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "Wayne" <Wayne@.discussions.microsoft.com> wrote in message
> news:4B6F25F5-FB78-4023-AE65-6F4335DA4940@.microsoft.com...
>
>
|||First follow http://support.microsoft.com/kb/817064 on each machine BEFORE
you install the cluster service.
Then on each node - open component services - Computers - My Computer -
Properties - MSDTC tab - Capacity = 12 or 16 or anything larger then 4 MB,
close it out. Make both machines the same size log.
Install Microsoft clustering.
Finally follow
http://support.microsoft.com/default...b;en-us;301600
Then Install SQL in the Cluster.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:AD40F458-65B9-45DC-8CA0-5031975CD3DD@.microsoft.com...[vbcol=seagreen]
> Rodney, yes I plan on the SQL applications using the MSDTC. Where can I
> find
> info on how to extend the default log size.
> Thanks for the heads up.
> "Rodney R. Fournier [MVP]" wrote:

Cluster question

My employer is asking to do an Active / Active SQL 2000 cluster to utilize
both servers. Problem is, I don't think SQL 2000 supports an Active/Active
solution because both would need access to the disk which isn't possible...
The only time an Active / Active cluster can work is when you have multiple
instances which allows Node A to use the disk for one instance and Node B to
utilize the disk for a different named instance.
Can someone clarify for me? Thanks.
Each instance of SQL Server will require its own disk resources. Thus, if
SQL1 owns E: then SQL2 cannot have an E: drive. SQL 2000 supports up to 16
instances within the same cluster. We don't use the term Active/Active any
more.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"burt_king" <burt_king@.yahoo.com> wrote in message
news:C926C991-9D66-4531-A5FF-912AEC097165@.microsoft.com...
My employer is asking to do an Active / Active SQL 2000 cluster to utilize
both servers. Problem is, I don't think SQL 2000 supports an Active/Active
solution because both would need access to the disk which isn't possible...
The only time an Active / Active cluster can work is when you have multiple
instances which allows Node A to use the disk for one instance and Node B to
utilize the disk for a different named instance.
Can someone clarify for me? Thanks.
|||"when you have multiple instances which allows Node A to use the disk for
one instance and Node B to utilize the disk for a different named instance."
--> correct
what you might want to look into is :
scalable shared databases, where multiple SQL 2005 (enterprise)
servers are accessing a read-only volume.
there are many restrictions to this
Please see ; http://support.microsoft.com/default.aspx?scid=kb;en-us;910378
for more info on this
"burt_king" <burt_king@.yahoo.com> wrote in message
news:C926C991-9D66-4531-A5FF-912AEC097165@.microsoft.com...
> My employer is asking to do an Active / Active SQL 2000 cluster to utilize
> both servers. Problem is, I don't think SQL 2000 supports an
Active/Active
> solution because both would need access to the disk which isn't
possible...
> The only time an Active / Active cluster can work is when you have
multiple
> instances which allows Node A to use the disk for one instance and Node B
to
> utilize the disk for a different named instance.
> Can someone clarify for me? Thanks.
> --
|||Each instance requires it own dedicated disk resources that cannot be
shared, and databases CANNOT be shared between instances. Those dedicated
resources cannot have the same drive assignment.
Instance A has SAN drive G, H,
Instance B has SAN drives M, N
Upon failover of Instance A, Physical computer B now runs both Instance B
AND Instance A, and Drives G, H, M, N.
This has been a very simplistic example, but hopefully you now understand a
bit better.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"burt_king" <burt_king@.yahoo.com> wrote in message
news:C926C991-9D66-4531-A5FF-912AEC097165@.microsoft.com...
> My employer is asking to do an Active / Active SQL 2000 cluster to utilize
> both servers. Problem is, I don't think SQL 2000 supports an
> Active/Active
> solution because both would need access to the disk which isn't
> possible...
> The only time an Active / Active cluster can work is when you have
> multiple
> instances which allows Node A to use the disk for one instance and Node B
> to
> utilize the disk for a different named instance.
> Can someone clarify for me? Thanks.
> --
|||Roland, very clear, thank you.
Now, slightly off but still for clustering, how do I administer the
traditional sp_configure settings? I'm speaking of memory for myself but
that raised the larger question, How do I administer the server? I'd assume
through the virtual server name since on the back end the Master and MSDB are
really being written to by the Active node... Am I correct? If I want to
give the server more or less memory, can I do so through the Enterprise
manager interface?
"Arnie Rowland" wrote:

> Each instance requires it own dedicated disk resources that cannot be
> shared, and databases CANNOT be shared between instances. Those dedicated
> resources cannot have the same drive assignment.
> Instance A has SAN drive G, H,
> Instance B has SAN drives M, N
> Upon failover of Instance A, Physical computer B now runs both Instance B
> AND Instance A, and Drives G, H, M, N.
> This has been a very simplistic example, but hopefully you now understand a
> bit better.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> "burt_king" <burt_king@.yahoo.com> wrote in message
> news:C926C991-9D66-4531-A5FF-912AEC097165@.microsoft.com...
>
>
|||Each server in the cluster is still an independent server; configuration is
done the same way as a stand alone server. However, you need to configure
with the understanding that both instances MAY have to operate on the same
box.
So if the box has 8 GB of memory, then you don't assign all 8 GBs to the
default instance on that box. If you did, when there is a failover, there
will be no memory for the 'visiting' instance.
If InstanceA has a minimum memory of 4 GB, and Instance B also has a minimum
memory allocation of 4 GB, and the server only has 8 GB, then upon failover,
the 'visiting' instance will be memory starved and will most like not come
online. (You have to make sure that there is enough memory for the OS as
well.)
Let's say both boxes have 8 GB. InstanceA contains large, heavily used
databases, so it is allocated 5 GB as a maximum, and InstanceB is less
demanding, so it is allocated 2 GB as a maximum. Upon failover, the two
instances require 7 GB, and leave 1 GB for the OS and memory management.
'Bean counters' will complain since it appears that InstanceB only needs 3
GB for the server, and adding an addition 5 GB is seen as a waste. However,
you have to consider the cost of the 'unused' 5 GB on InstanceB as insurance
payments for future availability. (And the same for the 'unused' 2 GB on
InstanceA.)
Thing to remember with configuration, is that upon failover, all instances
must be able to work (albeit perhaps not performing quite as well) on one
box. Most Server wide configuration settings 'should' be the same. Memory is
the most common setting that is different between Instances.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"burt_king" <burt_king@.yahoo.com> wrote in message
news:91DFAA5E-B271-4CA4-B6FE-727CA857BC39@.microsoft.com...[vbcol=seagreen]
> Roland, very clear, thank you.
> Now, slightly off but still for clustering, how do I administer the
> traditional sp_configure settings? I'm speaking of memory for myself but
> that raised the larger question, How do I administer the server? I'd
> assume
> through the virtual server name since on the back end the Master and MSDB
> are
> really being written to by the Active node... Am I correct? If I want to
> give the server more or less memory, can I do so through the Enterprise
> manager interface?
>
> "Arnie Rowland" wrote:

Cluster problems?

Every now and then (about once a week) our SQL server cluster
(active/passive) becomes unresponsive, and the following events are logged:
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Timeout expired
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] OnlineThread: QP is not online.
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
SQL server errorlog contains these errors:
2005-08-07 07:52:16 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:16 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:52:19 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:19 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:47 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:47 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:54:27 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:55:05 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:55:05 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [382] Logon to server '(local)' failed (JobManager)
During this time, connections are terminated and SQL server does not allow
legitimate accounts to log in. it last for a couple of minutes. The server is
clearly not overloaded, and it doesn't have any specific jobs or anything to
do at this time. I would like to exclude network problems too, because the
machine is otherwise responsive and fine. it's just the SQL server service
that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL 2000
Ent.
thanks
> that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL
2000
> Ent.
I forgot one thing, Win2k3 has SP1, and SQL server has SP3 applied.
- Gabor
sql sql

Cluster problems?

Every now and then (about once a week) our SQL server cluster
(active/passive) becomes unresponsive, and the following events are logged:
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Timeout expired
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] OnlineThread: QP is not online.
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
SQL server errorlog contains these errors:
2005-08-07 07:52:16 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:16 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:52:19 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:52:19 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:53:47 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:53:47 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:54:27 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:54:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManager)
2005-08-07 07:55:05 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:55:05 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 11, General network error.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [382] Logon to server '(local)' failed (JobManager)
During this time, connections are terminated and SQL server does not allow
legitimate accounts to log in. it last for a couple of minutes. The server is
clearly not overloaded, and it doesn't have any specific jobs or anything to
do at this time. I would like to exclude network problems too, because the
machine is otherwise responsive and fine. it's just the SQL server service
that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL 2000
Ent.
thanks> that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL
2000
> Ent.
I forgot one thing, Win2k3 has SP1, and SQL server has SP3 applied.
- Gabor

Cluster problems?

Every now and then (about once a week) our SQL server cluster
(active/passive) becomes unresponsive, and the following events are logged:
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Timeout expired
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
Type: Error
Event ID: 17052
Source: MSSQLSERVER
User: N/A
Generated: 8/7/2005 7:58:33 AM
Category: Failover
Message: [sqsrvres] OnlineThread: QP is not online.
Data: 9C 42 00 40 01 00 00 00 0B 00 00 00 44 00 41 00 54 00 41 00 42 00 41
00 53 00 45 00 30 00 31 00 00 00 00 00 00 00
SQL server errorlog contains these errors:
2005-08-07 07:52:16 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:52:16 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:52:19 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:52:19 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:53:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:53:27 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:53:47 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:53:47 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:54:27 - ! [298] SQLServer Error: 11, General network error
.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:54:27 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:54:27 - ! [165] ODBC Error: 0, Timeout expired [SQLSTA
TE HYT00]
2005-08-07 07:54:27 - ! [382] Logon to server '(local)' failed (JobManag
er)
2005-08-07 07:55:05 - ! [298] SQLServer Error: 11, General network error
.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:55:05 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 11, General network error
.
Check your network documentation. [SQLSTATE 08001]
2005-08-07 07:57:03 - ! [298] SQLServer Error: 65534, ConnectionOpen
(PreLoginHandshake()). [SQLSTATE 01000]
2005-08-07 07:57:03 - ! [382] Logon to server '(local)' failed (JobManag
er)
During this time, connections are terminated and SQL server does not allow
legitimate accounts to log in. it last for a couple of minutes. The server i
s
clearly not overloaded, and it doesn't have any specific jobs or anything to
do at this time. I would like to exclude network problems too, because the
machine is otherwise responsive and fine. it's just the SQL server service
that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL 200
0
Ent.
thanks> that seems to "take a nap". Has anyone seen this before? Win2k3 Ent, SQL
2000
> Ent.
I forgot one thing, Win2k3 has SP1, and SQL server has SP3 applied.
- Gabor

Cluster problem

An installation of sql2k5 sp2 to one node of a three node
active/active/active cluster has failed. It cannot proceed beyond the
beginning of the sql2k5 sp2 installation. It fails because it can't install
sqlsupport.msi. It seems to want to put the files in the wrong place.
We can't get the sp to install after a lot of trying and want to 1) fail the
instance the node normally hosts to a partner 2) disconnect the node from
the cluster heartbeat and public networks and 3) run a SQL de-install of the
problematic instance on the disconnected node to clear off SQL and then
reinstall it, bringing it up to SQL2K5 SP2 4) reconnect the node to the
network and 5) fail the instance on the partner node back.
I don't think this will work because during the de-install the add/remove
routine will ask to remove code from san drives it can't find because
they're no longer accessible to it, since it has been disconnected from the
network and SAN. I think a manual removal may be all that can work.
After the node has been reconnected, and SQL installation commenced I will
be asked to create a new instance, a local or clustered instance, neither of
which I want. Can I avoid this by running SQL Setup on the reconnected node
and asking to manage a virtual instance instead of installing a fresh one?
Will I need, at some point, to evict the disconnected node from the cluster?
I know on a previous occasion, I couldn't get the node, once evicted, to
rejoin. Once it's out, it's out for good, isn't it?
"Robert Hindla" <rhindla@.panix.com> wrote in message
news:C38733A0.1BA20%rhindla@.panix.com...
> An installation of sql2k5 sp2 to one node of a three node
> active/active/active cluster has failed. It cannot proceed beyond the
> beginning of the sql2k5 sp2 installation. It fails because it can't
> install
> sqlsupport.msi. It seems to want to put the files in the wrong place.
Are you installing the first instance or the second instance?
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Jan 18 - 31 in Denver
Mar 10- 13 in Denver
|||The virtual SQL instance I'm proposing to de-install and then re-configure
using the setup program in 'manage' mode (instead of 'setup' mode) is one of
two named instances. It isn't the default instance.
The default instance functions satisfactorily, but only after a lot of
backing and filling, such as returning the native client to RTM level and
then re-running the installation of the client tools.
On 12/17/07 1:25 PM, in article
351AA24D-A3AA-4812-9682-F36BAFB1BC14@.microsoft.com, "Russ Kaufmann [MVP]"
<russ@.clusterhelp.com> wrote:

> "Robert Hindla" <rhindla@.panix.com> wrote in message
> news:C38733A0.1BA20%rhindla@.panix.com...
> Are you installing the first instance or the second instance?
|||"Robert Hindla" <rhindla@.panix.com> wrote in message
news:C38DA216.1BACB%rhindla@.panix.com...
> The virtual SQL instance I'm proposing to de-install and then re-configure
> using the setup program in 'manage' mode (instead of 'setup' mode) is one
> of
> two named instances. It isn't the default instance.
> The default instance functions satisfactorily, but only after a lot of
> backing and filling, such as returning the native client to RTM level and
> then re-running the installation of the client tools.
So, it sounds to me like things are seriously hosed (to use a highly
technical term) with your cluster. I would consider a complete rebuild over
the holidays if it were me.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Jan 18 - 31 in Denver
Mar 10- 13 in Denver

CLuster problem

Hi,
I realized an active/passive Windows Cluster from two IBM xSeries346 with
Windows 2003 Enterprise Edition SP1 (patched..) and I use like a shared disk
an IBM EXP400 (certified..).
When Active server go down, passive server can't do automatically the
failover, the second server can't see shared disks..
any help?
thank's a lot
andrea
I can't tell you specifically what, but I recently heard of an issue where
teh drive letters for the shared droves were not "configured" correctly in
the SAN utilities.
Does the group go to the passive node and just sit there, or does it fail
back to the original active node? If on the Passive node, can you see the
drive in "My Computer"?
"Andrea Racca" wrote:

> Hi,
> I realized an active/passive Windows Cluster from two IBM xSeries346 with
> Windows 2003 Enterprise Edition SP1 (patched..) and I use like a shared disk
> an IBM EXP400 (certified..).
> When Active server go down, passive server can't do automatically the
> failover, the second server can't see shared disks..
> any help?
> thank's a lot
> andrea
>
>
sql sql

Sunday, March 25, 2012

Cluster name with multiple IP addresses?

Can multiple IP addresses be assigned to a cluster and/or virtual name?
I have a 2-node Active/Passive cluster on a switched (not routed) network.
Each node has 3 NICs, each on its own subnet;
a) public/client access - 192.168.10.0
b) private/cluster traffic - 10.0.0.0
c) data backup network - 192.168.20.0
The cluster name "SQLCLST" and the virtual machine name "SQLSVR" have been
defined with IP addresses on the public/client network.
My backup software is cluster aware but because the traffic is separated via
switched network, I need the cluster and/or virtual machine name to respond
to IP addresses on two different subnets. Is this possible? Did this make
sense? ;)
TIA
It is not an uncommon request, nor is it too difficult. Once you have the
NICs and networks defined in the cluser configuration, you run the SQL setup
wizard to add the networks to SQL Server. To use them effectively, look
into connection-specific suffixes. That way you can force traffic to a
particular network.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Structured Chaos" <jeffery_tyree@.yahoo.com> wrote in message
news:%23Y%23s8Mv0HHA.5380@.TK2MSFTNGP04.phx.gbl...
> Can multiple IP addresses be assigned to a cluster and/or virtual name?
> I have a 2-node Active/Passive cluster on a switched (not routed) network.
> Each node has 3 NICs, each on its own subnet;
> a) public/client access - 192.168.10.0
> b) private/cluster traffic - 10.0.0.0
> c) data backup network - 192.168.20.0
> The cluster name "SQLCLST" and the virtual machine name "SQLSVR" have been
> defined with IP addresses on the public/client network.
> My backup software is cluster aware but because the traffic is separated
> via switched network, I need the cluster and/or virtual machine name to
> respond to IP addresses on two different subnets. Is this possible? Did
> this make sense? ;)
> TIA
>
|||Thanks for the quick info. Apparently it is a little more difficult than
that, heheh
I did not see any dialog/screen that allowed for the addition of new
network - only to modify node membership.
I have a ticket opened with MS. They have escalated it stating that they
don't even know if SQL will support this configuration and are attempting to
duplicate it in their labs. The MS SQL Data Engine Team manager stated they
may even have to look at the code...
Should you happen to have any detailed steps on making this work, I'd
appreciate it and apparently MS would too! LOL
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OQYwDPx0HHA.1184@.TK2MSFTNGP04.phx.gbl...
> It is not an uncommon request, nor is it too difficult. Once you have the
> NICs and networks defined in the cluser configuration, you run the SQL
> setup wizard to add the networks to SQL Server. To use them effectively,
> look into connection-specific suffixes. That way you can force traffic to
> a particular network.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Structured Chaos" <jeffery_tyree@.yahoo.com> wrote in message
> news:%23Y%23s8Mv0HHA.5380@.TK2MSFTNGP04.phx.gbl...
>
|||OK, you are not trying to stack multiple IP addresses on a single NIC, you
are using a unique IP address for each NIC. That isn't a problem.
The problem comes from having the same DNS alias (network name) respond on
two different subnets. That is a networking issue, not a clustering issue.
I would use connection-specific domain suffixes to differentiate the
networks. Also, I would use DNS SRV records to abstract the names. I.E.
MySQLCluster points to the IP and port of the normal public NIC.
MySQLClusterBackup points to the IP and port on the backup LAN.
I have used this setup in the past and it works just fine.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Structured Chaos" <jeffery_tyree@.yahoo.com> wrote in message
news:Ooh45iT2HHA.2752@.TK2MSFTNGP06.phx.gbl...
> Thanks for the quick info. Apparently it is a little more difficult than
> that, heheh
> I did not see any dialog/screen that allowed for the addition of new
> network - only to modify node membership.
> I have a ticket opened with MS. They have escalated it stating that they
> don't even know if SQL will support this configuration and are attempting
> to duplicate it in their labs. The MS SQL Data Engine Team manager stated
> they may even have to look at the code...
> Should you happen to have any detailed steps on making this work, I'd
> appreciate it and apparently MS would too! LOL
>
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OQYwDPx0HHA.1184@.TK2MSFTNGP04.phx.gbl...
>

Cluster memory issue

I'm currently running 2 SQl Instance as an active/active
cluster.
Both servers are identical running windows 2000 Advance
server.
SQL Server Enterprise 2000 with settings exactly the same
on both servers,
8GB of memory, both servers are new builds, Windows sees
all the memory, boot.ini as /3gb /pae switches and SQL's
are awe configured.
Instance 1 running as default virtual server on node 1
Max Server memory 7406
SQL runs using 7.23GB of memory.
Instance 2 running as named instance of virtual server on
node 2
Max Server memory 7406
SQL runs using only 3.73 GB as max
How can I get node 2 to also use 7.23GB.
But I'm getting excessive paging so would use more memory
if it could get it.
First, you must use Performance monitor to get true memory settings. Task
manager will not report correct settings. If you are paging, you need to
back down on the max memory setting. I would recommend 6.5 GB for an 8GB
system as a starting point. You can adjust upwards until the system begins
to page then back down slightly. The server needs some memory for the OS
and some for non-sql apps (like the login console). Also, you really should
run these systems at about 3.5GB each so in case one fails over, you can
hold both on the same server. Right now, you may not be able to
successfully fail over since neither system has enough free memory to start
the other instance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Ray" <anonymous@.discussions.microsoft.com> wrote in message
news:27e1401c46401$a942d1d0$a501280a@.phx.gbl...
> I'm currently running 2 SQl Instance as an active/active
> cluster.
> Both servers are identical running windows 2000 Advance
> server.
> SQL Server Enterprise 2000 with settings exactly the same
> on both servers,
> 8GB of memory, both servers are new builds, Windows sees
> all the memory, boot.ini as /3gb /pae switches and SQL's
> are awe configured.
> Instance 1 running as default virtual server on node 1
> Max Server memory 7406
> SQL runs using 7.23GB of memory.
> Instance 2 running as named instance of virtual server on
> node 2
> Max Server memory 7406
> SQL runs using only 3.73 GB as max
> How can I get node 2 to also use 7.23GB.
> But I'm getting excessive paging so would use more memory
> if it could get it.
>
|||I agree with Geoff. The main reason that you are using SQL Server Failover Clustering is that High Availability is your highest priority. So, you do not want to compromise that. In this scenario, it is recommended
that each instance of SQL Server on either node use upto 3.5GB of memory.
Here is an example from " Microsoft SQL Server 2000 High Availability (MS Press) ISBN 0-7356-1920-4 " that will make this easier to understand.
Consider this example: you have a two-node cluster with three SQL Server instances. Instance 1, which currently resides on Node 1, has 7 GB of memory configured using AWE. Node 2 houses Instance 2, which
has 5 GB of memory allocated with AWE, and one instance that is not using any advanced options and is currently using 1.5 GB of memory. Each node individually has a total of 8 GB of physical memory. A
problem occurs on Node 1, causing a failover. The instance tries to restart on Node 2, but it cannot. You now have a failed set of SQL Server resources that cannot come online, causing an availability problem.
Why? Well, to use AWE, you need to guarantee that the memory you told SQL Server to use will be there. A failover is basically a stop and start on another server. In this case, you were already using 6.5 of the
available 8 GB of memory. 6.5 + 7 does not equal 8, and it does not matter how big your page file is. Your instance will not grab the memory for AWE. It might, however, start up, but it will only grab the amount of
memory that it can up to 2 GB . Now you are risking memory starvation of the operating system, and this can affect all instances.
So how do you prevent this? By planning, these are the types of scenarios you need to play out in your head when proposing the number of instances on a cluster. Your management might see a two-node cluster
and say, "Hey, why is this second server doing nothing? Get something on there!", leaving you in the state of the previous example. The way you can balance memory in this case would be to give two
instances that need a fixed amount of memory 3 GB each and let the other one be dynamic (or set it to 1 GB or 1.5 GB to allow room for the operating system).If you cannot live with this, you will need another cluster
or set of servers to handle this workload. The recommendation was basically to halve the memory,which might lead some to believe that you are wasting resources, but again, is performance or availability your
goal? By definition, if you are reading this book and implementing things like a cluster, you are probably saying that availability is your highest priority. If you never have to failover and you left the instances at 7
GB, 5 GB, and dynamic, things would work great. But once a failover happened, all bets would be off.
Additional Information
=======================
-- In your case, you do not need to use /3GB. AWE and /PAE should be sufficient.
-- When starting with both the /PAE and the /3GB switches, the system may not start
http://support.microsoft.com/?kbid=817566
HOW TO: Configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/?kbid=274750
Microsoft Whitepaper - SQL Server 2000 Failover Clustering
http://www.microsoft.com/SQL/techinf...vercluster.asp
Microsoft SQL Server 2000 High Availability Series
http://www.microsoft.com/technet/pro...y/sqlhalp.mspx
Microsoft Webcasts
Introduction to Microsoft SQL Server 2000 Clustering
http://support.microsoft.com/default...lurb051001.asp
Microsoft SQL Server 2000 Virtual Server: Things You Should Know
http://support.microsoft.com/default...lurb032602.asp
Microsoft SQL Server 2000 Virtual Server Basic Setup, Maintenance, and Service Pack http://support.microsoft.com/default...lurb061002.asp
Microsoft SQL Server 2000 Failover Clustering Disaster Recovery Procedures
http://support.microsoft.com/default...lurb101802.asp
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
Q243218 INF: Installation Order for SQL 2000 Enterprise Edition
http://support.microsoft.com/?kbid=243218
Q260758 - INF: Frequently Asked Questions - SQL Server 2000 - Failover Clustering
http://support.microsoft.com/?kbid=260758
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Cluster licencing

I have a question regarding licencing on a sql server active/passive cluster. If we have more than 1 instance of the sql server do we have to have to buy another licence for each additional instance?
A Single-instance cluster requires licensing for a single host node.
Multi-instance clustering requires licensing for all host nodes. I am
assuming you are licensing per-processor.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Robert" <anonymous@.discussions.microsoft.com> wrote in message
news:B92B51F4-2C4F-4A66-B53D-1DCAE282D8D8@.microsoft.com...
> I have a question regarding licencing on a sql server active/passive
cluster. If we have more than 1 instance of the sql server do we have to
have to buy another licence for each additional instance?
|||So is it true to say.
Server based license
If you have Active/Passive, and you have 4 instances, each in it's own cluster group, but on the same two nodes, you have to purchase 4 sets licenses. One for each instance.
I thought (from reading the 6.5 and 7.0 documentation) that you licensed the node, and in a 2 node cluster, regardless of active/passive or active/active you'd need to purchase 2 licenses (+ relevant CALs).
However, according to a Microsoft consultance (who's gone away to confirm) you only need to buy the license for the active node.
Sorry if this adds to the confusion.
|||Since you are clustering, you need Enterprise Edition. EE license allows
multiple instances on a host computer for the same processor license. The
exception for a licensing is when you are in single-instance cluster. Then
you only need to license one hose node's worth of processors. If you have
more than one instance, you must license ALL processors in the cluster.
Again, check with your local MS rep to get the exact wording.
(If you think this is confusing, you should try to figure out MSDE and
client tools licensing.)
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Beverley" <Bev.Brindle@.barclays.co.uk> wrote in message
news:8C12096A-8761-4589-82A3-C8B1E360E2B2@.microsoft.com...
> So is it true to say.
> Server based license
> If you have Active/Passive, and you have 4 instances, each in it's own
cluster group, but on the same two nodes, you have to purchase 4 sets
licenses. One for each instance.
> I thought (from reading the 6.5 and 7.0 documentation) that you licensed
the node, and in a 2 node cluster, regardless of active/passive or
active/active you'd need to purchase 2 licenses (+ relevant CALs).
> However, according to a Microsoft consultance (who's gone away to confirm)
you only need to buy the license for the active node.
> Sorry if this adds to the confusion.
|||Sorry to keep going on about this, but were putting strategic infrastructure in place, and I want to make sure that we are adequatley licensed.
So with clustering can you use EE Server License, or is Processor License compulsory.
And if EE Server Based is OK, does it apply to each instance (e.g. Server License x No Instances)
Im differentiating between Server and Processor on the basis that if your using Server you have to purchase CALs, but not if your using Processor.
We've purchased 60,000 CALs, so were going to use Server for all SQL unless its userbase is WWW based. What would we need to do for clustered SQL? We're intending a maxumim of 4 instances per cluster, over a 2 node active / passive cluster.
|||Again, the answer is "It Depends". You can use EE Server based with either
device or user CALs. EE allows multiple instances on a single host with one
license. The 'single-instance cluster exception' is actually a grant to use
the licenses on a failover node at no additional charge.
Here is an excerpt from the SQL licensing FAQ that seems to apply:
--snip--
Q. How does licensing work for computers that run SQL Server 2000
Enterprise Edition in failover scenarios?
A. Failover support, where servers are clustered together and set to
pick up each others' processing duties if one computer should fail, is
available only in SQL Server 2000 Enterprise Edition, just as it was with
SQL Server 7.0. Failover support can be configured in one of two ways:
a.. Active/active. In the active/active configuration, all servers
in the cluster regularly process information, but one or more take on the
workload of a failed server.
b.. Active/passive. In the active/passive configuration, one or more
computers in the cluster do not regularly process information but rather
passively wait to pick up the workload when an active server fails. All
active servers in a cluster must be fully licensed, according to either the
Per Processor licensing model or the Server/CAL licensing model. However, if
a server is strictly passive, working only while an active server has
failed, no additional licenses are needed for that passive server. The only
exception to this rule is if the cluster is licensed using Processor
licenses and the number of processors on the passive server exceeds the
number of processors on the active server. In these cases, additional
Processor licenses must be purchased for the additional processors on the
passive server.
--snip--
You can read the entire FAQ here:
http://www.microsoft.com/sql/howtobuy/faq.asp
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Beverley" <Bev.Brindle@.barclays.co.uk> wrote in message
news:AA19071B-9CBD-4B06-97A6-3B692301BF21@.microsoft.com...
> Sorry to keep going on about this, but were putting strategic
infrastructure in place, and I want to make sure that we are adequatley
licensed.
> So with clustering can you use EE Server License, or is Processor License
compulsory.
> And if EE Server Based is OK, does it apply to each instance (e.g. Server
License x No Instances)
> Im differentiating between Server and Processor on the basis that if your
using Server you have to purchase CALs, but not if your using Processor.
> We've purchased 60,000 CALs, so were going to use Server for all SQL
unless its userbase is WWW based. What would we need to do for clustered
SQL? We're intending a maxumim of 4 instances per cluster, over a 2 node
active / passive cluster.
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Thanks for the clarity

Cluster Lan Interface

We have a SQL Fail-Over Cluster with on Lan Interface and One Heartbeat
Interface. The Lan Interface (NIC) on our active node went down so our
clients could not access the server. Since the services and the Heartbeatr
interface did not go down the passive node did not failover and take control
of the Cluster automatically. We had to force the passive cluster to
failover. Is there anyway we can prevent this from happening in the future ?
Hi
Have you had a look at
http://support.microsoft.com/default...;en-us;242600?
If you have Media Sense Disabled, the cluster will not fail over.
Regards
Mike
"ejcs@.noemail.nospam.com" wrote:

> We have a SQL Fail-Over Cluster with on Lan Interface and One Heartbeat
> Interface. The Lan Interface (NIC) on our active node went down so our
> clients could not access the server. Since the services and the Heartbeatr
> interface did not go down the passive node did not failover and take control
> of the Cluster automatically. We had to force the passive cluster to
> failover. Is there anyway we can prevent this from happening in the future ?
|||Hi,
I wanted to post a quick note to see if you would like additional
assistance or information regarding Mike's suggestions on this particular
issue. Have you tried the method described in KB:Q242600, does this resolve
your problem?
Please feel free to let me know if there is anything more I could do to
help on this issue and we appreciate your patience and look forward to
hearing from you!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I thought I would post this here in case somebody else has this problem. Incidentally, the link above to the KB article doesn't work: here it is again:
http://support.microsoft.com/default...b;en-us;242600
A common expectation of a virtual SQL running on a MS cluster is that link failure on the active node NIC will result in a failover.
Examples: loose cable, kicked cable, failed switch or switch module.
However, this will not cause a failover to the passive node
"Simply removing the network cable from the client network adapter does not constitute an adapter failure."
http://support.microsoft.com/kb/176320
I'm currently exploring a different issue for a client which if I find a solution for I will post here.
Scenario: 2 cluster active/passive MS cluster running SQL 2000 Enterprise. Public NICS are mixed mode, Private NIC is internal heartbeat only.
Symptons:
- unplugging public NIC cable from passive node will cause interface to dissapear from Cluster Admin
- unplugging public NIC cable from active node will cause both public NICs to become unavailable in Cluster Admin
- unplugging BOTH public NICs will cause public NIC of active to RE-APPEAR and be normal!
Anyway, I'll post more if I find a solution...|||Erratim: sorry the link from the second poster does work... didn't realise it was truncating the display.
Also, when both cables are pulled from the public NICs the status is unreachable, not unavailable

|||As a conclusion to this post, my issue related to the DisableDHCPMediaSense in the Windows Registry.
The active node had this set. Nobody set this value, so it seems to have been set by the system at some point.
Check MS KB on this issue if you have a cluster that won't failover when the network cable or switch goes down.

Thursday, March 29, 2012

Cluster SQL Active-Active

Cluster SQL 2000 errorlog problem

Cluster SQL 2000 errorlog problem

Tuesday, March 27, 2012

Cluster SQL 2000 errorlog problem

Cluster Set up Question

Cluster Server Planning.

Cluster question

Cluster problems?

Cluster problems?

Cluster problems?

Cluster problem

CLuster problem

Sunday, March 25, 2012

Cluster name with multiple IP addresses?

Cluster memory issue

Cluster licencing

Cluster Lan Interface

Clearing LOG Files

Blog Archive

About Me