FAQs / Exchange 2003 / Clustering
01
Microsoft recommends Active/Passive clustering because it:
- Scales better
- sizes the same way as a stand alone Exchange server
- can have up to 8 nodes in the cluster
- always fails over to a fresh node
Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1102)
Categories: Exchange 2003/Clustering |
02
Active/Active clustering is only supported with a 2-node cluster limited to 1900 concurrent connections.
Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1103)
Categories: Exchange 2003/Clustering |
03
The Exchange services are automatically shutdown on failover so when fail back happens the services are automatically brought back online for a clean address space.
Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1104)
Categories: Exchange 2003/Clustering |
04
Exchange 2003 and Windows 2003, Standard Edition will run up to a 4-node cluster. Exchange 2003 and Windows 2003 Enterprise will run an 8-node cluster with at least one passive node.
Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1105)
Categories: Exchange 2003/Clustering |
05
Win2k3 Enterprise and Datacenter both support 8-node clusters. MSCS (Microsoft Clustering Services) is now available for high availability. NLB Manager allows the administrator to configure the NLB service in a central location thus avoiding mistakes from repetitive actions. For more information see the “Technical Overview of Clustering in Windows Server 2003” and “Windows Server 2003 Server Cluster Architecture” documents.
Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1106)
Categories: Exchange 2003/Clustering |
06
VM fragmentation is when the virtual memory becomes fragmented and can prevent stores form mounting. The 9582 event is the event that warns about this condition. For more information refer to “The Extensible Storage Engine Database Engine Contributes to Virtual Memory Fragmentation (324118)”
Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1107)
Categories: Exchange 2003/Clustering |