Issue of the week 8/17/2009

This issue deals with Antigen 9.x and clusters with Multiple Active Nodes.

You do not need the cluster resource on a single Active cluster.

There is a fix in Antigen 9.1 RU5 and Antigen 9 Service Pack 2 that addresses an issue when moving Active nodes to a passive node.

Below is an example of what you see when you have the issue resolved in RU5 or SP2

When the first Node is moved over to the passive node we set a registry key that identifies the database path for the engines and databases. In this example Server1 has its databases on G:\AntigenCluster

The store is then moved back to the original node and then server2 is moved to the passive.

Sever2’s database path is in F:\AntigenCluster

Most of the time Server2 will move the database path to the Passive cluster and everything works. Sometimes this process fails. You end up with a wrong database path and in this example server2 is on the passive with the database path still set to G:\AntigenCluster

This will cause us to initialize with no scan engines and no settings for our scanjobs.

The symptoms of this issue is as follows

End users cannot open or send mail.

Messages queue in Local delivery

The fix requires you to do one of the following to to create the cluster resource

1. Full uninstall (Pause passive nodes, uninstall from all active nodes and then passive nodes) and run a fresh install.

2. Upgrade to SP2 and do the following. Run Antutil.exe /disable and then Antutil.exe /enable on each active node (Pause passive nodes, bring exchange resources offline, leave CMS up.)

Both methods Require downtime