cleanVm: incorrect backup size in metadata

[DustinB]

@noritaka971 said in cleanVm: incorrect backup size in metadata:

Hi,

Last back up have always this message (XOA 5.109).
And incrémental backup have a Full Size... (ticket open on support)

I've had this issue for months with XOA and I've been told to not worry about it. Surely there is some way to recalculate the size of the VM backup to address this warning.

[noritaka971]

This post is deleted!

[noritaka971]

@DustinB
The problem with this issue are not the message, but each incremental backup have a full size backup on small infrastructure (2/3To of VMs) this is a little problem, but on more larger (10To) it's beginning to be boring.

[bufanda]

@noritaka971 You sure it does always a full backup. I have this isuue for ages and looking at the backup protocols it's only doing the deltas, never a full backup when not supposed to.

[noritaka971]

@bufanda
I'm sure all my backup since this bug was appear in my system is Full backup, I don't know if the two issues are related but they appeared at the same time.

[k11maris]

I am seeing this message, too. This is the first time I try out delta backups. I only did one backup so far, so this is a full backup. Storage is NFS.

[udegel]

@k11maris Same on my side. Delta backup for all VMs show this message.

[hoh]

I got bored by this "cleanVm: incorrect backup size" warnings. See https://github.com/vatesfr/xen-orchestra/pull/9637 So far, the fix works fine in our infra, no more warnings.

Keeping @florent and @olivierlambert in the loop.

jhoustek opened this pull request in vatesfr/xen-orchestra

closed fix(backups): record actual incremental VHD size #9637

[manilx]

@hoh This is SOOO long in the tooth........... Always was annoying. Thx for findinf a fix, looking forward to it.

[poddingue]

Good news, I think this one's finally sorted: the cleanVm: incorrect backup size in metadata warning was fixed in XO 6.4.0 (released end of April) via PR #9637, which makes incremental remote backups record the actual VHD size instead of the slightly-off metadata value.
If you're on 6.4.0 or later, it should be gone, so worth confirming your version and upgrading if you're behind. @manilx, you were waiting on this one.