Managed Disks in Windows 2003

While setting up windows cluster in 2003, my external array which is
logically partiotioned into P and Q appear as one disk group.
If i wanted to setup an active/active SQL cluster, how can i seperate into 2
groups, so that one node owns P and SQL instance 1 has data files on P and
the other node owns Q with another SQL instance owning Q. I didnt see a
managed disk dialog during the 2003 windows cluster instance.
Consult with your extenal array vendor documentation/support. It may be that your array cannot present virtual disks (like many high-end SANs can). This may mean that you need disk sets made up of different physical disks to present 2 "disks" to your cl
uster. eg physical disks 1, 2+3 are drive P, while physical disks 4 and 5 are drive Q. Don't forget that you'll also need a separate disk for the Quorum. So, in your configuration you'll need to have AT LEAST 3 separate disks to present to your cluster
. What sort of external array are you using?
|||MSCS looks at the physical layer, not the partition level. So you can have 4
partitions on a single disk, but MSCS will display this as one physical disk
resource. The only way to achieve an active/active configuration would be to
add another physical disk...can't be done with your current config.
Regards,
John.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:e$W6OIPFEHA.2768@.tk2msftngp13.phx.gbl...
> While setting up windows cluster in 2003, my external array which is
> logically partiotioned into P and Q appear as one disk group.
> If i wanted to setup an active/active SQL cluster, how can i seperate into
2
> groups, so that one node owns P and SQL instance 1 has data files on P and
> the other node owns Q with another SQL instance owning Q. I didnt see a
> managed disk dialog during the 2003 windows cluster instance.
>
>

Manage cluster resources via Visual Basic

Hello,
is it possible to manage cluster resources with a script language like
Visual Basic?
I want to update the cluster applications with an automatic
installation process. Therefore I must stop the corresponding cluster
resource (take offline), update the application and restart the
cluster resource (bring online).
Knows anyone a way to do this within a Visual Basic program?
Thanks
Widmann
Yes, it is very possible. Do I know how to do it? Heck no. I am not a
programmer in any sense. Check msdn.microsoft.com or "goggle
site:msdn.microsoft.com" cluster programming. Or something like that using
programmer speak
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Friedbert Widmann" <WidiHEL@.gmx.de> wrote in message
news:1acb6845.0411180650.2a2d88e6@.posting.google.c om...
> Hello,
> is it possible to manage cluster resources with a script language like
> Visual Basic?
> I want to update the cluster applications with an automatic
> installation process. Therefore I must stop the corresponding cluster
> resource (take offline), update the application and restart the
> cluster resource (bring online).
> Knows anyone a way to do this within a Visual Basic program?
> Thanks
> Widmann
|||This might be a good place to start:
http://msdn.microsoft.com/library/en...start_page.asp
Regards,
John
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:OWHUHbYzEHA.1196@.TK2MSFTNGP15.phx.gbl...
> Yes, it is very possible. Do I know how to do it? Heck no. I am not a
> programmer in any sense. Check msdn.microsoft.com or "goggle
> site:msdn.microsoft.com" cluster programming. Or something like that using
> programmer speak
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "Friedbert Widmann" <WidiHEL@.gmx.de> wrote in message
> news:1acb6845.0411180650.2a2d88e6@.posting.google.c om...
>
|||The easiest way is to us the command-line tool 'Cluster.exe'. It works very
well from a script. See Windows help for details.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Friedbert Widmann" <WidiHEL@.gmx.de> wrote in message
news:1acb6845.0411180650.2a2d88e6@.posting.google.c om...
> Hello,
> is it possible to manage cluster resources with a script language like
> Visual Basic?
> I want to update the cluster applications with an automatic
> installation process. Therefore I must stop the corresponding cluster
> resource (take offline), update the application and restart the
> cluster resource (bring online).
> Knows anyone a way to do this within a Visual Basic program?
> Thanks
> Widmann
|||use WMI...but carefull
rgds
Sinisa
"Geoff N. Hiten" wrote:

