Cluster Move |
|
|
Cluster Move SPAMfighter Exchange Module is fully cluster aware - in the sense that the Windows Cluster controls the service status of the SPAMfighter service (started / stopped).
In case of system maintenance etc. on a cluster node that requires the Exchange Cluster to be moved to another node in the Windows Cluster, you will have to move the cluster through the Exchange Management Shell.
Because Windows Cluster Administration isn't fully Exchange 2007 cluster aware - it is important that you do not use the Windows Cluster Administration to move the Exchange Cluster. Instead, Exchange 2007 has it's own tools to administer the Exchange cluster - but these tools are not aware of any other cluster resources that are dependent on the Exchange cluster resources.
To overcome the above, SPAMfighter comes bundled with an enhanced version of the Move-ClusteredMailboxServer command - named Move-SfClusteredMailboxServer. This new enhanced command is identical to the standard command - but also ensures the "SPAMfighter Cluster Instances" is being moved.
Note: If you are using Exchange 2000 / 2003 - please refer to this guide instead
1. Open Exchange Management Shell
2. Use the Move-SfClusteredMailboxServer command
NOTE THE NEW NAME OF THE COMMAND
Example: Move-SfClusteredMailboxServer -Identity:My2k7Cluster -TargetMachine:Ex2k7Node2 -MoveComment:"Cluster Administration"
NOTE: YOU WILL HAVE TO ENSURE THAT THE SHARED DISK CLUSTER RESOURCE ALSO IS MOVED - IF NOT NEITHER EXCHANGE NOR SPAMFIGHTER WILL WORK PROPERLY.
Note: It is per design from Microsoft that the shared disk isn't moved automatically. |