Backups not working
-
Hi,
Can you try with XOA stable then latest and see if it works? This way it could help to pinpoint the culprit.
-
Update - I got XOA working trying backups now.
I deployed XOA my initial try had expired so i create new account. Registered XOA got it updated but when i clicked on backups it was still locked down. Now am stuck here...
-
Backups are running and completing with XOA.
-
-
Just saw that post. Just restored backup of xo and going to try.
-
Reverted back to commit c8f0a and backups are working.
-
@acebmxer Yeap, latest build introduced a bug in the backups.....
-
same issue going to disable backup for now until either bug fixed or i figure out how to go back to an older version.
update - went to Xen Orchestra, commit fb9bd and backup working again.
-
Has anyone tried turning off delta, and turning off compression?
Not ideal, but its how I'm dealing with some different issues (windows with big empty disks).
-
@Greg_E
I didnt try any changes to backup settings to test if any form of the backups would work on the latest commit. I just went back to an earlier version to perform backups using original settings. -
Might be interesting to pinpoint the exact problematic commit so we got a fix on Monday
-
@olivierlambert Happened between commit 19412 and commit 6b263.....
-
@olivierlambert Pretty sure the problem originates from this PR.
-
It may be related to the other topic, but I see a few things :
-
invalid HTTP header in response body. There is an issue while trying to download the disk. The XO logs ( journalctl ) should contains lines ith the
xo:xapi:vdikey regarding this.
It may be worth to tests without purge snapshot , if this error reoccur -
SIGTERM is probably more an out of memory issue on the backup worker. How muck memory does your XO have ?
-
-
@florent said in Backups not working:
It may be related to the other topic, but I see a few things :
-
invalid HTTP header in response body. There is an issue while trying to download the disk. The XO logs ( journalctl ) should contains lines ith the
xo:xapi:vdikey regarding this.
It may be worth to tests without purge snapshot , if this error reoccur -
SIGTERM is probably more an out of memory issue on the backup worker. How muck memory does your XO have ?
I am pretty sure both this post and - https://xcp-ng.org/forum/topic/10970/xo-community-edition-backups-dont-work-as-of-build-6b263/12 are the same problem....
To answer your question my XO has 6GB ram set.
Edit - Also note my backups were failing local nfs backup storage.
-
-
Backup done to NFS share
Xen Orchestra, commit fb9bd - backup work
Xen Orchestra, commit 6b263 - backup broken
Xen Orchestra, commit 1a7b5 - backup working
looks like the issue might been resolved with the latest build.
-
@marcoi said in Backups not working:
Backup done to NFS share
Xen Orchestra, commit fb9bd - backup work
Xen Orchestra, commit 6b263 - backup broken
Xen Orchestra, commit 1a7b5 - backup working
looks like the issue might been resolved with the latest build.
Thank you for the update. I will update as well and report back.
-
@marcoi Confirmed: commit 1a7b5 backing up again without issues.
-
Confirm commit 1a7b5 backups completed successfully.
-
Excellent news, thanks for the feedback!
