Developers of Xen Orchestra
@CodeMercenary Looking for in detail would need a support tunnel
it's probably a vdi that has been deeemed incorrect by the cleanup script. The easiest way to fix it in mirror backup is to delete the most recent backups of this VM on the target , they will be re transferred from the source.
If your retention is the same, you can even ourge all the backups of this VM on the target and restart the mirror backup
the mix shouldn't be an issue in itself
@robyt are you using full backus ( called "backup" ) on the source ?
because incremental mirror will transfer all the backups generated by a "delta backup" whereas it's the first transfer or the following delta
(our terminology can be confusing for now)
@olivierlambert I think you're right, we just wait for the XAPI field PV_drivers_detected of the restored VM's guest metrics to be true.
@icompit Thank you.
It seems that the backup process fails to get the file lock on the backup directory. Have you modified anything on your remote recently?
Also, could you tell me if this is happening on all of this job's runs, all of your backup runs, or if it only happened once on this specific backup job execution?
@StephenAOINS
This endpoint is not currently present in our REST API swagger, but we do plan to add it to the list of endpoints.
We are currently finalizing the migration of existing endpoints, the next step will be adding new ones.
We will keep you informed when it is available. Feel free to come back to us if you want to learn more and follow our blog posts.
have a good day 
@StephenAOINS Hello, I'm asking XO team about it.
@icompit The EEXIST error has appeared with @florent's recent work on backups. I think he's investigating this problem, but he his on vacations now, and will be back in two weeks.
If this causes too much trouble for you, for the moment I would recommend you to go back to a previous XO version.
I'm not familiar with the new "Unknown system error" you got. Could you give us the log of that backup job execution?
