<![CDATA[cleanVm: incorrect backup size in metadata]]> cleanVm: incorrect backup size in metadata path "/xo-vm-backups/db8b6e5f-6e3a-e919-f5c1-d097f46eb259/20240321T000510Z.json" actual 21861989376 expected 21861989888

e62efac1-bea2-4547-808c-e653f2636126-image.png

I've been having this warning for 3~ months, on all my VMs.
At first the difference was just a few bytes (if those are bytes), but now the difference seems to be growing.

Running XO from the sources, updated multiple times during those 3 months, and also updated yesterday, same warning still occurred during last night's backup.

Any ideas how to get rid of this?

]]>https://xcp-ng.org/forum/topic/8716/cleanvm-incorrect-backup-size-in-metadataRSS for NodeMon, 10 Aug 2026 08:19:52 GMTThu, 28 Mar 2024 09:11:19 GMT60<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Sat, 06 Jun 2026 22:44:47 GMT]]>@poddingue Not seeing it anymore ✌

]]>https://xcp-ng.org/forum/post/106039https://xcp-ng.org/forum/post/106039Sat, 06 Jun 2026 22:44:47 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Sat, 06 Jun 2026 18:27:24 GMT]]>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.

]]>https://xcp-ng.org/forum/post/106035https://xcp-ng.org/forum/post/106035Sat, 06 Jun 2026 18:27:24 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Thu, 26 Mar 2026 09:30:37 GMT]]>@hoh This is SOOO long in the tooth........... Always was annoying. Thx for findinf a fix, looking forward to it.

]]>https://xcp-ng.org/forum/post/103842https://xcp-ng.org/forum/post/103842Thu, 26 Mar 2026 09:30:37 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Thu, 26 Mar 2026 08:43:58 GMT]]>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.

]]>https://xcp-ng.org/forum/post/103840https://xcp-ng.org/forum/post/103840Thu, 26 Mar 2026 08:43:58 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Fri, 21 Nov 2025 07:32:04 GMT]]>@k11maris Same on my side. Delta backup for all VMs show this message.
Bildschirmfoto 2025-11-21 um 08.30.44.png

]]>https://xcp-ng.org/forum/post/99864https://xcp-ng.org/forum/post/99864Fri, 21 Nov 2025 07:32:04 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Mon, 03 Nov 2025 14:33:25 GMT]]>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.

]]>https://xcp-ng.org/forum/post/99183https://xcp-ng.org/forum/post/99183Mon, 03 Nov 2025 14:33:25 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Tue, 05 Aug 2025 13:07:55 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/96009https://xcp-ng.org/forum/post/96009Tue, 05 Aug 2025 13:07:55 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Tue, 05 Aug 2025 07:21:28 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/95996https://xcp-ng.org/forum/post/95996Tue, 05 Aug 2025 07:21:28 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Mon, 04 Aug 2025 13:10:43 GMT]]>@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.

]]>https://xcp-ng.org/forum/post/95968https://xcp-ng.org/forum/post/95968Mon, 04 Aug 2025 13:10:43 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Mon, 04 Aug 2025 12:47:10 GMT]]>@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)

693d7e11-d1c4-4bd7-80be-f421ce4136c9-image.png

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.

]]>https://xcp-ng.org/forum/post/95964https://xcp-ng.org/forum/post/95964Mon, 04 Aug 2025 12:47:10 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Sat, 02 Aug 2025 15:42:13 GMT]]>Hi,

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

693d7e11-d1c4-4bd7-80be-f421ce4136c9-image.png

]]>https://xcp-ng.org/forum/post/95929https://xcp-ng.org/forum/post/95929Sat, 02 Aug 2025 15:42:13 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Sat, 01 Feb 2025 07:36:35 GMT]]>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.

]]>https://xcp-ng.org/forum/post/89136https://xcp-ng.org/forum/post/89136Sat, 01 Feb 2025 07:36:35 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Fri, 31 Jan 2025 18:43:23 GMT]]>@olivierlambert All my backups have and have had them all the time. I ignore them but it's quite disconcerting 😉

]]>https://xcp-ng.org/forum/post/89125https://xcp-ng.org/forum/post/89125Fri, 31 Jan 2025 18:43:23 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Fri, 31 Jan 2025 18:27:37 GMT]]>Hi,

Last time I asked the answer was "you can safely ignore this". Keeping @florent in the loop though.

]]>https://xcp-ng.org/forum/post/89123https://xcp-ng.org/forum/post/89123Fri, 31 Jan 2025 18:27:37 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Fri, 31 Jan 2025 07:31:27 GMT]]>It's really confusing. I'm using the current version of XO and I see this in the log:

cbe19d73-1616-409e-8331-b8e36d2b3147-obrazek.png

The value in the file mentioned is the expected value and the backup file itself is the appropriate size:

48b22e8d-25da-4129-ac24-d67fef04df86-obrazek.png

eba47e81-c834-42a2-815a-a9849d4ca358-obrazek.png

Xen Orchestra, commit 494ea

As if XO calculates the value before the backup is complete and the file has time to grow a bit? 🤔

]]>https://xcp-ng.org/forum/post/89102https://xcp-ng.org/forum/post/89102Fri, 31 Jan 2025 07:31:27 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Sun, 12 May 2024 13:29:14 GMT]]>Last time I asked @florent it's a non-problematic message, I think it will be removed in the future.

]]>https://xcp-ng.org/forum/post/77186https://xcp-ng.org/forum/post/77186Sun, 12 May 2024 13:29:14 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Sun, 12 May 2024 09:38:30 GMT]]>I found the same message in the Backup log as well:

d8e8115b-5280-4d28-83d7-d78c4e65bcd1-obrazek.png

Xen Orchestra, commit 9b9c7

Several VMs are being backed up, this message only appears for one.

]]>https://xcp-ng.org/forum/post/77180https://xcp-ng.org/forum/post/77180Sun, 12 May 2024 09:38:30 GMT<![CDATA[Reply to cleanVm: incorrect backup size in metadata on Thu, 28 Mar 2024 10:13:15 GMT]]>Pinging @florent

]]>https://xcp-ng.org/forum/post/74389https://xcp-ng.org/forum/post/74389Thu, 28 Mar 2024 10:13:15 GMT