• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 226
  • Last Modified:

Why HW must be alike in an "Windows Server 2003 Cluster and Microsoft Exchange 2003" environment

We are about to setup a system where the HW are not alike in a windows 2003 clustered environment: local disk-system is not alike, different CPU, same BIOS, same machine "type". Will Exchange Server 2003 help us with this as Microsoft has worked with Excange to make it work "well" in a Clustered environment ? I.e. would you setup Exchange Server 2003 in such a clustered environment ?
1 Solution
Well, the hardware has not necessarily to be alike; the point/"problem" is that the *complete* cluster solution (that is server, HBAs, SAN, ...) in this exact combination, not just the single components, has to be cluster certified in order to have Microsoft support should you need it.
Everything else is basically irresponsible. A cluster is used to ensure extended uptime because of the failover. This requires all involved components (NICs, HBAs, multi-path drivers, SAN switches, storage, ...) to work closely and reliably together. In a setup you cobbled together yourself, this can not be guaranteed, and you're likely to have increased downtime due to troubleshooting the cluster instead of increased uptime.

The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now