@<1526734383564722176:profile|BoredBat47> , that could indeed be an issue. If the server is still running things could be written in the databases, creating conflicts
@<1523701070390366208:profile|CostlyOstrich36>
What are the Elasticsearch, Mongo and apiserver versions in the docker compose are? Backup will only work in this scenario when they are exactly the same between 2 systems.
Can a problem be that backups are made while ClearML was running, not stopped, like docs suggest? @<1523701070390366208:profile|CostlyOstrich36>
@<1523701070390366208:profile|CostlyOstrich36> I understand but the description of the error seems to indicate not about database conflicts but about connectivity to elastic by apiserver. I couldn't find info about this on the internet. I think I ruled out incosistent image versions. Are there any more suggestions? Thanks.
I don't think so. Just some info about cluster state in there
Versions in compose are:
image: allegroai/clearml:1
image: elasticsearch:7.6.2
image: mongo:4.4.9
I am not quite sure that backups were made on those versions. Is there a way to see service versions from backup?
Hi @<1526734383564722176:profile|BoredBat47> , do you see any errors in the elastic container?