Errors and recommended actions
The following table describes the problem that might occur.
Table: Error and recommended actions
Error message or cause | Explanation and recommended action |
|---|---|
CBR node not reachable. | The CBR node in the DSS cluster is not reachable. Recommended actions:
|
CBR RSA key mismatch. | The CBR node RSA key specified do not match with the RSA key provided by the CBR node. Recommended actions:
|
CBR is reachable, but some nodes not reachable. | Some of the nodes in the DSS cluster are not reachable. Recommended actions:
|
Invalid nodes in the cluster. Credentials are invalid. Apache Cassandra not installed. | The nodes in the clusters are invalid or unable be log in indicates the possibility that Apache Cassandra is not installed. Recommended actions:
|
CBR credentials mismatch. | The DSS cluster's credentials are invalid on the CBR node. Recommended actions:
|
DSS node credentials are invalid. | The credentials that specified for the DSS node are not valid. Recommended actions:
|
Discovery nodes not reachable. | The Discovery node for the Cassandra cluster is not reachable. Recommended actions:
|
Discovery node RSA mismatch. | The status of the cluster is Pending for approval. Recommended action: Approve the RSA key of discovery node. |
Discovery node credentials invalid. | The credentials of the Cassandra cluster are invalid for the discovery node. Recommended actions:
|
Apache Cassandra not installed on the discovery node. | The Apache Cassandra is not installed on the discovery node of the Cassandra configuration. Recommended actions:
|
Apache Cassandra cluster name not matched. | The discovery node belongs to a different cluster. Recommended actions:
|
Datacenter name not matched. | The data center name of the Cassandra nodes mismatch. Recommended action:
|
Cassandra Cluster pending approval. | One ore more nodes in the Cassandra cluster and RSA key require approval. Recommended action:
|
Cassandra nodes invalid credentials. | Cassandra cluster credentials mismatch with one or more nodes in the cluster. Recommended action:
|
The Cassandra DSS cluster and/or Cassandra production cluster goes into invalid status due to concurrent operations. | NetBackup can do only one operation such as discovery, validate, backup, restore, at any given point in time on the DSS and production clusters. If one operation is running, the other fails and put the cluster in invalid state. If the cluster is in invalid state while the previous operation is running, wait for the pervious operation to complete. Then retry the operation you previous operation like discovery, validation, backup now or restore. |
Discovery of more than one cluster take time and doesn't show the discovering status immediately. | NetBackup works, discovery one cluster at a time hence the state of the second cluster changes after the first one is complete and reflect the appropriate status after completion. |
Cassandra restore page becomes unresponsive for keyspaces/column families more than 300. | Use computer with higher configuration for example RAM size is 16GB or more. |
Incremental backup fails with Error 6. | Recommended action: Verify if the scheduled full backup is completed. Note: Full backup run with a use of Backup now is not considered as it is not linked to scheduled backup. |
Backup/restore does not work post primary cluster node failover. | Recommended action: For primary server cluster, after the fail-over of node, update the primary server's Note: NetBackup media server is used as the backup host. |
no java in (/sbin:/bin:/usr/sbin:/usr/bin) Java executable not found (hint: set JAVA_HOME) | Recommended action: Update the |
DSS or production cluster status goes into unknown state during cluster validation | Recommended action: Edit and update the credentials from Credential management page and perform the cluster validation again. Add new credentials from Credential management page and then select desired credentials from the existing credential list using Manage credential option in DSS or Apache clusters page. |