XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    cleanVm: incorrect backup size in metadata

    Scheduled Pinned Locked Moved Xen Orchestra
    14 Posts 7 Posters 912 Views 7 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      ScarfAntennae
      last edited by

       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?

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Online
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Pinging @florent

        1 Reply Last reply Reply Quote 0
        • abudefA Offline
          abudef
          last edited by

          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.

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Online
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Last time I asked @florent it's a non-problematic message, I think it will be removed in the future.

            abudefA 1 Reply Last reply Reply Quote 0
            • abudefA Offline
              abudef @olivierlambert
              last edited by abudef

              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? 🤔

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Online
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Hi,

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

                M 1 Reply Last reply Reply Quote 0
                • M Offline
                  manilx @olivierlambert
                  last edited by

                  @olivierlambert All my backups have and have had them all the time. I ignore them but it's quite disconcerting 😉

                  1 Reply Last reply Reply Quote 0
                  • abudefA Offline
                    abudef
                    last edited by

                    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.

                    1 Reply Last reply Reply Quote 0
                    • N Offline
                      noritaka971
                      last edited by

                      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

                      D 1 Reply Last reply Reply Quote 0
                      • D Offline
                        DustinB @noritaka971
                        last edited by

                        @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.

                        N 1 Reply Last reply Reply Quote 0
                        • N Offline
                          noritaka971
                          last edited by

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          • N Offline
                            noritaka971 @DustinB
                            last edited by

                            @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.

                            B 1 Reply Last reply Reply Quote 0
                            • B Offline
                              bufanda @noritaka971
                              last edited by

                              @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.

                              N 1 Reply Last reply Reply Quote 0
                              • N Offline
                                noritaka971 @bufanda
                                last edited by

                                @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.

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post