Backing up from Replica triggers full backup
-
I am on it , thanks for all the informations
-
@flakpyro could you test this branch ?
https://github.com/vatesfr/xen-orchestra/pull/9635/commits -
@florent Just gave this branch a shot, trying to run replication job after running a backup job no longer results in a full replication but just fails with:
-
Retrying the job after the above failure results in a full replication and a new VM being created just as before.
-
@flakpyro you probaby had multiple job/schedule on the same schedule
I reworked the code and pushed an update and added a doc with the edge cases : https://github.com/vatesfr/xen-orchestra/pull/9635/changes#diff-ef545af2ad06f2759c1a3787f266108b3b2cbc203bc8071bbd847278f3e6a5f0 (will be on doc xo when merged )
-
@florent Since both jobs were test jobs that i have been running manually, i do have an unnamed and disabled schedule on both that does look identical, so i unintentionally did have multiple jobs on the same schedule. I have since named the schedule within my test job so to each is unique.
Updating to "f445b" shows improvement:
I was able to replicate from pool A to Pool B, then run a backup job which was incremental.
I then ran the replication job again which was incremental and did not create a new VM!
Unfortunately though after this i ran the backup job again which resulted in a full backup from the replica rather than a delta, not sure why. The snapshot from the first backup job run was also not removed, leaving 2 snapshots behind, one from each backup run.
I then tried the process again. Ran the CR job, which was a delta (this part seemed fixed!) then ran the backup job after, same behavior, a full ran instead of a delta and the previous backup snapshot was left behind leaving the VM looking like:
So it seems one problem solved but another remains.
-
Happy to report from my limited testing that as of this morning this appears to be fixed in master.
-
@flakpyro yes this one : https://github.com/vatesfr/xen-orchestra/pull/9635
fixed this morning in our work branch, and merged this after noon . We also explicited some edge cases here : https://github.com/vatesfr/xen-orchestra/blob/master/%40xen-orchestra/backups/docs/VM backups/incrementalReplication.md (that will probably be ported to the main doc shortly )
thank you for your input
closed feat(backups): improve incremental replication #9635
-
@florent Here's one more thing that needs improvement related to full backups running when it should be a delta.
I am running a CR job between two servers (single server pool for each). Each time the CR delta job would say it was falling back to a full backup without a reason or error.
I had CBT and NBD selected. It did not matter if it deleted the snapshot or not. It always ran a full backup.... The problem/solution I found was the server did not have any interface with NBD enabled. Once I enabled the management interface as NBD then delta backup/CR worked correctly.
The backup job config says NBD, if available. Not being available seems to cause an issue.
It would be nice to have the delta backup not fail if there is no NBD interface, or have it give a warning/error so you know there's an issue. Or it should work as advertised and not use or require NBD that's not available.
-
@Andrew the NBD warning is probably doable.
the other solution is not : NBD is mandaotry to use CBT ( the fallback with export can't work without a real snapshot )
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login