Cluster groups are features of Windows Server 2003 and Windows Server 2008. You can install Exchange Server 2007 on the nodes of a cluster group and have the advantages of clustering available to your messaging environment. Exchange 2010, 2013, 2016, and 2019 do not support cluster groups.
Cluster continuous replication (CCR) configurations support active/passive mode.
AppManager for Microsoft Exchange Server and Exchange Online supports up to eight physical nodes for single copy cluster (SCC) configurations. For more information, see Section 2.11.3, Monitoring Resources on Cluster Nodes.
NOTE:If you have clusters set up on Exchange Server 2007 and you upgrade to Exchange Server 2010, 2013, 2016, and 2019, you must manually delete the Exchange2007 objects from the Navigation pane or TreeView in AppManager and run discovery again after you upgrade to Exchange Server 2010, 2013, 2016, and 2019.
Add the computers that represent the individual nodes of a cluster to the master view of an AppManager repository in Control Center. Then group the nodes by cluster.
For example, if EX2KSVR_1 and EX2KSVR_2 are the two nodes of an Exchange Server 2007 cluster, add each computer to the master view.
When you have added all node computers, create a server group, for example, EX2K_CLUSTER_1, and add each node computer to that group.
For more information about adding computers to the master view of a repository and creating server groups, see the Control Center User Guide for AppManager.
To discover resources in an Exchange Server 2007 cluster, run the following Discovery Knowledge Scripts in the order listed:
|
Knowledge Script |
Resources Discovered |
|---|---|
|
Discovery_NT |
Windows configuration and resources, such as memory, physical and logical disks, and CPU. |
|
Discovery_MSCS |
Microsoft Cluster Service configuration and resources, such as cluster services and nodes in a cluster. NOTE:The MSCS module is not mandatory to monitor the Exchange server cluster. It is only used if you want to monitor additional services for Microsoft Cluster configuration and resources, such as cluster services and nodes in a cluster. |
|
Discovery_Cluster |
Clustered Mailbox Server (CMS) objects. |
|
Discovery_Exchange2007 |
Exchange Server configuration and resources, such as services, server view, and protocols. When you discover Exchange resources, AppManager for Microsoft Exchange Server and Exchange Online lists each CMS that a computer can own as a child object of that computer, regardless of whether the CMS is active at the time of discovery. |
Use cluster-aware Knowledge Scripts on both physical and virtual server to monitor resources on each node in a cluster and on each CMS as it moves from node to node as a result of failover. The All_* Knowledge Scripts and the Knowledge Scripts that run on a Mailbox server can monitor Windows cluster resources. Microsoft supports clustering only on the Mailbox server role.
You can run the MBS_* Knowledge Scripts on physical and virtual nodes.
When you monitor a CMS, AppManager for Microsoft Exchange Server and Exchange Online associates the collected data with the physical node.
A Knowledge Script job running on a CMS collects data for that CMS and for the associated physical node.
A Knowledge Script job running on a physical node collects data for any CMS associated with that physical node.
If CMS1 is active on EX2KSVR_1 and CMS2 is active on EX2KSVR_2, the job creates two datastreams when you run the job on CMS1:
Datastream for CMS1
Datastream for EX2KSVR_1
When you run a job on EX2KSVR_1, the job collects data for CMS1. If CMS2 fails over to EX2KSVR_1 and you run a job on EX2KSVR_1, the job creates two datastreams:
Datastream for CMS1
Datastream for CMS2
If CMS1 is active on EX2KSVR_1, the job creates two datastreams when you run the job on CMS1:
Datastream for CMS1
Datastream for EX2KSVR_1
If CMS1 fails over to EX2KSVR_2, and you run a job on EX2KSVR_2 the job creates two datastreams:
Data stream for CMS1
Datastream for EX2KSVR_2