Generic Error When Running S3 Backups to Minio on Latest XO Build
-
We use Minio to store standard backups that use it as an S3 target.
It works fine running on xo-web 5.92.0 and xo-server 5.87.0 from commit https://github.com/vatesfr/xen-orchestra/commit/6e6886a6bac6d8672c775991eebb00c991e54cfc
But if I upgrade to the latest from https://github.com/vatesfr/xen-orchestra/commit/a5e9f051a2f80358f2decf67e8cba64f2dbcb937 causes a backups to terminate shortly after starting with a very unhelpful error:
{ "data": { "mode": "full", "reportWhen": "failure" }, "id": "1654646632287", "jobId": "a3eaece2-b377-4dba-b7f2-bd9b4bc3ca7c", "jobName": "Backups for Resources Tagged with \"Backups-Daily-7d-3AM\"", "message": "backup", "scheduleId": "dc5f892c-8427-43d3-9eeb-9d1c18bc8f47", "start": 1654646632287, "status": "failure", "end": 1654646634770, "result": {} }
I rolled back to our original build and its back to working.
I have run into this on another upgrade attempt in early May (I have a timestamped backup of that XOA build marked with that date indicating I rolled back then).
Let me know if there is anyother log I can try to fetch for this.
-
@creoleMalady This does not help you, but my setup works with MinIO S3 (current version minio_20220607003341.0.0_amd64.deb) and current XO commit a5e9f.
I'm running XO commit 379e4 (June 2nd) and it has been working correctly with Wasabi.
I updated XO to commit a5e9f (current master) on a second server and backup still works for me to MinIO.... Delta Backup as a full and as a delta with and without merge.