Solved579 views18th September 2023 2 Chris Glover [DevOps Advocate]654 4th September 2023 0 Comments Hi, I'm seeing this in my notice events Backup job had errors. !! Backup-process failed, see logging for details. Unspecified error (-2147467259) Any idea which log file will point me in the right direction? Thanks Marieke Goethals [SLC] [DevOps Enabler] Selected answer as best 18th September 2023 2 Answers ActiveVotedNewestOldest 1 Miguel Obregon [SLC] [DevOps Enabler]8.14K Posted 4th September 2023 5 Comments Hi Chris, Please check similar questions: Backup job had error Backup Failure Hope it helps! Marieke Goethals [SLC] [DevOps Enabler] Selected answer as best 18th September 2023 Chris Glover [DevOps Advocate] commented 5th September 2023 Hi Miguel. That helped a bit, but the error I’m having is not caused by anything mentioned there. In C:Skyline DataminerBackupBackup.log I found 2023-09-05 12:39:23|1 errors occurred during backup 2023-09-05 12:39:23|- An error occured when dumping the elastic database. Error: An invalid IP address was specified. Yet, checking the DB.xml is pointing ot the correct IP addresses for our Elastic cluster, and all nodes are accessible. Do you know where the backup mechanism is looking to find the elastic Ip address? Miguel Obregon [SLC] [DevOps Enabler] commented 6th September 2023 Hi Chris, I was investigating a bit further and I could not find a similar issue. However, the error ‘An invalid IP address was specified’ was found in other scenarios when the ElasticSearch cluster runs on IPv6 addresses. This issue was found in 10.2 CU2 and fixed in 10.2 CU11, 10.3.2 More information in DataMIner Docs: https://docs.dataminer.services/user-guide/Troubleshooting/Known_issues/KI_Elasticsearch_IPv6.html Could it be the case that you are running a version older than 10.2 CU11? Chris Glover [DevOps Advocate] commented 8th September 2023 We’re on 10.3.4 with no IPv6 Miguel Obregon [SLC] [DevOps Enabler] commented 8th September 2023 Hi Chris, In this case I would suggest to contact to our support team (email@example.com) so they can follow up this issue. Chris Glover [DevOps Advocate] commented 12th September 2023 Thanks Miguel You are viewing 1 out of 2 answers, click here to view all answers. Please login to be able to comment or post an answer.