Cassandra was mistakenly deleted, and now elements on our DataMiner system are in error. Our setup is a 1+1 configuration with one Cassandra server and one Elasticsearch server. Although we've reinstalled Cassandra, the data loss has caused all elements on the failover server of the DMS to be in error.
Additionally, there's a critical authenticator alarm, and the main DMA is in a better state compared to the failover server.
Has anyone experienced a similar issue or can provide guidance on how to resolve this?
Hi Curtis,
Thanks for sharing the details; this definitely sounds like a challenging situation.
With Failover enabled, the Cassandra nodes on both agents (main and backup) are configured to remain in sync to support seamless switching in the event of a fault. Reinstalling one of the nodes likely disrupted this synchronization, preventing the two nodes from meeting the conditions required for a successful failover. This would explain the element startup errors you’re encountering after switching to the failover agent.
Just to clarify - was only one of the Cassandra nodes reinstalled, or were both? And do you happen to have a recent full backup of your DataMiner system? Depending on what data is still intact (and if restoration is a viable option), there may be a way to recover functionality without complete data loss.
Given the complexity of the issue and the potential risk of further impact, I’d strongly recommend reaching out to your account manager and our technical support team (Contacting DataMiner Support | DataMiner Docs). They can evaluate the current state of your system and provide guidance to get everything back on track.
Let me know if this information is helpful or if you have any further questions.
Thanks for your response. I have reached out for further assistance now.