Delta Backup Changes in 5.66 ?
-
@julien-f said in Delta Backup Changes in 5.66 ?:
@s-pam we were not able to reproduce so far on our side. Also, most of the XO team (myself included) is on holidays until next week, thus I'm not sure we'll be able to fix it before.
If you are using an official XO appliance, you can rollback to the
stablechannel and if you are using XO from the sources, you can go back to a previous commit.Yea, I have a support ticket active for another issue, but this popped up now in the middle of it. But then I'll wait until next week before downgrating so you can have a chance to look at it through the support tunnel. I've changed the backup schedule to daily instead of hourly to save some space on the remote
. -
Not wanting to be a "me too" but I'm seeing exactly the same thing.
Some VM's (unfortunately in my case large ones) and doing daily fulls rather than deltas.
Backup taking 14 hours instead of 2 or 3.
Similar etup to @S-Pam with nfs as the remote target.
-
We are doing progress in the investigation. @florent will keep you posted!
-
@pnunn @S-Pam If you use the sources, can you try to use this branch
feat-add-debug-backupit's master with additionnal debug and a potential fix ( potential , because I can't reproduce it regularly in our lab)Then you can activate more debug by this
[logs] # Display all logs matching this filter, regardless of their level filter = 'xo:backups' # Display all logs with level >=, regardless of their namespace level = 'debug'in your config file ( should be in
~/.config/xo-server/config.toml -
@florent unfortunately not. We use XOA.
-
@s-pam it's a great choice
If you can launch a backup , I can connect through a support tunnel and deploy the fixthen you can launch the backup and we can celebrate the success of this fix
-
@florent said in Delta Backup Changes in 5.66 ?:
@s-pam it's a great choice
If you can launch a backup , I can connect through a support tunnel and deploy the fixthen you can launch the backup and we can celebrate the success of this fix
Do you mean a second XOA? I already have a support ticket+tunnel open on it. Originally due to failed incremental backups, but now it includes this issue with full backups being made when they shouldn't.
-
@s-pam this issue caused quite a few tickets, which one is yours ? I can connect right away
-
@florent said in Delta Backup Changes in 5.66 ?:
@s-pam this issue caused quite a few tickets, which one is yours ? I can connect right away
It is Ticket#774300
-
@s-pam I answered on the ticket and deployed the fix.
-
We seem to experience the same issues. We are on commit d3071. It seems that xoa mislables the backups as well.
Even though we enforced a full backup through the schedule option, it is labled as a delta in the restore process menu.
The xoa backup "log" in the interface shows full as well instead of delta and the amount of data transferred is clearly a full. -
I'm running XO as well, not from sources.. but today, everthing worked as it should??
Lets see what happens tomorrow.
-
I'm not sure if mine is an edge case or another "me too", but
d3071has partially fixed the always a full backup issue on my end.I'm not sure exactly what's going on, but this morning I did wonder if it's to do with having two delta backup jobs (backing up to two different remotes), and whether something strange was happening with the snapshots between the two jobs.
For example, from my backup report for the first backup to a local NFS remote:
Half an hour or so later, that same VM yields a full backup-sized transfer:
(Which, incidentally, I don't understand how it's a 3.33GiB transfer, when the VHD size on the SR is ~111MB and the output of
df -hon the VM shows 1.8GB used. I'm confused!)I'll roll onto
feat-add-debug-backupand see what that yields! -
@andrewreid XO team has released a new version 5.66.2 for XOA and new sources for the XO community that should fix most of the recent backup issue, so please update to latest and report back if needed.
