XO Community edition backups dont work as of build 6b263
-
@marcoi @olivierlambert OK, I think I've found the problem, and a fix... at least for the error I was seeing...
- If you create a new backup with the method Delta Backup, it will fail with the error posted previously.
- Activate the "Use NBD to transfer disk if available" switch
- Save the backup job
- Deactivate the "Use NBD to transfer disk if available" switch
- Save the backup job
- Run the backup job again
This time,
journalctldoesn't log any errors, and the export task can be seen:
My guess is, that even though by default the "Use NBD to transfer disk if available" switch is shown as inactive when creating a new backup job...
...in reality NBD is switched on by default. Activating and deactivating the switch presumably creates an entry in the job that specifies NBD shouldn't be used.
It would be interesting to know if anyone else can replicate this behaviour, or if it's just something odd in my setup?
-
@RobWhalley nice work, I am testing it right now
-
@RobWhalley Thanks! It looks like that fixed it for me.
-
@florent Thanks for taking a look, much appreciated!
@siemsenit Glad to help! I can't claim credit though, @marcoi pointed out the mention of NBD in the logs
-
@RobWhalley
It works for me too. -
you're right, preferNbd default value is not the same on the front and the back, we'll fix it
Most of the backup issue are solved by either removing the snapshot, or having it fa enough so thaht the next backup will be a base one, with all the data
I am still not reproducing the nackup stuck issue after this commit https://github.com/vatesfr/xen-orchestra/commit/3c8efb4dc3e1cb3955521063047227849cfb6ed3
-
@RobWhalley I think in the beginning i had that option enabled in my backup jobs, but found it was a hassle to move VMs between hosts with it on so i turned it off for all backups. Might be why my jobs worked because i had already done that switch in the past.
-
@RobWhalley
That worked for me as well.I created a new XenOrchestra VM with commit 3c543.
Enabling and disabling NBD on the backup job did the trick.
Thank you and everyone else for your efforts and digging into the matter.
Regards
Marc -
@RobWhalley Thank you... Works for me as well, good job!
Have a great day everyone.
-
@RobWhalley saved the day
We are still working on it to better understand why it fixes and improve the situation -
found it , there was not one, but 2 bugs
albeit small they were putting the xo backup in a incorrect state
the fix is here, and will be merged as soon as possible and then released as a patch for xoa users
https://github.com/vatesfr/xen-orchestra/pull/8780really thank you everyone for the information
-
@florent Great work, thanks for the fixes
