Change from Active\Active to Active\Passive Cluster

I have a SQL Server 2000 Cluster with Windows 2000 Server.
The Cluster was set up as a Active\Active and I would like to change it to
Active\Passive.
What do I need to change go from Active\Active to Active\Passive?
Thanks,
Hi
Active/Active vs Active/Passive in SQL server tems is not correct.
Active/Active = 2 SQL Server instances, one running on each node.
Active/Passive = 1 SQL Server instance, running on a Node, with the other
node doing nothing but waiting for a failover.
Uninstall one SQL server instance and you have what you want. Any reason you
want to do this?
Regards
Mike
"Joe K." wrote:

> I have a SQL Server 2000 Cluster with Windows 2000 Server.
> The Cluster was set up as a Active\Active and I would like to change it to
> Active\Passive.
> What do I need to change go from Active\Active to Active\Passive?
> Thanks,
|||Mike - Are you recommending not to run an active/passive cluster config?
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Active/Active vs Active/Passive in SQL server tems is not correct.
> Active/Active = 2 SQL Server instances, one running on each node.
> Active/Passive = 1 SQL Server instance, running on a Node, with the other
> node doing nothing but waiting for a failover.
> Uninstall one SQL server instance and you have what you want. Any reason you
> want to do this?
> Regards
> Mike
> "Joe K." wrote:
|||Hi
No, but the decision must be based on business requirements.
If you need 2 instances of SQL Server, run them.
At work, we use put 4-6 instances per node on a SQL Cluster (= 8-12 per 2
node cluster). Our perspective is that having one machine do nothing is a
waste of space and energy.
Single Instance (Active/Passive), from a licensing perspective is cheaper,
you only need to license the single node as the other node is DR and is not
active.
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/
"Todd" <Todd@.discussions.microsoft.com> wrote in message
news:90355A4B-87CE-4B14-8C2C-AC0D909D1981@.microsoft.com...[vbcol=seagreen]
> Mike - Are you recommending not to run an active/passive cluster config?
> "Mike Epprecht (SQL MVP)" wrote:
other[vbcol=seagreen]
you[vbcol=seagreen]
it to[vbcol=seagreen]
|||I agree Mike. At work we use all active/passive clusters (4 total clusters
with 2 nodes in each) and run only a single instance on each active node. We
are doing a mass db consolidation project now and will likely go the path of
a multinode cluster as that will best suit our business needs.
Do you run different coalition settings on your 4-6 instances per node?
Thanks,
Todd
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> No, but the decision must be based on business requirements.
> If you need 2 instances of SQL Server, run them.
> At work, we use put 4-6 instances per node on a SQL Cluster (= 8-12 per 2
> node cluster). Our perspective is that having one machine do nothing is a
> waste of space and energy.
> Single Instance (Active/Passive), from a licensing perspective is cheaper,
> you only need to license the single node as the other node is DR and is not
> active.
> 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/
> "Todd" <Todd@.discussions.microsoft.com> wrote in message
> news:90355A4B-87CE-4B14-8C2C-AC0D909D1981@.microsoft.com...
> other
> you
> it to
>
>
|||Hi
No, Same collation. For us, multi-instances are there for security (bank),
to keep everyone away from each other.
It also makes it easier to add more nodes if we need to, so we then move the
instances around.
Once you start to have more than 2 busy instances, you better have a decent
SAN (EMC, biiiig EMC's) that can sustain the throughput. Multi fiber cards,
multi paths etc.
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/
"Todd" <Todd@.discussions.microsoft.com> wrote in message
news:23520408-C115-496C-9D33-A5313C3424C2@.microsoft.com...
> I agree Mike. At work we use all active/passive clusters (4 total
clusters
> with 2 nodes in each) and run only a single instance on each active node.
We
> are doing a mass db consolidation project now and will likely go the path
of[vbcol=seagreen]
> a multinode cluster as that will best suit our business needs.
> Do you run different coalition settings on your 4-6 instances per node?
> Thanks,
> Todd
> "Mike Epprecht (SQL MVP)" wrote:
2[vbcol=seagreen]
a[vbcol=seagreen]
cheaper,[vbcol=seagreen]
not[vbcol=seagreen]
config?[vbcol=seagreen]
reason[vbcol=seagreen]
change[vbcol=seagreen]
|||I agree 100% with Mike. I run a large N-1 cluster (N Nodes, N-1 Instances)
so I have one stand-by node for three active instances. I have scripts to
change the cluster failover order depending on what maintenance is
happening. I also can change memory settings and collapse the cluster on a
single node during low activity times for host node maintenance. It takes a
few extra steps to manage a large, multi-instance cluster, but the same
principles apply.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:Ok8qLjeGFHA.3472@.TK2MSFTNGP09.phx.gbl...
> Hi
> No, Same collation. For us, multi-instances are there for security (bank),
> to keep everyone away from each other.
> It also makes it easier to add more nodes if we need to, so we then move
the
> instances around.
> Once you start to have more than 2 busy instances, you better have a
decent
> SAN (EMC, biiiig EMC's) that can sustain the throughput. Multi fiber
cards,[vbcol=seagreen]
> multi paths etc.
> 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/
> "Todd" <Todd@.discussions.microsoft.com> wrote in message
> news:23520408-C115-496C-9D33-A5313C3424C2@.microsoft.com...
> clusters
node.[vbcol=seagreen]
> We
path[vbcol=seagreen]
> of
per[vbcol=seagreen]
> 2
is[vbcol=seagreen]
> a
> cheaper,
is[vbcol=seagreen]
> not
> config?
the[vbcol=seagreen]
> reason
> change
Active\Passive?
>
sql

Change

Currently have a 2 node windows 2000 cluster, active/passive, with sql 2000
running a data vault that's controlled by node a. Would like to upgrade to
windows 2003, but run active/active with sql running on node b. To do this,
do I have to reinstall sql server? I'm at a loss and all help and any white
papers would be appreciated.
Thanks in advance.
Hi
Don't think of "active/passive" or "active/active", rather think of it as 2
nodes, with either one or 2 (or 3 or 4 etc) virtual servers.
Currently, you have 2 nodes, with one virtual server and you want to have 2
nodes with 2 virtual servers. Between the 2 nodes, there is a shared quorum
drive.
The virtual server you currently have has a name, an IP address and disk
groups associated with it. If you want an additional virtual server, you
need the same again, another name, another IP address and another set of
disk groups.
Only one node can own a disk group at a time, so it you have allocated all
the space on the SAN to one disk group, you do not have space to make more
virtual disks for the other node. You might need to buy higher capacity
drives, add drives or add another SAN, or reduce the size allocated to the
disk group that currently exists.
I have a strict policy. No OS Upgrades to clusters. Re-Installs only.
Especially if you have to re-do the disk groups, it gives you a chance to
re-do the cluster.
So, backup your databases to a safe place, off the SAN, wipe it, setup your
disks and then re-do the whole cluster.
Get to know the content on
http://www.microsoft.com/windowsserv...g/default.mspx
On the pages, there is a step by step on how to setup a SQL cluster:
http://www.microsoft.com/technet/pro.../failclus.mspx
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/
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:B2FC1873-54BB-40F8-B0BD-CA25597A35E9@.microsoft.com...
> Currently have a 2 node windows 2000 cluster, active/passive, with sql
2000
> running a data vault that's controlled by node a. Would like to upgrade
to
> windows 2003, but run active/active with sql running on node b. To do
this,
> do I have to reinstall sql server? I'm at a loss and all help and any
white
> papers would be appreciated.
> Thanks in advance.
|||I have a slightly different approach. I will allow an OS node upgrade,
mainly to find out compatibility issues, then I go back and rebuild each
node from scratch.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OIoWPIzLFHA.2492@.TK2MSFTNGP14.phx.gbl...
> Hi
> Don't think of "active/passive" or "active/active", rather think of it as
> 2
> nodes, with either one or 2 (or 3 or 4 etc) virtual servers.
> Currently, you have 2 nodes, with one virtual server and you want to have
> 2
> nodes with 2 virtual servers. Between the 2 nodes, there is a shared
> quorum
> drive.
> The virtual server you currently have has a name, an IP address and disk
> groups associated with it. If you want an additional virtual server, you
> need the same again, another name, another IP address and another set of
> disk groups.
> Only one node can own a disk group at a time, so it you have allocated all
> the space on the SAN to one disk group, you do not have space to make more
> virtual disks for the other node. You might need to buy higher capacity
> drives, add drives or add another SAN, or reduce the size allocated to the
> disk group that currently exists.
> I have a strict policy. No OS Upgrades to clusters. Re-Installs only.
> Especially if you have to re-do the disk groups, it gives you a chance to
> re-do the cluster.
> So, backup your databases to a safe place, off the SAN, wipe it, setup
> your
> disks and then re-do the whole cluster.
> Get to know the content on
> http://www.microsoft.com/windowsserv...g/default.mspx
> On the pages, there is a step by step on how to setup a SQL cluster:
> http://www.microsoft.com/technet/pro.../failclus.mspx
> 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/
> "Scott" <Scott@.discussions.microsoft.com> wrote in message
> news:B2FC1873-54BB-40F8-B0BD-CA25597A35E9@.microsoft.com...
> 2000
> to
> this,
> white
>
|||Thanks Mike and Geoff!!!!
It's pretty much what I figured, but was hoping not.
Again, THANKS!!!!
"Geoff N. Hiten" wrote:

> I have a slightly different approach. I will allow an OS node upgrade,
> mainly to find out compatibility issues, then I go back and rebuild each
> node from scratch.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:OIoWPIzLFHA.2492@.TK2MSFTNGP14.phx.gbl...
>
>