cleanVm: incorrect backup size in metadata
-
Pinging @florent
-
I found the same message in the Backup log as well:
Xen Orchestra, commit 9b9c7
Several VMs are being backed up, this message only appears for one.
-
Last time I asked @florent it's a non-problematic message, I think it will be removed in the future.
-
It's really confusing. I'm using the current version of XO and I see this in the log:
The value in the file mentioned is the expected value and the backup file itself is the appropriate size:
Xen Orchestra, commit 494ea
As if XO calculates the value before the backup is complete and the file has time to grow a bit?
-
Hi,
Last time I asked the answer was "you can safely ignore this". Keeping @florent in the loop though.
-
@olivierlambert All my backups have and have had them all the time. I ignore them but it's quite disconcerting
-
It looks like this issue occurs only when saving the backup to non-block storage. When saving to block storage ("Store backup as multiple data blocks instead of a whole VHD file: ON"), it does not, at least in my environment.
-
Hi,
Last back up have always this message (XOA 5.109).
And incrémental backup have a Full Size... (ticket open on support)
-
@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.
-
This post is deleted! -
@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. -
@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.
-
@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.
