Information Necessary to perform Root Cause Analysis on Unity Failover
The Information needed to troubleshoot why a Unity server running versions 4.x, 5.x, and 7.x failed over:
Mandatory: Should be Included when Opening TAC SR Desired: Follow up Information that should be collected once Mandatory Information has been collected.
Unity failover normally occurs for a few possible reasons:
Call received on the secondary server
The secondary server loses communication with the primary server (primary does not respond for 30 seconds)
Failover is manually initiated using Failover Monitor
SQL replication failures
Slow MAPI interaction with exchange
Mandatory information to get:
GUSI Cab files from both servers. This will tell us why it failed over.
For full root cause analysis, the CCM and SDL Traces from all the nodes in the cluster are necessary.(if Unity is integrated with CM). Traces should span at least 30 minutes prior to the failure. Refer to this link for CM trace collection -