Friday, March 30, 2012

Replacing failed node with dissimilar hardware

I need to replace a node with a server that is not the same as the failed one. When the cluster was built the hardware was identical down to the positioning of the NIC and HBA. What are the consequences of this? It is a SQL 2000 server SP3a running on Win
dows 2000 Advanced server.
Thanks for any input.
Paul L
Its not a best practice or something that I ever like to do, but it will
work. So no real consequences to speak of.
Cheers,
Rod
"Paul" <paul_lane@.supplyworks.com> wrote in message
news:AE7B3C3A-82B4-4F64-AF85-7F2165B9CD5D@.microsoft.com...
> I need to replace a node with a server that is not the same as the failed
one. When the cluster was built the hardware was identical down to the
positioning of the NIC and HBA. What are the consequences of this? It is a
SQL 2000 server SP3a running on Windows 2000 Advanced server.
> Thanks for any input.
> Paul L
|||Not something I would do in production. But we do it in the lab all the
time. I have a Win2003 3+1 cluster with three different kinds of hardware
from two vendors. It works fine.
Linchi Shea
linchi_shea@.NOSPAMml.com
"Paul" <paul_lane@.supplyworks.com> wrote in message
news:AE7B3C3A-82B4-4F64-AF85-7F2165B9CD5D@.microsoft.com...
> I need to replace a node with a server that is not the same as the failed
one. When the cluster was built the hardware was identical down to the
positioning of the NIC and HBA. What are the consequences of this? It is a
SQL 2000 server SP3a running on Windows 2000 Advanced server.
> Thanks for any input.
> Paul L
|||The major consequence would be if there was a failure and you needed
support from Microsoft. Only cluster configurations on the HCL are
supported.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks for all of your input, I appreciate it.

No comments:

Post a Comment