Groups | Blog | Home
all groups > sql server clustering > august 2007 >

sql server clustering : high availabilty of windows/sql clustering


Rodney R. Fournier [MVP]
8/20/2007 11:10:20 AM
Systems are only as good as your people, processes, and procedures. Do you
plan to have complete as built documents? 24 x 7 mentoring? SLA? Top
management support? Trained personal? Tested restores? Fully designed
systems?

How are you defining availability?

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner


[quoted text, click to view]

gigel
8/20/2007 11:52:04 AM
How well does MS clustering meet the 99.999% availability?
What other technoologies/architectures that do a better job from this
stand-point?

Gigel

Ayad Shammout
8/20/2007 12:07:51 PM
We are using MS clustering on all of our SQL servers and we are 99.999% HA.

We have no issues and been very stable.

Ayad Shammout

[quoted text, click to view]

Russ Kaufmann [MVP]
8/20/2007 12:52:48 PM
[quoted text, click to view]

I would define it as the total time unavailable during hours when the
service is required. So, for example, if there is no requirement for it to
be available at 2am because there are no users, then taking an outage at
that time would not count against me.

There are many other views on the term.


--
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp

The next ClusterHelp classes are:
Sep 3 - 6 in Copenhagen
Oct 8 - 11 in New York
Rodney R. Fournier [MVP]
8/20/2007 1:50:58 PM
You and I can talk about definitions all day, what does your SLA say? Your
customer expect?

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner


[quoted text, click to view]

gigel
8/20/2007 2:27:41 PM
Thanks for your reply Ayad.

What about situations when you have to apply windows or sql service packs?
I guess on a well built / well maintained cluster the installation of
service packs is smooth
with little downtime. But what about when things aren't going smoothly?

Gigel

[quoted text, click to view]

gigel
8/20/2007 2:35:58 PM
Rodney,

I agree 100%, but there are things that happen(or happened) outside of dba's
control.

Here is how I would define unavailability, the total amount of time in the
course of a year when a database is unavailable, cause by applying
windows or sql service packs. More concerned with situations when the
installation doesn't go smoothly and the last resort is rebuilding the
cluster or installing sql from scratch.

Gigel

"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:%23NWhcS04HHA.1484@TK2MSFTNGP06.phx.gbl...
[quoted text, click to view]

Enghps1
8/20/2007 8:04:20 PM
any patching would involve moving resources from node to node and vice versa
multiple times, so you also need to know whether whatever application youre
running is cluster-aware or whether each failover will create outages to
users which last long after the the cluster has finished failing over. You
patch one node at a time and test after each stage so you should never need
to "start from scratch" you'd just restore one node. If your company dont
provide a real test lab then they shoudlnt expect an exact figure, I assume
they opted for a "high availability" cluster hardware along with redundant
power and environmental control etc otherwise theyre not seeing the whole
picture when they ask for a "minutes per year"


[quoted text, click to view]

JR
8/22/2007 8:32:04 AM
Hello Gigel

[quoted text, click to view]
The fail over will work fine..
Well, i can speak in my experience, seven years using SQL clusters
The problem about the service not available is in "most" cases is related to
HW (bios, drivers, frimware, SP), and in this cases is when you can use the
cluster fail over, at this time you have like 30 seconds of downtime while
the service is moved to other node...
If the problem is software I recommend to have a support contract whit
MSFT.. or the software installed in the cluster, in MSFT the cases can be
fixed for a patch o directions that msft can provide in allmost cases, in
other cases you can find a document in the KB of microsoft and download the
file o request the patch directly..

** try to have updated all drivers and bios for your cluster ...

[quoted text, click to view]
AddThis Social Bookmark Button