![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Is it possible to use Windows 2003 clusters to have 2 active nodes, each with a completely independent virtual server/instance of SQL 2000 and have them both fail over to 1 single failover node? This would mean I would ahve node 1/instance 1, node 2/instance 2, node 3/failover, and node 1/instance 1 and node 2/instance 2 both failver to node 3, and running both instances on the 3rd, failover node in the event of a hardware failure? I ask, because in Exchange, for example, you cannot do this since Exchange can only have 1 active virtual server running on a single node in a cluster of more than 2 nodes. thanks, Jason |
#3
| |||
| |||
|
|
-----Original Message----- Yes. I actually have a 4-node, 3 instance cluster that works just that way. SQL 2000 can go up to 4 nodes in a cluster. Windows 2003 Enterprise Edition can go to 8-node clusters. -- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org "Jason" <jdheltne (AT) sbcglobal (DOT) net> wrote in message news:elSgP4A8DHA.2480 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Is it possible to use Windows 2003 clusters to have 2 active nodes, each with a completely independent virtual server/instance of SQL 2000 and have them both fail over to 1 single failover node? This would mean I would ahve node 1/instance 1, node 2/instance 2, node 3/failover, and node 1/instance 1 and node 2/instance 2 both failver to node 3, and running both instances on the 3rd, failover node in the event of a hardware failure? I ask, because in Exchange, for example, you cannot do this since Exchange can only have 1 active virtual server running on a single node in a cluster of more than 2 nodes. thanks, Jason . |
![]() |
| Thread Tools | |
| Display Modes | |
| |