@olivierlambert Hmm. It may just be easier to do a restore and export. I tried doing a file restore of / but I get a Cannot GET error when trying to download the tgz. I don't see anything in the UI to indicate what the problem is or if it actually created the tgz.

@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?

@olivierlambert I agree, ping @thomas-dkmt

Great!

@florent Great work, thanks for the fixes

@frank-s yes please the more detailed the bug report is, the easier it is to fix

Workaround found here https://xcp-ng.org/forum/post/94626 Seems like turning "Use NDB to transfer disk if available" switch ON and save backup job, then turn the switch OFF and save backup job again, will fix the issue. Thanks to @RobWhalley and have a nice day everyone.

@DwightHat I am using xoa from sources and i updated it to the latest commit which seemed to fix it for me..

hmm, I found the solution, after I read here on forum. I enable this options and save and then disable and save and now is ok. Task is running again. It is running with last commit to So the problem is with these settings which may not exist in the task created before the update. [image: 1751377404079-05b77f69-6e87-49d2-9c62-d795a13d161a-image.png]

fixed in commit fcefa

Excellent!

Hello, I am asking XO team.

some news on these , we did some test and clearly if proxy lost connection we loose all the info.

I have wondered this myself. [image: 1750783454921-screenshot-2025-06-24-124344.png] { "id": "0mcapon47", "properties": { "name": "Schedule sequence", "userId": "dbf49297-78e4-48c1-a996-a159343f89fe", "type": "xo:schedule:sequence", "progress": 67 }, "start": 1750780800006, "status": "success", "updatedAt": 1750782845608, "end": 1750782845608 } [image: 1750783475725-screenshot-2025-06-24-124427.png]

@florent Expected: Backup A (disabled) run first Backup B (disabled) will run after Backup A Backup C (disabled) will run after Backup B Outcome: All three backups ran in sequence as expected Thank you Florent for the help here

Excellent news, thanks for the feedback!

Sorry I don't see any error, it's just a message from the GC. However, I have to admit I don't have time to take a deeper look myself. If you have support, might be the right time to open a ticket, alternatively someone will take a look when they can

@olivierlambert xe vdi-forget uuid=c6853f48-4b06-4c34-9707-b68f9054e6fc xe sr-scan uuid=6b24cd1c-22ad-0994-5b6b-a75389a6ddba xe vdi-list uuid=c6853f48-4b06-4c34-9707-b68f9054e6fc params=sr-uuid sr-uuid ( RO) : 6b24cd1c-22ad-0994-5b6b-a75389a6ddba yup, that worked, thanks

@florent Thank you.

Thank you for the update. Last night before I saw your replys that is exactly what i did. I purged the backup's for the two VMs from BackBlaze. The backup job completed successfully while copying over the previous backup images. [image: 1749549311956-screenshot-2025-06-10-055256.png]