Cluster Configuration - Troubleshooting
This document provides information and resolutions for the following troubleshooting scenarios:
- Backup fails during index restore due to MediaAgent failover
- Cluster configuration fails for one or more remote cluster nodes
- Executable application errors during failover
- Removal of cluster configuration from Client Completed with Errors
- Services stop running after a failover on Linux clusters
- INS0029: Microsoft Cluster Configuration: The Cluster Group is not yet configured
Backup fails during index restore due to MediaAgent failover
A backup may fail if the MediaAgent enters the failover state while the scan phase is restoring an index from media. The reason for job failure will state that the index restore was not able to complete due to failover.
In such a situation, terminate the job and perform another backup.
Cluster configuration fails for one or more remote cluster nodes
After configuring the cluster group client, a message is displayed indicating that some remote cluster nodes failed to be configured with the cluster group client.
The cluster group configuration may fail to update a remote cluster node if the cluster node presents the following issues:
- Network related problems (node not reachable)
- SnapProtect services not running
In the cluster group client properties dialog box, you must try to associate the remote cluster nodes to the Cluster Group.
Use the following steps to force the cluster configuration on the remote cluster nodes. Note that this operation creates an update request for the client in the CommServe database.
- From the CommCell Browser, go to the Client Computers node, right-click the Cluster_Group_Client and then click Properties.
- On the Cluster Group Configuration tab of the Client Computer Properties dialog box, click the Force Sync configuration on remote nodes check box and then click OK.
- In the Information dialog box, click OK.
Executable application errors during failover
Executable application errors have been observed on the originating active node during a failover. Once the new node takes over, the jobs will continue and complete. On rare occasions, an archiveindex.exe application error may corrupt the index and the backup cannot recover. In such a situation, kill the job and perform another backup.
Removal of cluster configuration from Client Completed with Errors
When a client computer is removed from the cluster group, all cluster settings are removed from the CommServe and client computer. If the CommServe fails to remove the cluster settings from the client, use the following steps to resolve this issue:
- Add the client back to the cluster group.
- Resolve the issues in the client that caused the failure. Check the failure reason stated in the error message received during the cluster configuration update. For example, <Connection to remote machine [machine_host_name] refused. Please check that the services are running on the remote machine.>
- Remove the client again from the cluster group.
Services stop running after a failover on Linux clusters
During a failover on Linux clusters, services on the node that takes over may be killed by cluster services. To ensure the services are restarted on the new node, add commands to start services to failover scripts.