About CCR systems
Applies to: Forefront Protection for Exchange
You must first install Microsoft Forefront Protection 2010 for Exchange Server (FPE) on the active node and then on the passive node. When you begin the installation on the passive node, the CMS should still be running on the active node; do not failover to the passive node.
You cannot perform a remote installation of a CCR cluster.
.gif "Note") Note: |
|---|
It is very important not to restart the system until FPE is installed on both the active and passive nodes. If you restart during the installation on an active node, the CMS will fail over to the passive node. Because FPE has not yet been installed on the passive node, the CMS will fail to go online, and the cluster becomes unstable.
When the Proxy Information page appears during passive node installation, you can leave the information blank, even if you filled it in for the active node. The cluster replication process overwrites the settings on the passive node with those of the active node.
Installation tips
Keep the following tips in mind when installing FPE on a CCR cluster:
Never configure FPE by connecting directly to the passive node of a CCR cluster.
The quarantine and incident databases are not replicated. To release an item from quarantine on the passive node, connect directly to the passive node. Do not make any other configuration changes.
After saving configuration changes on the active node, you must allow time for a replication cycle to complete before failing over to the passive node. The default replication cycle is 30 seconds for configuration files and five minutes for engines.
Do not configure FPE on the passive node separately. Configure it on the active node, and the replication cycle will copy all your configuration settings.
If you need to convert an existing CCR cluster node with FPE to a standalone server, FPE must be uninstalled and reinstalled.
The FPE replication service creates backup files on startup and whenever a transition from active node to passive node occurs. These files can be used for recovery if current configuration data is accidentally overwritten with older configuration data.
On a CCR cluster system, the Enable as an update redistribution server option is automatically selected in the Global Settings - Engine Updates pane. This option is required for successful engine updates on the cluster. Do not disable this option. If this option is disabled, you can select the Enable as an update redistribution server check box again to restore engine updates. Each engine will require a new update before it can be replicated correctly again.
Replacing a CCR cluster node
In the event that a CCR cluster node becomes damaged or unusable, it must be replaced with a new server.
To replace a CCR cluster node
Add the new server to the cluster as the passive node.
Install Microsoft Exchange Server on the passive node.
Install FPE on the passive node.
Note
Wait until one replication cycle has completed, also known as seeding, before permitting the node to become the active node. When the seeding is complete, the message "Successfully updated from the active CCR node (seeding successful)" is written to the event log.