Summary
An administrator installed SMEX on two Windows 2008 Exchange 2007 SP2 CCR cluster nodes, but did not install SMEX on the SCR Target server.
When performing a failover attempt to the SCR Target server, the failover procedure stated that it is unable to do so because there was a non-Exchange cluster resource in the cluster resource group for the server.
As a workaround, the administrator deleted the SMEX cluster resource to successfully perform the SCR failover to the standby cluster node. Eventually, the node failed and went back to the original clue nodes, but the SMEX resource was not in the cluster resource group and there was a need to confirm if SMEX was functioning properly.
You would like to know if the failover would be successful had the administrator installed SMEX on the SCR Target server.
Details
The failover would not have been successful had you installed SMEX on the SCR Target server. This is because there will be no SMEX resource created if the SCR is not activated during installation.
Since SCR is inactive without Exchange resources, SMEX will treat the SCR node as normal and will not create the SMEX resource in cluster administrator. However, everything else, including the SMEX services, will be created and started.
There is no standard procedure for cluster installation as it follows the procedure for a stand-alone setup. However, you can use of this procedure to failover the CCR over to the SCR:
- Delete the SMEX resource in cluster administrator.
- Perform the procedure to failover and activate the SCR with Exchange resources.
- Install SMEX to the SCR if you have not done so. Otherwise, you can follow the steps in this Knowledge Base article to manually create the resource:
- If you failed back to the CCR nodes, repeat Step 3 to manually create the SMEX resource on the Exchange EVS.
Without the SMEX resource created, SMEX will not scan anything in the cluster environment.Note: In some environments, one may have a Node and File Share Majority Quorum configuration (File Share Witness). In this setting, the resource type for SMEX may be appear differently from what is listed in the article mentioned above. It is possible to appear as "clusRDLLCCR". Therefore, if a user types "clusRDLL", it will give an error that the type does not exist.
