Exchange 2007 supports the Single Copy Clusters (SCC) type, which is more or less identical to the traditional active/passive clusters we know from previous versions of Exchange. This means that a SCC-based cluster only provides service failover and still has a single point of failure when it comes to the databases, unless a shared storage solution that provides redundancy via other means is used in the environment. An SCC-based cluster...
using a fault-tolerant SAN is just as good as a CCR-based cluster in terms of data availability, but such a solution is much more expensive than a CCR solution.
Although it's possible to move the cluster resource group between the nodes using the Cluster Administrator console, you should always do so (as is the case with CCR-based clusters) using the Move-ClusteredMailboxServer CMDlet because the Move Group task in the Cluster Administrator console isn't Exchange 2007 aware.
Managing an Exchange 2007 Single Copy Cluster-based setup
Part 1: A basic Single Copy Cluster setup in Exchange 2007
Part 2: Configuring Single Copy Cluster (SCC) nodes and shared cluster disks
Part 3: Creating a Windows Server 2003 cluster for an Exchange SCC setup
Part 4: Installing Exchange Server 2007 clustered mailbox roles on SCC nodes
Part 5: Verify Exchange 2007 clustered mailbox server functionality
Part 6: Exchange 2007 Single Copy Cluster-based setup review
|This chapter excerpt from How to Cheat at Configuring Exchange Server 2007: Including Outlook Web, Mobile, and Voice Access, by Henrik Walther, is printed with permission from Syngress, a division of Elsevier, Copyright 2007.
Click here for the chapter download.