Has anyone clustered SQL server 2000 using a NAS server (eg. Dell PowerVault
745N) as the shared storage? I know that SAN is recommended but costs are
vastly higher. Any reasons as to why it shouldn't be done would be helpful.
thanks - pete.
Hi
NAS is not fully supported. If you are going to build a cluster, make sure
that all the components are on the Windows Hardware Compatibility List for
Clustering. If not, don't expect support from Microsoft when things go bad.
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/
"Pete Waters" <petewaters008@.yahoo.com> wrote in message
news:e7$cBT9XFHA.3300@.TK2MSFTNGP10.phx.gbl...
> Has anyone clustered SQL server 2000 using a NAS server (eg. Dell
> PowerVault 745N) as the shared storage? I know that SAN is recommended but
> costs are vastly higher. Any reasons as to why it shouldn't be done would
> be helpful.
> thanks - pete.
>
|||Not being supported by Microsoft is a good enough reason for me to not try
it...
There are cheaper failover options that are less hardware strict, such as a
product called double-take (www.nsisoftware.com no affiliation...)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Pete Waters" <petewaters008@.yahoo.com> wrote in message
news:e7$cBT9XFHA.3300@.TK2MSFTNGP10.phx.gbl...
> Has anyone clustered SQL server 2000 using a NAS server (eg. Dell
> PowerVault 745N) as the shared storage? I know that SAN is recommended but
> costs are vastly higher. Any reasons as to why it shouldn't be done would
> be helpful.
> thanks - pete.
>
|||Hi Mike,
Thanks for the response. Whilst I appreciate that clustering with NAS is not
supported by Microsoft, I'm interested to find out if people are actually
doing it. If they are and it seems to be reliable enough then i'd imagine it
would be worth the cost saving.
thanks - pete.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OQXq%23c9XFHA.3464@.TK2MSFTNGP10.phx.gbl...
> Hi
> NAS is not fully supported. If you are going to build a cluster, make sure
> that all the components are on the Windows Hardware Compatibility List for
> Clustering. If not, don't expect support from Microsoft when things go
> bad.
> 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/
> "Pete Waters" <petewaters008@.yahoo.com> wrote in message
> news:e7$cBT9XFHA.3300@.TK2MSFTNGP10.phx.gbl...
>
|||Hi Kevin,
I'm looking for an Active/Active cluster solution - not a passive failover
one.
thanks - pete.
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:eBgCxe9XFHA.584@.TK2MSFTNGP15.phx.gbl...
> Not being supported by Microsoft is a good enough reason for me to not try
> it...
> There are cheaper failover options that are less hardware strict, such as
> a product called double-take (www.nsisoftware.com no affiliation...)
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> www.experts-exchange.com - experts compete for points to answer your
> questions
>
> "Pete Waters" <petewaters008@.yahoo.com> wrote in message
> news:e7$cBT9XFHA.3300@.TK2MSFTNGP10.phx.gbl...
>
|||Basic Question...what is more important to you? Data or Price?
If you don't mind loosing data in a supposedly "high availability" scenario,
then do it the cheap way.
Is your network and switches as reliable as 99.999%? If not, when they fail,
and you end up with data corruption.
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/
"Pete Waters" <petewaters008@.yahoo.com> wrote in message
news:u6trGh9XFHA.3620@.TK2MSFTNGP09.phx.gbl...
> Hi Mike,
> Thanks for the response. Whilst I appreciate that clustering with NAS is
> not supported by Microsoft, I'm interested to find out if people are
> actually doing it. If they are and it seems to be reliable enough then i'd
> imagine it would be worth the cost saving.
> thanks - pete.
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:OQXq%23c9XFHA.3464@.TK2MSFTNGP10.phx.gbl...
>
|||The internal network and switches are certainly 99.999% reliable (or at
least have been over the last year!). I'm more interested in peoples
practical experiences rather than the obvious value of data argument. I see
that Microsoft are beginning to support iSCSI - any experience with that?
thanks - pete.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uSShGp9XFHA.1240@.TK2MSFTNGP14.phx.gbl...
> Basic Question...what is more important to you? Data or Price?
> If you don't mind loosing data in a supposedly "high availability"
> scenario, then do it the cheap way.
> Is your network and switches as reliable as 99.999%? If not, when they
> fail, and you end up with data corruption.
> 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/
> "Pete Waters" <petewaters008@.yahoo.com> wrote in message
> news:u6trGh9XFHA.3620@.TK2MSFTNGP09.phx.gbl...
>
|||Well, I've been at 3 customers who used non-HCL equipment, 2 of them used a
NAS. Well, they all had one option, revert to yesterday's good backup. One
was an investment bank that lost about US$ 50 million due to the failure.
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/
"Pete Waters" <petewaters008@.yahoo.com> wrote in message
news:OjS0X39XFHA.3876@.TK2MSFTNGP10.phx.gbl...
> The internal network and switches are certainly 99.999% reliable (or at
> least have been over the last year!). I'm more interested in peoples
> practical experiences rather than the obvious value of data argument. I
> see that Microsoft are beginning to support iSCSI - any experience with
> that?
> thanks - pete.
>
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uSShGp9XFHA.1240@.TK2MSFTNGP14.phx.gbl...
>
|||Hi Mike,
Ah - that's not good! That's the kind of info i'm after - real world cases -
thanks. Have you had any experience with using iSCSI in these setups?
pete.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23M0e0C%23XFHA.3320@.TK2MSFTNGP12.phx.gbl...
> Well, I've been at 3 customers who used non-HCL equipment, 2 of them used
> a NAS. Well, they all had one option, revert to yesterday's good backup.
> One was an investment bank that lost about US$ 50 million due to the
> failure.
> 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/
> "Pete Waters" <petewaters008@.yahoo.com> wrote in message
> news:OjS0X39XFHA.3876@.TK2MSFTNGP10.phx.gbl...
>
|||Hi
No. Not iSCSI. After the IT Directors got a good beating by the
shareholders, they all went SAN.
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/
"Pete Waters" <petewaters008@.yahoo.com> wrote in message
news:OrxoIL%23XFHA.2756@.tk2msftngp13.phx.gbl...
> Hi Mike,
> Ah - that's not good! That's the kind of info i'm after - real world
> cases - thanks. Have you had any experience with using iSCSI in these
> setups?
> pete.
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23M0e0C%23XFHA.3320@.TK2MSFTNGP12.phx.gbl...
>
Showing posts with label san. Show all posts
Showing posts with label san. Show all posts
Friday, February 24, 2012
Clustering Service not starting right away on One Node
I just set up a cluster attached to a SAN. I have had it where the cluster
service on one of the nodes doesn't start up right away. I have checked the
services to make sure that it is set to automatic which it is. Both nodes
are current with the latest patches and security updates. I'm a little
clueless as to why this is happening. Here is the real weird part after 1
minute the cluster service starts on the node that is giving me troubles.
The other node is perfectly fine.
Hi
If you do a fail-over using cluster admin, are there any resources (that SQL
server depends on) take a long to come online?
I have seen similar issues when the devices take long to come online due to
high SAN activity.
Does the SQL Server resource come online, but take a long time until it has
done it's recovery steps?
This can occur when the other node was de-porting it's devices and still had
IO pending. This results in not all pages being fluished to SAN, so SQL
Server has to do more recovery on the database start-up.
The best guage of how quickly a resource comes online is to look at cluster
admin during the failover.
Regards
Mike
Regards
Mike
"Thomas" wrote:
> I just set up a cluster attached to a SAN. I have had it where the cluster
> service on one of the nodes doesn't start up right away. I have checked the
> services to make sure that it is set to automatic which it is. Both nodes
> are current with the latest patches and security updates. I'm a little
> clueless as to why this is happening. Here is the real weird part after 1
> minute the cluster service starts on the node that is giving me troubles.
> The other node is perfectly fine.
|||We haven't installed SQL server yet. I should've posted that first. But I
know from passed installs that SQL does take some time to come online. The
SAN doesn't have much activity on it right now
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> If you do a fail-over using cluster admin, are there any resources (that SQL
> server depends on) take a long to come online?
> I have seen similar issues when the devices take long to come online due to
> high SAN activity.
> Does the SQL Server resource come online, but take a long time until it has
> done it's recovery steps?
> This can occur when the other node was de-porting it's devices and still had
> IO pending. This results in not all pages being fluished to SAN, so SQL
> Server has to do more recovery on the database start-up.
> The best guage of how quickly a resource comes online is to look at cluster
> admin during the failover.
> Regards
> Mike
> Regards
> Mike
> "Thomas" wrote:
|||Hi
Have a look in your event logs and check the time differences between when
Node A shuts down and Node B notices it and starts up. There will be at least
15 event messages during this process. Post the information here so that I
can compare it to our big clusters.
Regards
Mike
"Thomas" wrote:
[vbcol=seagreen]
> We haven't installed SQL server yet. I should've posted that first. But I
> know from passed installs that SQL does take some time to come online. The
> SAN doesn't have much activity on it right now
> "Mike Epprecht (SQL MVP)" wrote:
|||That may be somewhat normal on a simultaneous startup. The first node grabs
the quorum device and owns the cluster but isn't talking on the network yet.
The second node tries to get the device but times out. Eventually the
service comes online and talks to the other node and agrees on who is in
charge. This is especially prevalent on SCSI-based clusters.
Check the System and Application event logs on both systems to see if there
are any unusual startup errors. Also, check what happens when the second
node is rebooted. If the cluster service does come online quickly, it is
just a device contention issue. I try and avoid powering up more than one
cluster node at a time.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Thomas" <Thomas@.discussions.microsoft.com> wrote in message
news:AF61883D-AE50-4F3F-AD3F-3F07834A2B78@.microsoft.com...
> I just set up a cluster attached to a SAN. I have had it where the
cluster
> service on one of the nodes doesn't start up right away. I have checked
the
> services to make sure that it is set to automatic which it is. Both nodes
> are current with the latest patches and security updates. I'm a little
> clueless as to why this is happening. Here is the real weird part after 1
> minute the cluster service starts on the node that is giving me troubles.
> The other node is perfectly fine.
|||Node 2 which I haven't seen the problem with having ownership of the cluster.
When I reboot node 1 is when I see the problem of it taking 1 mintue to
start the cluster service.
"Geoff N. Hiten" wrote:
> That may be somewhat normal on a simultaneous startup. The first node grabs
> the quorum device and owns the cluster but isn't talking on the network yet.
> The second node tries to get the device but times out. Eventually the
> service comes online and talks to the other node and agrees on who is in
> charge. This is especially prevalent on SCSI-based clusters.
> Check the System and Application event logs on both systems to see if there
> are any unusual startup errors. Also, check what happens when the second
> node is rebooted. If the cluster service does come online quickly, it is
> just a device contention issue. I try and avoid powering up more than one
> cluster node at a time.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Thomas" <Thomas@.discussions.microsoft.com> wrote in message
> news:AF61883D-AE50-4F3F-AD3F-3F07834A2B78@.microsoft.com...
> cluster
> the
>
>
|||Node order is arbitrary in a cluster. We could use Node X and Node Y
instead of Node 1 and Node 2.
Try manually stopping and starting the cluster service on Node 1. If it
restarts quickly, then the problem likely is one of the services that the
cluster service depends on. Time service is a usual suspect for that, but
you will have to check the entire list. Again, the Application and System
event logs are your friends here.
Now is the time to deal with this issue, not after you load SQL and get this
baby into production.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Thomas" <Thomas@.discussions.microsoft.com> wrote in message
news:29B2402A-537B-4DCE-A137-FA200DD28872@.microsoft.com...
> Node 2 which I haven't seen the problem with having ownership of the
cluster.[vbcol=seagreen]
> When I reboot node 1 is when I see the problem of it taking 1 mintue to
> start the cluster service.
> "Geoff N. Hiten" wrote:
grabs[vbcol=seagreen]
yet.[vbcol=seagreen]
there[vbcol=seagreen]
second[vbcol=seagreen]
is[vbcol=seagreen]
one[vbcol=seagreen]
checked[vbcol=seagreen]
nodes[vbcol=seagreen]
little[vbcol=seagreen]
after 1[vbcol=seagreen]
troubles.[vbcol=seagreen]
service on one of the nodes doesn't start up right away. I have checked the
services to make sure that it is set to automatic which it is. Both nodes
are current with the latest patches and security updates. I'm a little
clueless as to why this is happening. Here is the real weird part after 1
minute the cluster service starts on the node that is giving me troubles.
The other node is perfectly fine.
Hi
If you do a fail-over using cluster admin, are there any resources (that SQL
server depends on) take a long to come online?
I have seen similar issues when the devices take long to come online due to
high SAN activity.
Does the SQL Server resource come online, but take a long time until it has
done it's recovery steps?
This can occur when the other node was de-porting it's devices and still had
IO pending. This results in not all pages being fluished to SAN, so SQL
Server has to do more recovery on the database start-up.
The best guage of how quickly a resource comes online is to look at cluster
admin during the failover.
Regards
Mike
Regards
Mike
"Thomas" wrote:
> I just set up a cluster attached to a SAN. I have had it where the cluster
> service on one of the nodes doesn't start up right away. I have checked the
> services to make sure that it is set to automatic which it is. Both nodes
> are current with the latest patches and security updates. I'm a little
> clueless as to why this is happening. Here is the real weird part after 1
> minute the cluster service starts on the node that is giving me troubles.
> The other node is perfectly fine.
|||We haven't installed SQL server yet. I should've posted that first. But I
know from passed installs that SQL does take some time to come online. The
SAN doesn't have much activity on it right now
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> If you do a fail-over using cluster admin, are there any resources (that SQL
> server depends on) take a long to come online?
> I have seen similar issues when the devices take long to come online due to
> high SAN activity.
> Does the SQL Server resource come online, but take a long time until it has
> done it's recovery steps?
> This can occur when the other node was de-porting it's devices and still had
> IO pending. This results in not all pages being fluished to SAN, so SQL
> Server has to do more recovery on the database start-up.
> The best guage of how quickly a resource comes online is to look at cluster
> admin during the failover.
> Regards
> Mike
> Regards
> Mike
> "Thomas" wrote:
|||Hi
Have a look in your event logs and check the time differences between when
Node A shuts down and Node B notices it and starts up. There will be at least
15 event messages during this process. Post the information here so that I
can compare it to our big clusters.
Regards
Mike
"Thomas" wrote:
[vbcol=seagreen]
> We haven't installed SQL server yet. I should've posted that first. But I
> know from passed installs that SQL does take some time to come online. The
> SAN doesn't have much activity on it right now
> "Mike Epprecht (SQL MVP)" wrote:
|||That may be somewhat normal on a simultaneous startup. The first node grabs
the quorum device and owns the cluster but isn't talking on the network yet.
The second node tries to get the device but times out. Eventually the
service comes online and talks to the other node and agrees on who is in
charge. This is especially prevalent on SCSI-based clusters.
Check the System and Application event logs on both systems to see if there
are any unusual startup errors. Also, check what happens when the second
node is rebooted. If the cluster service does come online quickly, it is
just a device contention issue. I try and avoid powering up more than one
cluster node at a time.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Thomas" <Thomas@.discussions.microsoft.com> wrote in message
news:AF61883D-AE50-4F3F-AD3F-3F07834A2B78@.microsoft.com...
> I just set up a cluster attached to a SAN. I have had it where the
cluster
> service on one of the nodes doesn't start up right away. I have checked
the
> services to make sure that it is set to automatic which it is. Both nodes
> are current with the latest patches and security updates. I'm a little
> clueless as to why this is happening. Here is the real weird part after 1
> minute the cluster service starts on the node that is giving me troubles.
> The other node is perfectly fine.
|||Node 2 which I haven't seen the problem with having ownership of the cluster.
When I reboot node 1 is when I see the problem of it taking 1 mintue to
start the cluster service.
"Geoff N. Hiten" wrote:
> That may be somewhat normal on a simultaneous startup. The first node grabs
> the quorum device and owns the cluster but isn't talking on the network yet.
> The second node tries to get the device but times out. Eventually the
> service comes online and talks to the other node and agrees on who is in
> charge. This is especially prevalent on SCSI-based clusters.
> Check the System and Application event logs on both systems to see if there
> are any unusual startup errors. Also, check what happens when the second
> node is rebooted. If the cluster service does come online quickly, it is
> just a device contention issue. I try and avoid powering up more than one
> cluster node at a time.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Thomas" <Thomas@.discussions.microsoft.com> wrote in message
> news:AF61883D-AE50-4F3F-AD3F-3F07834A2B78@.microsoft.com...
> cluster
> the
>
>
|||Node order is arbitrary in a cluster. We could use Node X and Node Y
instead of Node 1 and Node 2.
Try manually stopping and starting the cluster service on Node 1. If it
restarts quickly, then the problem likely is one of the services that the
cluster service depends on. Time service is a usual suspect for that, but
you will have to check the entire list. Again, the Application and System
event logs are your friends here.
Now is the time to deal with this issue, not after you load SQL and get this
baby into production.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Thomas" <Thomas@.discussions.microsoft.com> wrote in message
news:29B2402A-537B-4DCE-A137-FA200DD28872@.microsoft.com...
> Node 2 which I haven't seen the problem with having ownership of the
cluster.[vbcol=seagreen]
> When I reboot node 1 is when I see the problem of it taking 1 mintue to
> start the cluster service.
> "Geoff N. Hiten" wrote:
grabs[vbcol=seagreen]
yet.[vbcol=seagreen]
there[vbcol=seagreen]
second[vbcol=seagreen]
is[vbcol=seagreen]
one[vbcol=seagreen]
checked[vbcol=seagreen]
nodes[vbcol=seagreen]
little[vbcol=seagreen]
after 1[vbcol=seagreen]
troubles.[vbcol=seagreen]
Clustering Question...
Say I have a current standalone SQL 2005 node that is SAN attached.
How can I get it clustered by adding a passive secondary node to it ? Can I
do so ? Or do I have to setup an entirely 2 new clustered set of servers and
move the database from the standalone server to it ?
I am trying to avoid buying 2 new servers and move the database across but
would like to just add another node to the existing standalone server and
get it clustered. If this is possible, how can I do it ?
Clusters have built from the ground up. You can't make it a cluster after
the install of SQL. Migrate to a new cluster, built from the ground up, that
is the best option.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Hassan" <Hassan@.hotmail.com> wrote in message
news:%23PKJjfJHHHA.3872@.TK2MSFTNGP06.phx.gbl...
> Say I have a current standalone SQL 2005 node that is SAN attached.
> How can I get it clustered by adding a passive secondary node to it ? Can
> I do so ? Or do I have to setup an entirely 2 new clustered set of servers
> and move the database from the standalone server to it ?
> I am trying to avoid buying 2 new servers and move the database across but
> would like to just add another node to the existing standalone server and
> get it clustered. If this is possible, how can I do it ?
>
>
|||Just to expand on what Rodney said, it is possible to create a cluster from
existing equipment, but it is neither desirable nor supported. The
potential disruption during the install and migration process will likely
cause some unplanned downtime, which defeats the entire purpose of a
cluster. It is best to start from a clean slate and migrate the data into
the new system.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:ODTKVxJHHHA.4804@.TK2MSFTNGP03.phx.gbl...
> Clusters have built from the ground up. You can't make it a cluster after
> the install of SQL. Migrate to a new cluster, built from the ground up,
> that is the best option.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://www.msmvps.com/clustering - Blog
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:%23PKJjfJHHHA.3872@.TK2MSFTNGP06.phx.gbl...
>
|||What you can do, however, if you are willing to live with a new network
name, is to build a new single-node cluster and install SQL Server on it.
After migrating the databases to this new host, you can then rebuild the
original server and then have it joined to the new cluster as a new cluster
node.
This last bit has very specific steps. Look them up in Books Online or
TechNet. I even think I have a detailed list lying around this new group
somewhere. If I find it, I'll shoot it out to you.
Anyway, this should save you the cost of buying a third server.
Sincerely,
Anthony Thomas
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23WajdlSHHHA.960@.TK2MSFTNGP04.phx.gbl...
> Just to expand on what Rodney said, it is possible to create a cluster
from[vbcol=seagreen]
> existing equipment, but it is neither desirable nor supported. The
> potential disruption during the install and migration process will likely
> cause some unplanned downtime, which defeats the entire purpose of a
> cluster. It is best to start from a clean slate and migrate the data into
> the new system.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:ODTKVxJHHHA.4804@.TK2MSFTNGP03.phx.gbl...
after[vbcol=seagreen]
Can[vbcol=seagreen]
server
>
How can I get it clustered by adding a passive secondary node to it ? Can I
do so ? Or do I have to setup an entirely 2 new clustered set of servers and
move the database from the standalone server to it ?
I am trying to avoid buying 2 new servers and move the database across but
would like to just add another node to the existing standalone server and
get it clustered. If this is possible, how can I do it ?
Clusters have built from the ground up. You can't make it a cluster after
the install of SQL. Migrate to a new cluster, built from the ground up, that
is the best option.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Hassan" <Hassan@.hotmail.com> wrote in message
news:%23PKJjfJHHHA.3872@.TK2MSFTNGP06.phx.gbl...
> Say I have a current standalone SQL 2005 node that is SAN attached.
> How can I get it clustered by adding a passive secondary node to it ? Can
> I do so ? Or do I have to setup an entirely 2 new clustered set of servers
> and move the database from the standalone server to it ?
> I am trying to avoid buying 2 new servers and move the database across but
> would like to just add another node to the existing standalone server and
> get it clustered. If this is possible, how can I do it ?
>
>
|||Just to expand on what Rodney said, it is possible to create a cluster from
existing equipment, but it is neither desirable nor supported. The
potential disruption during the install and migration process will likely
cause some unplanned downtime, which defeats the entire purpose of a
cluster. It is best to start from a clean slate and migrate the data into
the new system.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:ODTKVxJHHHA.4804@.TK2MSFTNGP03.phx.gbl...
> Clusters have built from the ground up. You can't make it a cluster after
> the install of SQL. Migrate to a new cluster, built from the ground up,
> that is the best option.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://www.msmvps.com/clustering - Blog
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:%23PKJjfJHHHA.3872@.TK2MSFTNGP06.phx.gbl...
>
|||What you can do, however, if you are willing to live with a new network
name, is to build a new single-node cluster and install SQL Server on it.
After migrating the databases to this new host, you can then rebuild the
original server and then have it joined to the new cluster as a new cluster
node.
This last bit has very specific steps. Look them up in Books Online or
TechNet. I even think I have a detailed list lying around this new group
somewhere. If I find it, I'll shoot it out to you.
Anyway, this should save you the cost of buying a third server.
Sincerely,
Anthony Thomas
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23WajdlSHHHA.960@.TK2MSFTNGP04.phx.gbl...
> Just to expand on what Rodney said, it is possible to create a cluster
from[vbcol=seagreen]
> existing equipment, but it is neither desirable nor supported. The
> potential disruption during the install and migration process will likely
> cause some unplanned downtime, which defeats the entire purpose of a
> cluster. It is best to start from a clean slate and migrate the data into
> the new system.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:ODTKVxJHHHA.4804@.TK2MSFTNGP03.phx.gbl...
after[vbcol=seagreen]
Can[vbcol=seagreen]
server
>
Sunday, February 19, 2012
Clustering Newbie - SAN Advice
Hi,
We are looking into implementing an Active:Passive SQL 2005 Cluster for a
reasonably large and important system (< 1Tb)
I'm not looking for advice re: particular brand etc., but on advice on type
/ type of connection to SAN that may be appropriate. The SQL 2005 instance(s)
will be x64.
Please, any wannabe MVPs do not provide sarcastic/useless answers just to up
your profile. To pre-empt some of these:-
Yes I have indexes on current database
Yes the queries have been tuned
Yes, I have detailed stats on usage, performance, but you do not need
these to answer the general thrust of the question
etc.
Now, I went through the Dell SQL configurator to see what they came up with
.... they suggested ￡50k would be a reasonable price ... maybe it is, maybe
it isn't. This had all manner fancy fibre connection things, disks at ￡1000
each, other buzzers and bells. I wonder if I really need all this?
Basic setup is 2 * servers (Windows 2003 R2, standard, x64), spec'd (each):-
1 * Quad-core CPU
2 * 15,000rpm disks (RAID 1) for O/S and SQL program files etc. (and
swap files)
8Gb RAM
Network cards, etc.
I would like, an external disk array to hold database drives (pretty
essential really for a cluster!), of roughly the following format (each
physical disk probably 146Gb capacity):-
2 * 15,000 rpm RAID 1 (tempdb)
2 * 15,000 rpm RAID 1 (transaction logs)
At least 6 (probably more) * 15,000 rpm Stripped and Mirrored for main
database files
What sort of storage kit/spec. (fibre? not fibre? etc. ?) should I be
looking for to support the cluster? ie. what will do, not what do HP/Dell
etc. wish to sell me.
Yes the system wil grow over time.
One last thing ...
There may be alternative solutions to an Active:Passive cluster, but some
big name players (financial/multinational etc.) are using the system, and we
need to do some serious bomb-proofing.
I would prefer to have a single high-performance cluster, to reduce number
of requried SQL licences (sorry Bill!), and also avoid having to maintain too
many live copies of the database (yes Mirroring is a cool technology, but
maybe not for me at this moment in time?)
Surely an Active:Passive Cluster (even if x64) with external array is such a
basic setup these days, that kit for this is fairly standard?
Thank you for reading this, and thanks in advance for any constructive
anwers/pointers.
Craig
Lets see.
x64 is definitely the best bang for the buck in the range you are looking
at. More memory will help. Put in as much as the box can hold.
Obligatory naming rant: Active/Passive really doesn't describe how things
work. You are building a two-node, single-instance cluster. That
nomenclature is much more accurate and it scales. (Try describing a cluster
with 6 nodes and 12 instances using the words "active" and "passive".)
One very important consideration when building a cluster is to use some type
of smart array or a true SAN. The key is that the disk cache must reside in
the array, not on an onboard controller. Controller write cache is always
disabled in a clustered setting to maintain data consistency.
If performance is key, then RAID 1+0 is the configuration you want. Don't
worry about swap files, a properly configured dedicated SQL server should
not have any significnt paging activity. Do split tempdb onto its own fast
disk set.
As for connections, I strongly prefer fibre channel where possible. First,
it is a full-duplex data path so you can read and write at the same time.
SCSI is a bus so a large checkpoint can hammer read performance. Second,
you can only have two nodes in the cluster with SCSI. I am also very
reluctant to unplug a SCSI cable on a downed node should I need to repair
something. Not so much with a fibre channel connector.
You can always bolt mirroring on top of clustering for some geographic
separation. Choosing one does not necessarily eliminate the other.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"craig_amtdatatechnologies@.discussions.mi"
<craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
message news:130DBB73-7072-4E58-A36D-DFCD35CC6057@.microsoft.com...
> Hi,
> We are looking into implementing an Active:Passive SQL 2005 Cluster for a
> reasonably large and important system (< 1Tb)
> I'm not looking for advice re: particular brand etc., but on advice on
> type
> / type of connection to SAN that may be appropriate. The SQL 2005
> instance(s)
> will be x64.
> Please, any wannabe MVPs do not provide sarcastic/useless answers just to
> up
> your profile. To pre-empt some of these:-
> Yes I have indexes on current database
> Yes the queries have been tuned
> Yes, I have detailed stats on usage, performance, but you do not need
> these to answer the general thrust of the question
> etc.
> Now, I went through the Dell SQL configurator to see what they came up
> with
> ... they suggested ￡50k would be a reasonable price ... maybe it is,
> maybe
> it isn't. This had all manner fancy fibre connection things, disks at
> ￡1000
> each, other buzzers and bells. I wonder if I really need all this?
> Basic setup is 2 * servers (Windows 2003 R2, standard, x64), spec'd
> (each):-
> 1 * Quad-core CPU
> 2 * 15,000rpm disks (RAID 1) for O/S and SQL program files etc. (and
> swap files)
> 8Gb RAM
> Network cards, etc.
> I would like, an external disk array to hold database drives (pretty
> essential really for a cluster!), of roughly the following format (each
> physical disk probably 146Gb capacity):-
> 2 * 15,000 rpm RAID 1 (tempdb)
> 2 * 15,000 rpm RAID 1 (transaction logs)
> At least 6 (probably more) * 15,000 rpm Stripped and Mirrored for main
> database files
> What sort of storage kit/spec. (fibre? not fibre? etc. ?) should I be
> looking for to support the cluster? ie. what will do, not what do HP/Dell
> etc. wish to sell me.
> Yes the system wil grow over time.
> One last thing ...
> There may be alternative solutions to an Active:Passive cluster, but some
> big name players (financial/multinational etc.) are using the system, and
> we
> need to do some serious bomb-proofing.
> I would prefer to have a single high-performance cluster, to reduce number
> of requried SQL licences (sorry Bill!), and also avoid having to maintain
> too
> many live copies of the database (yes Mirroring is a cool technology, but
> maybe not for me at this moment in time?)
> Surely an Active:Passive Cluster (even if x64) with external array is such
> a
> basic setup these days, that kit for this is fairly standard?
> Thank you for reading this, and thanks in advance for any constructive
> anwers/pointers.
>
> Craig
>
>
>
>
|||Hi,
Thanks for reply, certainly helpful
I note the need for clarity in nomenclature, correction welcome.
If your (or anyone else), were to put names (not brands) to the bits, what
nomenclature should I be using to described the various components and bits
connecting them together?
Basically, my knowledge of storage systems is pretty weak (as you wil lhave
guessed) ... so I need a connector out the back of my sql boxes (a bit of
fibre ... 1 or 2 bits each?), something to plug the fibre cables into (an
array), some disks to stick in the array. If fibre connector is used, do
these disks need to be anything special?
Sorry for noddy style questions ... !!
Thanks again
"Geoff N. Hiten" wrote:
> Lets see.
> x64 is definitely the best bang for the buck in the range you are looking
> at. More memory will help. Put in as much as the box can hold.
> Obligatory naming rant: Active/Passive really doesn't describe how things
> work. You are building a two-node, single-instance cluster. That
> nomenclature is much more accurate and it scales. (Try describing a cluster
> with 6 nodes and 12 instances using the words "active" and "passive".)
> One very important consideration when building a cluster is to use some type
> of smart array or a true SAN. The key is that the disk cache must reside in
> the array, not on an onboard controller. Controller write cache is always
> disabled in a clustered setting to maintain data consistency.
> If performance is key, then RAID 1+0 is the configuration you want. Don't
> worry about swap files, a properly configured dedicated SQL server should
> not have any significnt paging activity. Do split tempdb onto its own fast
> disk set.
> As for connections, I strongly prefer fibre channel where possible. First,
> it is a full-duplex data path so you can read and write at the same time.
> SCSI is a bus so a large checkpoint can hammer read performance. Second,
> you can only have two nodes in the cluster with SCSI. I am also very
> reluctant to unplug a SCSI cable on a downed node should I need to repair
> something. Not so much with a fibre channel connector.
> You can always bolt mirroring on top of clustering for some geographic
> separation. Choosing one does not necessarily eliminate the other.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "craig_amtdatatechnologies@.discussions.mi"
> <craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
> message news:130DBB73-7072-4E58-A36D-DFCD35CC6057@.microsoft.com...
>
|||What you will need is one or more fibre channel adapters (called Host Bus
Adapters or HBAs) in each host computer. These can connect directly to the
SAN/Smart array or through a fibre channel switch. The configuration is
different for each. Fibre channel is really just a wrapper protocol around
the standard SCSI block access protocol, along with a fiber and an
electrical (copper) spec.
A SAN generally has gigabtes of cache and uses large internal block sizes
and aggressive caching techniques to optimize IO. A SAN can also support
many host computers where a smart array is intended to support only a few.
SANs are much more scalable. A Smart array does some abstraction of the
internal disks, but not nearly to the degree a SAN will.
The SAN or Smart array will dictate what internal connection the disks have.
Some have fibre channel (sometimes over copper wire) all the way to the
disks. Some have SCSI or SAS attachments to the actual disks.
When dealing with a SAN, the topic of LUN alignment is critical. This is
where the OS allocation blocks line up with the SAN internal stripe
boundaries. If they are not lined up, the SAN must execute excessive
internal IO operations for each physical disk request. This can lose you up
to 40% of the IO capacity of the unit.
Whatever you buy, run some IO tests so you will have a realistic expectation
and a baseline comparison when the unit is in production.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"craig_amtdatatechnologies@.discussions.mi"
<craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
message news:C485D29A-13F2-4F88-BF41-25C3F4B4B8AD@.microsoft.com...[vbcol=seagreen]
> Hi,
> Thanks for reply, certainly helpful
> I note the need for clarity in nomenclature, correction welcome.
> If your (or anyone else), were to put names (not brands) to the bits, what
> nomenclature should I be using to described the various components and
> bits
> connecting them together?
> Basically, my knowledge of storage systems is pretty weak (as you wil
> lhave
> guessed) ... so I need a connector out the back of my sql boxes (a bit of
> fibre ... 1 or 2 bits each?), something to plug the fibre cables into (an
> array), some disks to stick in the array. If fibre connector is used, do
> these disks need to be anything special?
> Sorry for noddy style questions ... !!
>
> Thanks again
>
> "Geoff N. Hiten" wrote:
|||Talking about nomenclature, unless your I/O traffic goes through some kind of
FC switch(es) or at least a hub, I wouldn't consider the storage setup as a
SAN. It's more like direct-attached.
From what you just described, I'm not sure you want the cost of setting up a
full-fledged SAN, which can be justified only if you want to share the
storage among many hosts and have significant growth expectation in that
sharing.
The thing that you would plug fibre cable in on the host is a host bus
adapter (HBA). The most commonly used HBAs are from QLogic and Emulex. Their
websites have a lot of info on HBAs that are worth reading.
The disks in the array doesn't need anything special. But the array
manufacturer typically has specs to restrict what you can plug in there if
you want their support.
Linchi
"craig_amtdatatechnologies@.discussions.mi" wrote:
[vbcol=seagreen]
> Hi,
> Thanks for reply, certainly helpful
> I note the need for clarity in nomenclature, correction welcome.
> If your (or anyone else), were to put names (not brands) to the bits, what
> nomenclature should I be using to described the various components and bits
> connecting them together?
> Basically, my knowledge of storage systems is pretty weak (as you wil lhave
> guessed) ... so I need a connector out the back of my sql boxes (a bit of
> fibre ... 1 or 2 bits each?), something to plug the fibre cables into (an
> array), some disks to stick in the array. If fibre connector is used, do
> these disks need to be anything special?
> Sorry for noddy style questions ... !!
>
> Thanks again
>
> "Geoff N. Hiten" wrote:
|||Thank you for reply.
You are right to observe that we probably don't want cost of full-blown SAN
at the moment. In future, as we do more data-warehousing for live systems, I
can see a theoretical need for shared a disk system, and we also have other
database servers related to this system where there are cost arguments for
piggy backing them on some sort of shared disk array. However, I don't think
I can justify up-front costs for this in the short and medium term.
Thanks for help with this q.
Craig
"Linchi Shea" wrote:
[vbcol=seagreen]
> Talking about nomenclature, unless your I/O traffic goes through some kind of
> FC switch(es) or at least a hub, I wouldn't consider the storage setup as a
> SAN. It's more like direct-attached.
> From what you just described, I'm not sure you want the cost of setting up a
> full-fledged SAN, which can be justified only if you want to share the
> storage among many hosts and have significant growth expectation in that
> sharing.
> The thing that you would plug fibre cable in on the host is a host bus
> adapter (HBA). The most commonly used HBAs are from QLogic and Emulex. Their
> websites have a lot of info on HBAs that are worth reading.
> The disks in the array doesn't need anything special. But the array
> manufacturer typically has specs to restrict what you can plug in there if
> you want their support.
> Linchi
> "craig_amtdatatechnologies@.discussions.mi" wrote:
|||I have a similar situation to Craig. I was looking at using the Dell MD 3000
for storage. I know that it is SCSI, but cost is an issue at this point. Any
thoughts on that box. Additionally, (this may be a stupid question so forgive
me), but can we have one server with an active intance of one database and a
passive instance of another. This way my two node cluster would be using both
severs actively and spread the load. Does this make sense.
Aaron
"Geoff N. Hiten" wrote:
> What you will need is one or more fibre channel adapters (called Host Bus
> Adapters or HBAs) in each host computer. These can connect directly to the
> SAN/Smart array or through a fibre channel switch. The configuration is
> different for each. Fibre channel is really just a wrapper protocol around
> the standard SCSI block access protocol, along with a fiber and an
> electrical (copper) spec.
> A SAN generally has gigabtes of cache and uses large internal block sizes
> and aggressive caching techniques to optimize IO. A SAN can also support
> many host computers where a smart array is intended to support only a few.
> SANs are much more scalable. A Smart array does some abstraction of the
> internal disks, but not nearly to the degree a SAN will.
> The SAN or Smart array will dictate what internal connection the disks have.
> Some have fibre channel (sometimes over copper wire) all the way to the
> disks. Some have SCSI or SAS attachments to the actual disks.
> When dealing with a SAN, the topic of LUN alignment is critical. This is
> where the OS allocation blocks line up with the SAN internal stripe
> boundaries. If they are not lined up, the SAN must execute excessive
> internal IO operations for each physical disk request. This can lose you up
> to 40% of the IO capacity of the unit.
> Whatever you buy, run some IO tests so you will have a realistic expectation
> and a baseline comparison when the unit is in production.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "craig_amtdatatechnologies@.discussions.mi"
> <craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
> message news:C485D29A-13F2-4F88-BF41-25C3F4B4B8AD@.microsoft.com...
>
|||I have not used that particular unit, bit it does meet my basic criteria of
having the controllers and cache on-board the array. I would see if Dell
can give you access to one to do some I/O testing.
You have hit upon why I am so frustrated with the
"Active/Active/Passive/whatever" nomenclature. Simply put, you cannot have
a single database file accessed and managed by two host computers. You can
have two different databases on different disk sets that normally live on
different nodes, but can failover to a single node if necessary.
Of course, any single node must be able to handle the entire load under the
worst conditions. Because that is when the system will fail.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:5AB08E84-4804-4308-8EFC-959811EDC752@.microsoft.com...[vbcol=seagreen]
>I have a similar situation to Craig. I was looking at using the Dell MD
>3000
> for storage. I know that it is SCSI, but cost is an issue at this point.
> Any
> thoughts on that box. Additionally, (this may be a stupid question so
> forgive
> me), but can we have one server with an active intance of one database and
> a
> passive instance of another. This way my two node cluster would be using
> both
> severs actively and spread the load. Does this make sense.
> Aaron
> "Geoff N. Hiten" wrote:
|||Geoff,
I understand your frustration. I am still trying to learn and understand the
new lingo. What is the basic lowdown on nodes vs. instances.
THanks,
Aaron
"Geoff N. Hiten" wrote:
> I have not used that particular unit, bit it does meet my basic criteria of
> having the controllers and cache on-board the array. I would see if Dell
> can give you access to one to do some I/O testing.
> You have hit upon why I am so frustrated with the
> "Active/Active/Passive/whatever" nomenclature. Simply put, you cannot have
> a single database file accessed and managed by two host computers. You can
> have two different databases on different disk sets that normally live on
> different nodes, but can failover to a single node if necessary.
> Of course, any single node must be able to handle the entire load under the
> worst conditions. Because that is when the system will fail.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Aaron" <Aaron@.discussions.microsoft.com> wrote in message
> news:5AB08E84-4804-4308-8EFC-959811EDC752@.microsoft.com...
>
We are looking into implementing an Active:Passive SQL 2005 Cluster for a
reasonably large and important system (< 1Tb)
I'm not looking for advice re: particular brand etc., but on advice on type
/ type of connection to SAN that may be appropriate. The SQL 2005 instance(s)
will be x64.
Please, any wannabe MVPs do not provide sarcastic/useless answers just to up
your profile. To pre-empt some of these:-
Yes I have indexes on current database
Yes the queries have been tuned
Yes, I have detailed stats on usage, performance, but you do not need
these to answer the general thrust of the question
etc.
Now, I went through the Dell SQL configurator to see what they came up with
.... they suggested ￡50k would be a reasonable price ... maybe it is, maybe
it isn't. This had all manner fancy fibre connection things, disks at ￡1000
each, other buzzers and bells. I wonder if I really need all this?
Basic setup is 2 * servers (Windows 2003 R2, standard, x64), spec'd (each):-
1 * Quad-core CPU
2 * 15,000rpm disks (RAID 1) for O/S and SQL program files etc. (and
swap files)
8Gb RAM
Network cards, etc.
I would like, an external disk array to hold database drives (pretty
essential really for a cluster!), of roughly the following format (each
physical disk probably 146Gb capacity):-
2 * 15,000 rpm RAID 1 (tempdb)
2 * 15,000 rpm RAID 1 (transaction logs)
At least 6 (probably more) * 15,000 rpm Stripped and Mirrored for main
database files
What sort of storage kit/spec. (fibre? not fibre? etc. ?) should I be
looking for to support the cluster? ie. what will do, not what do HP/Dell
etc. wish to sell me.
Yes the system wil grow over time.
One last thing ...
There may be alternative solutions to an Active:Passive cluster, but some
big name players (financial/multinational etc.) are using the system, and we
need to do some serious bomb-proofing.
I would prefer to have a single high-performance cluster, to reduce number
of requried SQL licences (sorry Bill!), and also avoid having to maintain too
many live copies of the database (yes Mirroring is a cool technology, but
maybe not for me at this moment in time?)
Surely an Active:Passive Cluster (even if x64) with external array is such a
basic setup these days, that kit for this is fairly standard?
Thank you for reading this, and thanks in advance for any constructive
anwers/pointers.
Craig
Lets see.
x64 is definitely the best bang for the buck in the range you are looking
at. More memory will help. Put in as much as the box can hold.
Obligatory naming rant: Active/Passive really doesn't describe how things
work. You are building a two-node, single-instance cluster. That
nomenclature is much more accurate and it scales. (Try describing a cluster
with 6 nodes and 12 instances using the words "active" and "passive".)
One very important consideration when building a cluster is to use some type
of smart array or a true SAN. The key is that the disk cache must reside in
the array, not on an onboard controller. Controller write cache is always
disabled in a clustered setting to maintain data consistency.
If performance is key, then RAID 1+0 is the configuration you want. Don't
worry about swap files, a properly configured dedicated SQL server should
not have any significnt paging activity. Do split tempdb onto its own fast
disk set.
As for connections, I strongly prefer fibre channel where possible. First,
it is a full-duplex data path so you can read and write at the same time.
SCSI is a bus so a large checkpoint can hammer read performance. Second,
you can only have two nodes in the cluster with SCSI. I am also very
reluctant to unplug a SCSI cable on a downed node should I need to repair
something. Not so much with a fibre channel connector.
You can always bolt mirroring on top of clustering for some geographic
separation. Choosing one does not necessarily eliminate the other.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"craig_amtdatatechnologies@.discussions.mi"
<craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
message news:130DBB73-7072-4E58-A36D-DFCD35CC6057@.microsoft.com...
> Hi,
> We are looking into implementing an Active:Passive SQL 2005 Cluster for a
> reasonably large and important system (< 1Tb)
> I'm not looking for advice re: particular brand etc., but on advice on
> type
> / type of connection to SAN that may be appropriate. The SQL 2005
> instance(s)
> will be x64.
> Please, any wannabe MVPs do not provide sarcastic/useless answers just to
> up
> your profile. To pre-empt some of these:-
> Yes I have indexes on current database
> Yes the queries have been tuned
> Yes, I have detailed stats on usage, performance, but you do not need
> these to answer the general thrust of the question
> etc.
> Now, I went through the Dell SQL configurator to see what they came up
> with
> ... they suggested ￡50k would be a reasonable price ... maybe it is,
> maybe
> it isn't. This had all manner fancy fibre connection things, disks at
> ￡1000
> each, other buzzers and bells. I wonder if I really need all this?
> Basic setup is 2 * servers (Windows 2003 R2, standard, x64), spec'd
> (each):-
> 1 * Quad-core CPU
> 2 * 15,000rpm disks (RAID 1) for O/S and SQL program files etc. (and
> swap files)
> 8Gb RAM
> Network cards, etc.
> I would like, an external disk array to hold database drives (pretty
> essential really for a cluster!), of roughly the following format (each
> physical disk probably 146Gb capacity):-
> 2 * 15,000 rpm RAID 1 (tempdb)
> 2 * 15,000 rpm RAID 1 (transaction logs)
> At least 6 (probably more) * 15,000 rpm Stripped and Mirrored for main
> database files
> What sort of storage kit/spec. (fibre? not fibre? etc. ?) should I be
> looking for to support the cluster? ie. what will do, not what do HP/Dell
> etc. wish to sell me.
> Yes the system wil grow over time.
> One last thing ...
> There may be alternative solutions to an Active:Passive cluster, but some
> big name players (financial/multinational etc.) are using the system, and
> we
> need to do some serious bomb-proofing.
> I would prefer to have a single high-performance cluster, to reduce number
> of requried SQL licences (sorry Bill!), and also avoid having to maintain
> too
> many live copies of the database (yes Mirroring is a cool technology, but
> maybe not for me at this moment in time?)
> Surely an Active:Passive Cluster (even if x64) with external array is such
> a
> basic setup these days, that kit for this is fairly standard?
> Thank you for reading this, and thanks in advance for any constructive
> anwers/pointers.
>
> Craig
>
>
>
>
|||Hi,
Thanks for reply, certainly helpful
I note the need for clarity in nomenclature, correction welcome.
If your (or anyone else), were to put names (not brands) to the bits, what
nomenclature should I be using to described the various components and bits
connecting them together?
Basically, my knowledge of storage systems is pretty weak (as you wil lhave
guessed) ... so I need a connector out the back of my sql boxes (a bit of
fibre ... 1 or 2 bits each?), something to plug the fibre cables into (an
array), some disks to stick in the array. If fibre connector is used, do
these disks need to be anything special?
Sorry for noddy style questions ... !!
Thanks again
"Geoff N. Hiten" wrote:
> Lets see.
> x64 is definitely the best bang for the buck in the range you are looking
> at. More memory will help. Put in as much as the box can hold.
> Obligatory naming rant: Active/Passive really doesn't describe how things
> work. You are building a two-node, single-instance cluster. That
> nomenclature is much more accurate and it scales. (Try describing a cluster
> with 6 nodes and 12 instances using the words "active" and "passive".)
> One very important consideration when building a cluster is to use some type
> of smart array or a true SAN. The key is that the disk cache must reside in
> the array, not on an onboard controller. Controller write cache is always
> disabled in a clustered setting to maintain data consistency.
> If performance is key, then RAID 1+0 is the configuration you want. Don't
> worry about swap files, a properly configured dedicated SQL server should
> not have any significnt paging activity. Do split tempdb onto its own fast
> disk set.
> As for connections, I strongly prefer fibre channel where possible. First,
> it is a full-duplex data path so you can read and write at the same time.
> SCSI is a bus so a large checkpoint can hammer read performance. Second,
> you can only have two nodes in the cluster with SCSI. I am also very
> reluctant to unplug a SCSI cable on a downed node should I need to repair
> something. Not so much with a fibre channel connector.
> You can always bolt mirroring on top of clustering for some geographic
> separation. Choosing one does not necessarily eliminate the other.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "craig_amtdatatechnologies@.discussions.mi"
> <craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
> message news:130DBB73-7072-4E58-A36D-DFCD35CC6057@.microsoft.com...
>
|||What you will need is one or more fibre channel adapters (called Host Bus
Adapters or HBAs) in each host computer. These can connect directly to the
SAN/Smart array or through a fibre channel switch. The configuration is
different for each. Fibre channel is really just a wrapper protocol around
the standard SCSI block access protocol, along with a fiber and an
electrical (copper) spec.
A SAN generally has gigabtes of cache and uses large internal block sizes
and aggressive caching techniques to optimize IO. A SAN can also support
many host computers where a smart array is intended to support only a few.
SANs are much more scalable. A Smart array does some abstraction of the
internal disks, but not nearly to the degree a SAN will.
The SAN or Smart array will dictate what internal connection the disks have.
Some have fibre channel (sometimes over copper wire) all the way to the
disks. Some have SCSI or SAS attachments to the actual disks.
When dealing with a SAN, the topic of LUN alignment is critical. This is
where the OS allocation blocks line up with the SAN internal stripe
boundaries. If they are not lined up, the SAN must execute excessive
internal IO operations for each physical disk request. This can lose you up
to 40% of the IO capacity of the unit.
Whatever you buy, run some IO tests so you will have a realistic expectation
and a baseline comparison when the unit is in production.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"craig_amtdatatechnologies@.discussions.mi"
<craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
message news:C485D29A-13F2-4F88-BF41-25C3F4B4B8AD@.microsoft.com...[vbcol=seagreen]
> Hi,
> Thanks for reply, certainly helpful
> I note the need for clarity in nomenclature, correction welcome.
> If your (or anyone else), were to put names (not brands) to the bits, what
> nomenclature should I be using to described the various components and
> bits
> connecting them together?
> Basically, my knowledge of storage systems is pretty weak (as you wil
> lhave
> guessed) ... so I need a connector out the back of my sql boxes (a bit of
> fibre ... 1 or 2 bits each?), something to plug the fibre cables into (an
> array), some disks to stick in the array. If fibre connector is used, do
> these disks need to be anything special?
> Sorry for noddy style questions ... !!
>
> Thanks again
>
> "Geoff N. Hiten" wrote:
|||Talking about nomenclature, unless your I/O traffic goes through some kind of
FC switch(es) or at least a hub, I wouldn't consider the storage setup as a
SAN. It's more like direct-attached.
From what you just described, I'm not sure you want the cost of setting up a
full-fledged SAN, which can be justified only if you want to share the
storage among many hosts and have significant growth expectation in that
sharing.
The thing that you would plug fibre cable in on the host is a host bus
adapter (HBA). The most commonly used HBAs are from QLogic and Emulex. Their
websites have a lot of info on HBAs that are worth reading.
The disks in the array doesn't need anything special. But the array
manufacturer typically has specs to restrict what you can plug in there if
you want their support.
Linchi
"craig_amtdatatechnologies@.discussions.mi" wrote:
[vbcol=seagreen]
> Hi,
> Thanks for reply, certainly helpful
> I note the need for clarity in nomenclature, correction welcome.
> If your (or anyone else), were to put names (not brands) to the bits, what
> nomenclature should I be using to described the various components and bits
> connecting them together?
> Basically, my knowledge of storage systems is pretty weak (as you wil lhave
> guessed) ... so I need a connector out the back of my sql boxes (a bit of
> fibre ... 1 or 2 bits each?), something to plug the fibre cables into (an
> array), some disks to stick in the array. If fibre connector is used, do
> these disks need to be anything special?
> Sorry for noddy style questions ... !!
>
> Thanks again
>
> "Geoff N. Hiten" wrote:
|||Thank you for reply.
You are right to observe that we probably don't want cost of full-blown SAN
at the moment. In future, as we do more data-warehousing for live systems, I
can see a theoretical need for shared a disk system, and we also have other
database servers related to this system where there are cost arguments for
piggy backing them on some sort of shared disk array. However, I don't think
I can justify up-front costs for this in the short and medium term.
Thanks for help with this q.
Craig
"Linchi Shea" wrote:
[vbcol=seagreen]
> Talking about nomenclature, unless your I/O traffic goes through some kind of
> FC switch(es) or at least a hub, I wouldn't consider the storage setup as a
> SAN. It's more like direct-attached.
> From what you just described, I'm not sure you want the cost of setting up a
> full-fledged SAN, which can be justified only if you want to share the
> storage among many hosts and have significant growth expectation in that
> sharing.
> The thing that you would plug fibre cable in on the host is a host bus
> adapter (HBA). The most commonly used HBAs are from QLogic and Emulex. Their
> websites have a lot of info on HBAs that are worth reading.
> The disks in the array doesn't need anything special. But the array
> manufacturer typically has specs to restrict what you can plug in there if
> you want their support.
> Linchi
> "craig_amtdatatechnologies@.discussions.mi" wrote:
|||I have a similar situation to Craig. I was looking at using the Dell MD 3000
for storage. I know that it is SCSI, but cost is an issue at this point. Any
thoughts on that box. Additionally, (this may be a stupid question so forgive
me), but can we have one server with an active intance of one database and a
passive instance of another. This way my two node cluster would be using both
severs actively and spread the load. Does this make sense.
Aaron
"Geoff N. Hiten" wrote:
> What you will need is one or more fibre channel adapters (called Host Bus
> Adapters or HBAs) in each host computer. These can connect directly to the
> SAN/Smart array or through a fibre channel switch. The configuration is
> different for each. Fibre channel is really just a wrapper protocol around
> the standard SCSI block access protocol, along with a fiber and an
> electrical (copper) spec.
> A SAN generally has gigabtes of cache and uses large internal block sizes
> and aggressive caching techniques to optimize IO. A SAN can also support
> many host computers where a smart array is intended to support only a few.
> SANs are much more scalable. A Smart array does some abstraction of the
> internal disks, but not nearly to the degree a SAN will.
> The SAN or Smart array will dictate what internal connection the disks have.
> Some have fibre channel (sometimes over copper wire) all the way to the
> disks. Some have SCSI or SAS attachments to the actual disks.
> When dealing with a SAN, the topic of LUN alignment is critical. This is
> where the OS allocation blocks line up with the SAN internal stripe
> boundaries. If they are not lined up, the SAN must execute excessive
> internal IO operations for each physical disk request. This can lose you up
> to 40% of the IO capacity of the unit.
> Whatever you buy, run some IO tests so you will have a realistic expectation
> and a baseline comparison when the unit is in production.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "craig_amtdatatechnologies@.discussions.mi"
> <craigamtdatatechnologiesdiscussionsmi@.discussions .microsoft.com> wrote in
> message news:C485D29A-13F2-4F88-BF41-25C3F4B4B8AD@.microsoft.com...
>
|||I have not used that particular unit, bit it does meet my basic criteria of
having the controllers and cache on-board the array. I would see if Dell
can give you access to one to do some I/O testing.
You have hit upon why I am so frustrated with the
"Active/Active/Passive/whatever" nomenclature. Simply put, you cannot have
a single database file accessed and managed by two host computers. You can
have two different databases on different disk sets that normally live on
different nodes, but can failover to a single node if necessary.
Of course, any single node must be able to handle the entire load under the
worst conditions. Because that is when the system will fail.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:5AB08E84-4804-4308-8EFC-959811EDC752@.microsoft.com...[vbcol=seagreen]
>I have a similar situation to Craig. I was looking at using the Dell MD
>3000
> for storage. I know that it is SCSI, but cost is an issue at this point.
> Any
> thoughts on that box. Additionally, (this may be a stupid question so
> forgive
> me), but can we have one server with an active intance of one database and
> a
> passive instance of another. This way my two node cluster would be using
> both
> severs actively and spread the load. Does this make sense.
> Aaron
> "Geoff N. Hiten" wrote:
|||Geoff,
I understand your frustration. I am still trying to learn and understand the
new lingo. What is the basic lowdown on nodes vs. instances.
THanks,
Aaron
"Geoff N. Hiten" wrote:
> I have not used that particular unit, bit it does meet my basic criteria of
> having the controllers and cache on-board the array. I would see if Dell
> can give you access to one to do some I/O testing.
> You have hit upon why I am so frustrated with the
> "Active/Active/Passive/whatever" nomenclature. Simply put, you cannot have
> a single database file accessed and managed by two host computers. You can
> have two different databases on different disk sets that normally live on
> different nodes, but can failover to a single node if necessary.
> Of course, any single node must be able to handle the entire load under the
> worst conditions. Because that is when the system will fail.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Aaron" <Aaron@.discussions.microsoft.com> wrote in message
> news:5AB08E84-4804-4308-8EFC-959811EDC752@.microsoft.com...
>
clustering Exchange and SQL server using one SAN drive
I'm planning to use Exchange Server 2003 and SQL server 2000 in a clustered
solution (windows 2003) with 2 nodes.
One node should contain the active Exchange resources. The other node should
contain the active SQL server resources. If one node failes the other node
should run all Exchange AND SQL server resources.
I am using a SAN (HP MSA500) solution for data storage. In our cluster
server this is assigned as the physical disk resource "Disk D:". This disk
resource was added to the default group "Cluster group".
I need to store my data from both Exchange Server and SQL server on this
"Disk D:". However, this disk resource is joined to only one node. The
D-drive is only available on the node which is active for the "Cluster
group".
Question: is it possible to use the D-drive for both nodes at the same time?
What am I doing wrong?
Thanks in advance for your answer.
Arnoud Muggen
You have a hardware configuration issue. Microsoft clustering uses the
shared nothing model. You simply can't have the D Drive on both nodes at the
same time.
Start all over. Carve up your MAS500 into volumes. Clustering will use these
volumes as drives.
Next issue, its really not a good idea to run Active(SQL)/Active(Exchange)
on a two node cluster. During a failure the remaining system is going to
take a pretty big performance hit. Let alone having the SQL & Exchange bits
on the same machine at the same time. Yuck and not a best practice,
especially if you care about performance.
I suggest you get Virtual Server 2005 or VMWare and create a test cluster to
learn more about configurations. Knowledge is very handy with clusters.
I also hear that www.clusterhelp.com has several custom detailed training
classes coming up in NYC & Denver. You may want to looking to them for help
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Arnoud Muggen" <webmaster_n_o_s_p_a_m_@.act-one.net> wrote in message
news:eZkgekp6FHA.1724@.TK2MSFTNGP10.phx.gbl...
> I'm planning to use Exchange Server 2003 and SQL server 2000 in a
> clustered
> solution (windows 2003) with 2 nodes.
> One node should contain the active Exchange resources. The other node
> should
> contain the active SQL server resources. If one node failes the other node
> should run all Exchange AND SQL server resources.
> I am using a SAN (HP MSA500) solution for data storage. In our cluster
> server this is assigned as the physical disk resource "Disk D:". This disk
> resource was added to the default group "Cluster group".
> I need to store my data from both Exchange Server and SQL server on this
> "Disk D:". However, this disk resource is joined to only one node. The
> D-drive is only available on the node which is active for the "Cluster
> group".
> Question: is it possible to use the D-drive for both nodes at the same
> time?
> What am I doing wrong?
> Thanks in advance for your answer.
> Arnoud Muggen
>
|||Everything clear, thanks. I'll start the installation all over again.
Thanks for your help
Arnoud
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23as4D8q6FHA.3120@.tk2msftngp13.phx.gbl...
> You have a hardware configuration issue. Microsoft clustering uses the
> shared nothing model. You simply can't have the D Drive on both nodes at
the
> same time.
> Start all over. Carve up your MAS500 into volumes. Clustering will use
these
> volumes as drives.
> Next issue, its really not a good idea to run Active(SQL)/Active(Exchange)
> on a two node cluster. During a failure the remaining system is going to
> take a pretty big performance hit. Let alone having the SQL & Exchange
bits
> on the same machine at the same time. Yuck and not a best practice,
> especially if you care about performance.
> I suggest you get Virtual Server 2005 or VMWare and create a test cluster
to
> learn more about configurations. Knowledge is very handy with clusters.
> I also hear that www.clusterhelp.com has several custom detailed training
> classes coming up in NYC & Denver. You may want to looking to them for
help[vbcol=seagreen]
>
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://www.msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
>
> "Arnoud Muggen" <webmaster_n_o_s_p_a_m_@.act-one.net> wrote in message
> news:eZkgekp6FHA.1724@.TK2MSFTNGP10.phx.gbl...
node[vbcol=seagreen]
disk
>
solution (windows 2003) with 2 nodes.
One node should contain the active Exchange resources. The other node should
contain the active SQL server resources. If one node failes the other node
should run all Exchange AND SQL server resources.
I am using a SAN (HP MSA500) solution for data storage. In our cluster
server this is assigned as the physical disk resource "Disk D:". This disk
resource was added to the default group "Cluster group".
I need to store my data from both Exchange Server and SQL server on this
"Disk D:". However, this disk resource is joined to only one node. The
D-drive is only available on the node which is active for the "Cluster
group".
Question: is it possible to use the D-drive for both nodes at the same time?
What am I doing wrong?
Thanks in advance for your answer.
Arnoud Muggen
You have a hardware configuration issue. Microsoft clustering uses the
shared nothing model. You simply can't have the D Drive on both nodes at the
same time.
Start all over. Carve up your MAS500 into volumes. Clustering will use these
volumes as drives.
Next issue, its really not a good idea to run Active(SQL)/Active(Exchange)
on a two node cluster. During a failure the remaining system is going to
take a pretty big performance hit. Let alone having the SQL & Exchange bits
on the same machine at the same time. Yuck and not a best practice,
especially if you care about performance.
I suggest you get Virtual Server 2005 or VMWare and create a test cluster to
learn more about configurations. Knowledge is very handy with clusters.
I also hear that www.clusterhelp.com has several custom detailed training
classes coming up in NYC & Denver. You may want to looking to them for help
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Arnoud Muggen" <webmaster_n_o_s_p_a_m_@.act-one.net> wrote in message
news:eZkgekp6FHA.1724@.TK2MSFTNGP10.phx.gbl...
> I'm planning to use Exchange Server 2003 and SQL server 2000 in a
> clustered
> solution (windows 2003) with 2 nodes.
> One node should contain the active Exchange resources. The other node
> should
> contain the active SQL server resources. If one node failes the other node
> should run all Exchange AND SQL server resources.
> I am using a SAN (HP MSA500) solution for data storage. In our cluster
> server this is assigned as the physical disk resource "Disk D:". This disk
> resource was added to the default group "Cluster group".
> I need to store my data from both Exchange Server and SQL server on this
> "Disk D:". However, this disk resource is joined to only one node. The
> D-drive is only available on the node which is active for the "Cluster
> group".
> Question: is it possible to use the D-drive for both nodes at the same
> time?
> What am I doing wrong?
> Thanks in advance for your answer.
> Arnoud Muggen
>
|||Everything clear, thanks. I'll start the installation all over again.
Thanks for your help
Arnoud
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23as4D8q6FHA.3120@.tk2msftngp13.phx.gbl...
> You have a hardware configuration issue. Microsoft clustering uses the
> shared nothing model. You simply can't have the D Drive on both nodes at
the
> same time.
> Start all over. Carve up your MAS500 into volumes. Clustering will use
these
> volumes as drives.
> Next issue, its really not a good idea to run Active(SQL)/Active(Exchange)
> on a two node cluster. During a failure the remaining system is going to
> take a pretty big performance hit. Let alone having the SQL & Exchange
bits
> on the same machine at the same time. Yuck and not a best practice,
> especially if you care about performance.
> I suggest you get Virtual Server 2005 or VMWare and create a test cluster
to
> learn more about configurations. Knowledge is very handy with clusters.
> I also hear that www.clusterhelp.com has several custom detailed training
> classes coming up in NYC & Denver. You may want to looking to them for
help[vbcol=seagreen]
>
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://www.msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
>
> "Arnoud Muggen" <webmaster_n_o_s_p_a_m_@.act-one.net> wrote in message
> news:eZkgekp6FHA.1724@.TK2MSFTNGP10.phx.gbl...
node[vbcol=seagreen]
disk
>
Clustering configuring
Hi all,
I'm new to clustering. Is there any website on how i could learn to
configure clustering.
I have 2 new servers(Svr1 & Svr2) and san storage. On Svr1 i'm going to
install Win 2003 and sql 2000. Svr2 is going to be application server(dfs,
VB.NET, etc).
Can anyone help me on how should i do the configuration.
Appreciate ur help.
Tks
Message posted via http://www.sqlmonster.com
Hi
http://www.microsoft.com/windowsserv...g/default.mspx
Importantly, the applications you install must be at least cluster aware.
http://msdn.microsoft.com/library/de...plications.asp
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/
"Mohd via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in message
news:a65b8f99202043dfba56c3b4499fb5a6@.SQLMonster.c om...
> Hi all,
> I'm new to clustering. Is there any website on how i could learn to
> configure clustering.
> I have 2 new servers(Svr1 & Svr2) and san storage. On Svr1 i'm going to
> install Win 2003 and sql 2000. Svr2 is going to be application server(dfs,
> VB.NET, etc).
> Can anyone help me on how should i do the configuration.
> Appreciate ur help.
> Tks
> --
> Message posted via http://www.sqlmonster.com
|||We website has a ton of information.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Mohd via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in message
news:a65b8f99202043dfba56c3b4499fb5a6@.SQLMonster.c om...
> Hi all,
> I'm new to clustering. Is there any website on how i could learn to
> configure clustering.
> I have 2 new servers(Svr1 & Svr2) and san storage. On Svr1 i'm going to
> install Win 2003 and sql 2000. Svr2 is going to be application server(dfs,
> VB.NET, etc).
> Can anyone help me on how should i do the configuration.
> Appreciate ur help.
> Tks
> --
> Message posted via http://www.sqlmonster.com
|||We? Where did that come from. I meant my. DOH!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:OjlOfTDQFHA.204@.TK2MSFTNGP15.phx.gbl...
> We website has a ton of information.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> "Mohd via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in message
> news:a65b8f99202043dfba56c3b4499fb5a6@.SQLMonster.c om...
>
I'm new to clustering. Is there any website on how i could learn to
configure clustering.
I have 2 new servers(Svr1 & Svr2) and san storage. On Svr1 i'm going to
install Win 2003 and sql 2000. Svr2 is going to be application server(dfs,
VB.NET, etc).
Can anyone help me on how should i do the configuration.
Appreciate ur help.
Tks
Message posted via http://www.sqlmonster.com
Hi
http://www.microsoft.com/windowsserv...g/default.mspx
Importantly, the applications you install must be at least cluster aware.
http://msdn.microsoft.com/library/de...plications.asp
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/
"Mohd via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in message
news:a65b8f99202043dfba56c3b4499fb5a6@.SQLMonster.c om...
> Hi all,
> I'm new to clustering. Is there any website on how i could learn to
> configure clustering.
> I have 2 new servers(Svr1 & Svr2) and san storage. On Svr1 i'm going to
> install Win 2003 and sql 2000. Svr2 is going to be application server(dfs,
> VB.NET, etc).
> Can anyone help me on how should i do the configuration.
> Appreciate ur help.
> Tks
> --
> Message posted via http://www.sqlmonster.com
|||We website has a ton of information.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Mohd via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in message
news:a65b8f99202043dfba56c3b4499fb5a6@.SQLMonster.c om...
> Hi all,
> I'm new to clustering. Is there any website on how i could learn to
> configure clustering.
> I have 2 new servers(Svr1 & Svr2) and san storage. On Svr1 i'm going to
> install Win 2003 and sql 2000. Svr2 is going to be application server(dfs,
> VB.NET, etc).
> Can anyone help me on how should i do the configuration.
> Appreciate ur help.
> Tks
> --
> Message posted via http://www.sqlmonster.com
|||We? Where did that come from. I meant my. DOH!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:OjlOfTDQFHA.204@.TK2MSFTNGP15.phx.gbl...
> We website has a ton of information.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> "Mohd via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in message
> news:a65b8f99202043dfba56c3b4499fb5a6@.SQLMonster.c om...
>
Friday, February 10, 2012
Cluster/SQL 2005/1 node install
We have setup a MSCS with no problem. Have a SAN with mounted volumes and
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message.
Further action is only required if Kerberos authentication is required by
authentication policies.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
Thanks and God Bless,
ThomBeaux
The service account did not have the:
(local policy) - Act as part of the OS
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. Failure to register an SPN may cause integrated authentication
> to fall back to NTLM instead of Kerberos. This is an informational message.
> Further action is only required if Kerberos authentication is required by
> authentication policies.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message.
Further action is only required if Kerberos authentication is required by
authentication policies.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
Thanks and God Bless,
ThomBeaux
The service account did not have the:
(local policy) - Act as part of the OS
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. Failure to register an SPN may cause integrated authentication
> to fall back to NTLM instead of Kerberos. This is an informational message.
> Further action is only required if Kerberos authentication is required by
> authentication policies.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux
Cluster/SQL 2005/1 node install
We have setup a MSCS with no problem. Have a SAN with mounted volumes and
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message.
Further action is only required if Kerberos authentication is required by
authentication policies.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
--
Thanks and God Bless,
ThomBeauxThe service account did not have the:
(local policy) - Act as part of the OS
--
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. Failure to register an SPN may cause integrated authentication
> to fall back to NTLM instead of Kerberos. This is an informational message.
> Further action is only required if Kerberos authentication is required by
> authentication policies.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message.
Further action is only required if Kerberos authentication is required by
authentication policies.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
--
Thanks and God Bless,
ThomBeauxThe service account did not have the:
(local policy) - Act as part of the OS
--
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. Failure to register an SPN may cause integrated authentication
> to fall back to NTLM instead of Kerberos. This is an informational message.
> Further action is only required if Kerberos authentication is required by
> authentication policies.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux
Subscribe to:
Posts (Atom)