Summary
Advanced Recovery SnapVault backup of an Exchange 2010 3-node DAG fails, displaying an error in the job log similar to the following:192.168.1.211 4/24/2013 2:50:29 pm SNBAPP_004X java.lang.Exception: getDRSystemVolumesN: GetSystemVolumes failed, rc (-1), reason (Failed to open the cluster error -2147023143)192.168.1.225 4/24/2013 2:50:30 pm SNBAPH_126E Func(AHOpPfs:run): Exception (com.syncsort.bex.msg.bexException: <EXCEPTION CATEGORY=BEXEXCEPTION"><CODE>21005</CODE></EXCEPTION> )"
Symptoms
The job definition can be opened from the management console. Expanding the EXCH component under the virtual node displays all the databases. The following Windows application error events are noted on the active cluster node:
Log Name: Application
Source: MSExchangeRepl
Event ID: 3154
Task Category: Service
Level: Error
Description:
Active Manager failed to mount database <xxxx> on server <xxx.xxxx.xxx>. Error: An Active Manager operation failed. Error The database action failed. Error: An error occurred while trying to select a database copy for possible activation. Error: The database <xxxx> was not mounted because errors occurred either while validating database copies for possible activation, or while attempting to activate another copy. Detailed error(s):
An Active Manager operation failed. Error The database action failed. Error: An error occurred while trying to select a database copy for possible activation. Error: The database <xxxx> was not mounted because errors occurred either while validating database copies for possible activation, or while attempting to activate another copy. Detailed error(s):
Resolution
In this case, one of the DAG cluster nodes was removed from the active failover cluster membership. The Cluster service on this node may have stopped.
The error could also be due to the node having lost communication with other active nodes in the failover cluster. In that case, do the following:
- Open Failover Cluster Manager from the Active DAG node and notice one of the nodes is down.
- Determine the reason for the down condition and bring the node up.
- Run the backup again. If the cluster node is up and joined to the cluster, the backup should succeed.