> The easiest way is to us the command-line tool 'Cluster.exe'. It works very
> well from a script. See Windows help for details.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Friedbert Widmann" <WidiHEL@.gmx.de> wrote in message
> news:1acb6845.0411180650.2a2d88e6@.posting.google.c om...
>
>

Making changes to a pre-existing cluster. Need help!

Hello,
We are making some changes to our existing SQL 2 Node cluster with Heartbeat
cross over.
1). We are adding a third node for Failover.
2). We added new NICS to all three servers and will set the Heartbeat up on
a switch.
3). Need to team the other two NICS on each server which I believe will
trash the cluster because the cluster is bound to one of the NICs on each of
the two node cluster.
Just looking for some insight on which steps need to be done. Do we have to
remove the servers from the cluster and recreate? What does that do to SQL?
What are the steps for adding a Failover node?
Thanks for your help,
Jeremey
First of all, you have to be running Win2K Datacenter Edition or at least
Win2K3 Enterprise Edition to support more than 2-node failover server
clusters.
The heartbeat network needs to be segmented differently than the public
networks, with NETBIOS disabled, which uses multi-cast; so, you'll want to
VLAN it and can not use NIC-teaming with it.
Each of the public networks can use NIC-teaming. As soon as you configure
each node, the cluster will recognize the networks. Each bound IP will go
offline and reregister.
To add nodes, you use the Cluster Administrator to add nodes to the cluster.
You use the SQL Server installation to deploy the binaries to the additional
nodes. You then apply the service packs from the newly joined Inactive
nodes only.
Here are a few links as well as Books Online for reference.
SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
Both of the Maintaining and Troubleshooting sections talk about adding nodes
and service packs.
Server Clusters: Rolling Upgrades. Upgrading to Windows Server 2003
http://www.microsoft.com/technet/pro.../rllupnet.mspx
Sincerely,
Anthony Thomas

"Jeremey" <Jeremey@.discussions.microsoft.com> wrote in message
news:39C48FBE-D7CB-4907-B7A1-DF1ADEB5499F@.microsoft.com...
> Hello,
> We are making some changes to our existing SQL 2 Node cluster with
Heartbeat
> cross over.
> 1). We are adding a third node for Failover.
> 2). We added new NICS to all three servers and will set the Heartbeat up
on
> a switch.
> 3). Need to team the other two NICS on each server which I believe will
> trash the cluster because the cluster is bound to one of the NICs on each
of
> the two node cluster.
> Just looking for some insight on which steps need to be done. Do we have
to
> remove the servers from the cluster and recreate? What does that do to
SQL?
> What are the steps for adding a Failover node?
> Thanks for your help,
> Jeremey
|||Hi Anthony,
Thanks for the links. I am however coming a cross a problem where the newly
added Node is now part of the storage group on the SAN but I can't format the
drives through the new servers Disk Manager, at which point I can't add it to
the cluster because it can't see any of the drives. In Disk Manager the
description of each drive is unavailable and New Partition is greyed out.
Any thoughts?
Thanks,
Jeremey
"Anthony Thomas" wrote:

