visual bug in backup data
-
hello there, still XOA 6.3.3 here.
since the last big XObackup & CR reworking, we have an annoying bug
This VM is 2.17Tb
how can be the KEY is 9.1Gb ?
In fact the KEY size is good, but when retention of 10 points is obtained, the merging of last incremental in the first KEY point of the chain erase the size.So in our restore view, data sizes are all wrong, based on the sum of this key + 9 inc
@florent could you do something about that ? -
Hey, thanks for flagging this. I think what may be happening is that after the merge at the end of the retention chain, the UI might be picking up the full VM size (2.17 TB) instead of the actual KEY file size on disk (9.1 GB).
If you can confirm the key file is genuinely 9.1 GB on your storage, that would point to a display bug rather than a data issue.
Could you please check, and if so, it might be worth opening an issue on the XO GitHub with the numbers? I'm not entirely sure of the exact mechanism here, so @Team-XO-Backend would know better than me. -
@Pilow Hi,
Thank you for your reporting! It should be fixed in the next version we are thinking releasing this month if no surprise happens. There is a big refactoring on the clean part which handles metadata (and size) updates. -
the size is really 2.17Tb, but showing last incremental size on the key
I'll wait for the patch, this is really a visual bug, backup is working okay.
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