Hi Dojo,
Currently, on my customer's (single-node) DMA, I am facing exactly the same Backup issue as described in this Dojo question:
I am getting the
"Backup job had errors. !! Backup-process failed, see logging for details. Unspecified error (-2147467259)"
notice, and in my case, the Backup log file "C:\Skyline DataMiner\Backup\Backup_2025-07-02_...log" shows up
2025-07-02 13:01:12|1 errors occurred during backup
2025-07-02 13:01:12|- An error occured when dumping the elastic database. Error:
(not specifiying any Error here)
And the Elastic Backup logfile "C:\Skyline DataMiner\Backup\ElasticBackup_2025-07-02_...log" contains the message such as
2025-07-02 12:58:16|No YML file found
But I don't know where ElasticBackup.exe expects the YML file. I have installed/configured OpenSearch (on the local Windows, it's a Staging DMA) and, apart from this Backup issue, it seems to be running properly.
@Alberto de Luca, @Wouter Demuynck:
So I was wondering if your issue was maybe same or similar. You were mentioning a misconfiguration in the database. Can you tell me what it was like?
(This way, I might be able to save both my time and a squad's time by not opening a DCP task.)
Or maybe has anybody else experienced this issue again in the meantime and can give a hint? Thanks.
Best Regards
Jörg
Hi all,
thanks to Wouter Demuynck, who has answered my similar question in the other Dojo task, I was led to the following insight.
Wouter suggested that the backup procedure complains about the absence of the YML file at this location:
C:\Program Files\Elasticsearch\config\elasticsearch.yml
Actually that's true. When offering the YML file there, ElasticBackup.exe finds it and tries the next steps. It parses the yml file but doesn't find paths to data and repo then and hence produces another error, leading to the same error code notice in Cube.
Playing around with this helped me to conclude that the backup procedure seems to rely on a legacy Elasticsearch installed on the DMA. With YML file in C:\Program Files\Elasticsearch\config\, data and repo in C:\ProgramData\Elasticsearch\, and so on.
However, following the instruction to use OpenSearch for newer DMA (my customer's -DMA runs 10.4.0), I had installed OpenSearch somewhere on the Windows system (as mentioned before - it's a staging DMA) and let the DMA point to it. That OpenSearch installation seems to work fine with the DMA, I can use LCA on DOM and other things, but it will probably never be backed up by the Cube backup procedure.
And I believe that this will never be supported, since 3-node-cluster for OpenSearch with backup procedure e.g. as described here
is the method of choice. Or, even better, probably STaaS 🙂
My main goal was to get rid of the annoying error notice in Cube. And my main interest is to backup the Cassandra database (SLDMADB), while just playing around with some features requiring OpenSearch, but not requiring an OpenSearch backup so urgently. Hence, as a workaround, I have just unticked the Elasticsearch respectively OpenSearch options to backup in the "Custom Backup" section in Cube.
Now the error notice is gone and my backup is good enough for the time being.
This novel might help anyone in the Dojo community, maybe not. In any case, I'll leave this question open for a while just in case anyone has additional input.
Cheers
Jörg