> First of all, you have to be running Win2K Datacenter Edition or at least
> Win2K3 Enterprise Edition to support more than 2-node failover server
> clusters.
> The heartbeat network needs to be segmented differently than the public
> networks, with NETBIOS disabled, which uses multi-cast; so, you'll want to
> VLAN it and can not use NIC-teaming with it.
> Each of the public networks can use NIC-teaming. As soon as you configure
> each node, the cluster will recognize the networks. Each bound IP will go
> offline and reregister.
> To add nodes, you use the Cluster Administrator to add nodes to the cluster.
> You use the SQL Server installation to deploy the binaries to the additional
> nodes. You then apply the service packs from the newly joined Inactive
> nodes only.
> Here are a few links as well as Books Online for reference.
> SQL Server 2000 Failover Clustering
> http://www.microsoft.com/technet/pro.../failclus.mspx
> Both of the Maintaining and Troubleshooting sections talk about adding nodes
> and service packs.
> Server Clusters: Rolling Upgrades. Upgrading to Windows Server 2003
> http://www.microsoft.com/technet/pro.../rllupnet.mspx
> Sincerely,
>
> Anthony Thomas
>
> --
> "Jeremey" <Jeremey@.discussions.microsoft.com> wrote in message
> news:39C48FBE-D7CB-4907-B7A1-DF1ADEB5499F@.microsoft.com...
> Heartbeat
> on
> of
> to
> SQL?
>
>
|||You are adding an additional node to the cluster. What is the purpose of
this node with respect to SQL Server? Will this be a new active instance or
will this be an inactive node for existing instances?
If a new SQL Server instance, then yes, you will need to detect the drive,
format it, create a new cluster group with separate IP and Network Name and
then add this new disk.
To get the Disk Manager to "see" new disks, you'll have to "Rescan Disks"
and then "Refresh." You might also have to mark the disk as "Online," all
through the Disk Manager interface. If it does not recognize the disk,
you'll have to check the zoning configuration in the SAN.
Also, check the other cluster nodes to see if they recognize the new disk.
You will also want to check out the DISKPAR utility if prior to SP 1 and
DISKPART utility if post SP1 on Win2K3. Look into disk sector alignment.
Here's a link.
Examining and Tuning Disk Performance
http://www.microsoft.com/resources/d...e_exa_oori.asp
Disk Geometry
http://www.msexchange.org/tutorials/Disk-Geometry.html
Even though many of these refer to Exchange Server, much is still relevant
to SQL Server, Clustered Disks, and SAN configurations.
Sincerely,
Anthony Thomas

"Jeremey" <Jeremey@.discussions.microsoft.com> wrote in message
news:62D731CD-7129-459B-AF92-79D2FF588BC7@.microsoft.com...
> Hi Anthony,
> Thanks for the links. I am however coming a cross a problem where the
newly
> added Node is now part of the storage group on the SAN but I can't format
the
> drives through the new servers Disk Manager, at which point I can't add it
to[vbcol=seagreen]
> the cluster because it can't see any of the drives. In Disk Manager the
> description of each drive is unavailable and New Partition is greyed out.
> Any thoughts?
> Thanks,
> Jeremey
> "Anthony Thomas" wrote:
least[vbcol=seagreen]
to[vbcol=seagreen]
configure[vbcol=seagreen]
go[vbcol=seagreen]
cluster.[vbcol=seagreen]
additional[vbcol=seagreen]
http://www.microsoft.com/technet/pro.../failclus.mspx[vbcol=seagreen]
nodes[vbcol=seagreen]
http://www.microsoft.com/technet/pro.../rllupnet.mspx[vbcol=seagreen]
up[vbcol=seagreen]
will[vbcol=seagreen]
each[vbcol=seagreen]
have[vbcol=seagreen]
to[vbcol=seagreen]
|||Hi Anthony,
It will actually be an Inactive node used for failover. All servers are
Win2k3 Ent SP1 with the latest patches. We are not adding any new LUNs to
the group just a new Node at which I will need to at least be able to connect
to the Quorum drive. I will try the suggestions you gave me. Also when I go
to install SQL as a Failover will I need a dedicated Drive for the install
that is part of the SAN?
Thanks again for all your help, this is the first more than two node SQL
cluster that I've ever worked on.
Jeremey
"Anthony Thomas" wrote:

> You are adding an additional node to the cluster. What is the purpose of
> this node with respect to SQL Server? Will this be a new active instance or
> will this be an inactive node for existing instances?
> If a new SQL Server instance, then yes, you will need to detect the drive,
> format it, create a new cluster group with separate IP and Network Name and
> then add this new disk.
> To get the Disk Manager to "see" new disks, you'll have to "Rescan Disks"
> and then "Refresh." You might also have to mark the disk as "Online," all
> through the Disk Manager interface. If it does not recognize the disk,
> you'll have to check the zoning configuration in the SAN.
> Also, check the other cluster nodes to see if they recognize the new disk.
> You will also want to check out the DISKPAR utility if prior to SP 1 and
> DISKPART utility if post SP1 on Win2K3. Look into disk sector alignment.
> Here's a link.
> Examining and Tuning Disk Performance
> http://www.microsoft.com/resources/d...e_exa_oori.asp
> Disk Geometry
> http://www.msexchange.org/tutorials/Disk-Geometry.html
> Even though many of these refer to Exchange Server, much is still relevant
> to SQL Server, Clustered Disks, and SAN configurations.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Jeremey" <Jeremey@.discussions.microsoft.com> wrote in message
> news:62D731CD-7129-459B-AF92-79D2FF588BC7@.microsoft.com...
> newly
> the
> to
> least
> to
> configure
> go
> cluster.
> additional
> http://www.microsoft.com/technet/pro.../failclus.mspx
> nodes
> http://www.microsoft.com/technet/pro.../rllupnet.mspx
> up
> will
> each
> have
> to
>
>
|||"It will actually be an Inactive node used for failover. . . . Also when I
go to install SQL as a Failover will I need a dedicated Drive for the
install that is part of the SAN?"
I am not sure what you are asking. Are you trying to add an additional node
to an existing SQL Server failover instance or are you adding another node
in order to add another instance?
If you have a cluster, then you already have a Quorum drive visible to the
cluster and configured as a Disk cluster resource in the Default Cluster
Resource Group. You can use Cluster Administrator to add another node to
the cluster. After which, you attempt to move the Cluster Resource Group
from the existing node to the newly added node and then back again. If all
works out, then the Quorum drive will automatically be configured on the new
node. Move the Cluster Resource Group back to the original node.
Now, whether or not you are trying to add another node to an existing SQL
Server failover instance or installing a new instance, you install new and
manage existing instances with the SQL Server installation media and
program. Each instance will require a separate cluster resource group which
contains at least a Disk, IP, and Network Name resource. You begin by
adding the disk resource. Since it is in a separate resource group, it MUST
be a uniquely identified and shared disk visible to all nodes in the cluster
that will be potential owners of this resource. The SQL Server installation
program will automatically create and manage the IP and Network Name
resources.
When only dealing with a 2-node, single or dual instance SQL Server failover
cluster, the installation is not too complicated; however, when you are
dealing with a multi-node, multi-instanced cluster, the choices and, thus,
the installation and configuration gets more complicated. You have to
decide which nodes will be possible owners of which instances. Those nodes
will need to be added as members for those instances, each will receive
copies of the binaries for those instances only, each Resource Group will
need to have a unique Network Name resource, but each instance that can run
on specific nodes must also be unique by instance name.
You'll have to decide if every node can host resources, configure a
round-robin solution, or an N x I solution. You will also want to consider
configuring a dedicated Resource Group, separate Disk, IP, and Network Name,
for the single MS DTC instance.
If you are running the IA-64 version of SQL Server, the installation is
completely different; so, you would need to do some additional research.
Sincerely,
Anthony Thomas

"Jeremey" <Jeremey@.discussions.microsoft.com> wrote in message
news:EAA547F9-8295-40BA-A088-2571C7D97F94@.microsoft.com...
> Hi Anthony,
> It will actually be an Inactive node used for failover. All servers are
> Win2k3 Ent SP1 with the latest patches. We are not adding any new LUNs to
> the group just a new Node at which I will need to at least be able to
connect
> to the Quorum drive. I will try the suggestions you gave me. Also when I
go[vbcol=seagreen]
> to install SQL as a Failover will I need a dedicated Drive for the install
> that is part of the SAN?
> Thanks again for all your help, this is the first more than two node SQL
> cluster that I've ever worked on.
> Jeremey
> "Anthony Thomas" wrote:
of[vbcol=seagreen]
instance or[vbcol=seagreen]
drive,[vbcol=seagreen]
and[vbcol=seagreen]
Disks"[vbcol=seagreen]
all[vbcol=seagreen]
disk.[vbcol=seagreen]
alignment.[vbcol=seagreen]
http://www.microsoft.com/resources/d...e_exa_oori.asp[vbcol=seagreen]
relevant[vbcol=seagreen]
format[vbcol=seagreen]
add it[vbcol=seagreen]
the[vbcol=seagreen]
out.[vbcol=seagreen]
server[vbcol=seagreen]
public[vbcol=seagreen]
want[vbcol=seagreen]
will[vbcol=seagreen]
Inactive[vbcol=seagreen]
http://www.microsoft.com/technet/pro.../failclus.mspx[vbcol=seagreen]
adding[vbcol=seagreen]
http://www.microsoft.com/technet/pro.../rllupnet.mspx[vbcol=seagreen]
Heartbeat[vbcol=seagreen]
on[vbcol=seagreen]
we[vbcol=seagreen]
do[vbcol=seagreen]

makepipe and readpipe on cluster

I am trying to see if named pipes connection works on my cluster, sql server
2K.
I have tryied the 2 utilities, makepipe and readpipe.
The connection works if, when using readpipe, I use the physical server name.
But our configuration is on MSCS 2 nodes Cluster.
If I use the virtual name the connection fails.
Is that normal?
Please advise.
Franco
Did you have any problem connecting to a SQL instance in the cluster via
named pipes? If so, why not just use osql to test your named pipe
connectivity.
Linchi
"Franco" wrote:

> I am trying to see if named pipes connection works on my cluster, sql server
> 2K.
> I have tryied the 2 utilities, makepipe and readpipe.
> The connection works if, when using readpipe, I use the physical server name.
> But our configuration is on MSCS 2 nodes Cluster.
> If I use the virtual name the connection fails.
> Is that normal?
> Please advise.
> Franco

Majority Node Set SQL cluster Or ?

S it possible to set up SQL cluster like MNS, without having common share
drives ? or without vendor specific solution.
Target is to have high-availability, but have no SAN or share SCSI drives
available.
I can set up mirroring, at the moment these is the only solution that I
thing is possible. Both servers are in same location.
MNS only removes the need for a shared Quorum Disk, you still need disks for
your SQL data to be shared disks
"Mr.B" <MrB@.discussions.microsoft.com> wrote in message
news:39BE540E-15FA-4CB9-811D-2B1279B0CA61@.microsoft.com...
> S it possible to set up SQL cluster like MNS, without having common share
> drives ? or without vendor specific solution.
> Target is to have high-availability, but have no SAN or share SCSI drives
> available.
> I can set up mirroring, at the moment these is the only solution that I
> thing is possible. Both servers are in same location.
>
|||Thank you. I will set up miroring.
"Edwin vMierlo [MVP]" wrote:

> MNS only removes the need for a shared Quorum Disk, you still need disks for
> your SQL data to be shared disks
>
> "Mr.B" <MrB@.discussions.microsoft.com> wrote in message
> news:39BE540E-15FA-4CB9-811D-2B1279B0CA61@.microsoft.com...
>
>

Majority Node Set cluster

If you want to deploy a SQL 2005 geocluster or a cluster without shared
storage for quorum - there is only Windows 2003 Ent Edition "Majority Node
Set" option.
Majority Node Set implies three nodes for failover - in case one node is
failing.
But I have 2 SQL 2005 nodes and no shared storage - how we can implement in
this situation SQL Majority Node Set Cluster ?
There is possible? There are other possibilities ?
Thank you in advance,
You can look into SQL Server 2005 database mirroring, although for
automatic failover you will still need a witness server. There are
lesser levels of availability (high protection and high performance
operating modes) you can build with SQL 2005 Database mirroring that
only require 2-Nodes, however the failover is always done manually. It
is more of a DR solution than an HA solution. Check out the details
here...
http://www.microsoft.com/technet/pro.../dbmirror.mspx
http://www.databasejournal.com/featu...le.php/3440511
You can look into third party solutions such as Neverfail and
SteelEye's LifeKeeper (my employer) which provide both the replication
for data protection and application/system level protection using just
two servers. Another benefit of 3rd party clustering is that it will
work fine with Standard versions of Windows and SQL, Enterprise is not
required.
You can request a 30 day free trial from our website at
www.steeleye.com.
David A. Bermingham, MCSE, MCSA:Messaging
Senior Systems Engineer
www.steeleye.com
anonymous wrote:
> If you want to deploy a SQL 2005 geocluster or a cluster without shared
> storage for quorum - there is only Windows 2003 Ent Edition "Majority Node
> Set" option.
> Majority Node Set implies three nodes for failover - in case one node is
> failing.
> But I have 2 SQL 2005 nodes and no shared storage - how we can implement in
> this situation SQL Majority Node Set Cluster ?
> There is possible? There are other possibilities ?
> Thank you in advance,
|||"anonymous" <anonymous@.discussions.microsoft.com> wrote in message
news:88AA523B-7A76-4E5C-B507-468EF6DF7B02@.microsoft.com...
> If you want to deploy a SQL 2005 geocluster or a cluster without shared
> storage for quorum - there is only Windows 2003 Ent Edition "Majority Node
> Set" option.
> Majority Node Set implies three nodes for failover - in case one node is
> failing.
> But I have 2 SQL 2005 nodes and no shared storage - how we can implement
> in
> this situation SQL Majority Node Set Cluster ?
> There is possible? There are other possibilities ?
MNS covers _only_ the quorum. If you want to cluster SQL 2005, you will need
shared storage for the database and transaction logs.
You can use 3rd party software for this, but if you do, then you must depend
on them for your support, too.
Another option you have with SQL 2005 is to use Database Mirroring. See
books online for additional information.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp

Majority Node Set and SQL Server 2000

Hello
I was doing some research about Windows 2003 Cluster with Majority Node Set
and SQL Server 2000 EE support.
I found some messages on the newsgroup saying that SQL Server 2000 is not
supported on MNS cluster.
I also read on SQL Server 2000 High Availability book on page 158 that SQL
Server support both cluster types (MNS and Shared Storage).
I also did not find any official documentation on the Microsoft web site
staying that SQL Server 2000 clustering is not supported on a MSCS configured
with MNS.
Because of that I am a lit bit confused.
Anyone know any document com Microsoft where its possible to read that SQL
Server 2000 is not supported on an MNS cluster?
I belive that is not possible to install SQL Server 2000 virtual server on a
MNS quorum because the SQL Server needs a shared storage for the system and
user databases. But It would be possible to install the WIndows 20003 cluster
on a MNS and them install SQL Server 2000 virtual server on a shared storage
(SAN)?
Regards
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
Hi
Have a look at the last post on this
http://groups.google.com.au/group/mi...f897c8231ea9f2
http://groups.google.com.au/group/mi...c936d07ef15cda
http://groups.google.com.au/group/mi...a0220e71bc8008
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/
"Carlos Eduardo Selonke de Souza"
<CarlosEduardoSelonkedeSouza@.discussions.microsoft .com> wrote in message
news:529DAF39-A3E6-4451-AE79-B91695CDFE7F@.microsoft.com...
> Hello
> I was doing some research about Windows 2003 Cluster with Majority Node
> Set
> and SQL Server 2000 EE support.
> I found some messages on the newsgroup saying that SQL Server 2000 is not
> supported on MNS cluster.
> I also read on SQL Server 2000 High Availability book on page 158 that SQL
> Server support both cluster types (MNS and Shared Storage).
> I also did not find any official documentation on the Microsoft web site
> staying that SQL Server 2000 clustering is not supported on a MSCS
> configured
> with MNS.
> Because of that I am a lit bit confused.
> Anyone know any document com Microsoft where its possible to read that SQL
> Server 2000 is not supported on an MNS cluster?
> I belive that is not possible to install SQL Server 2000 virtual server on
> a
> MNS quorum because the SQL Server needs a shared storage for the system
> and
> user databases. But It would be possible to install the WIndows 20003
> cluster
> on a MNS and them install SQL Server 2000 virtual server on a shared
> storage
> (SAN)?
> Regards
> --
> Carlos Eduardo Selonke de Souza
> http://carlos.geekbunker.org