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

    Potential bug with Windows VM backup: "Body Timeout Error"

    Scheduled Pinned Locked Moved Backup
    66 Posts 16 Posters 12.6k Views 16 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.
    • nikadeN Offline
      nikade Top contributor @CodeMercenary
      last edited by

      @CodeMercenary alright, thanks for replying. I tried some more, but still getting the same error, on linux as well as windows vm's so im at lost here.

      P 1 Reply Last reply Reply Quote 0
      • P Online
        Pilow @nikade
        last edited by Pilow

        @nikade Hey Nikade,

        Did you try to create a new job that will do a new chain ? Just for test.

        nikadeN 1 Reply Last reply Reply Quote 0
        • nikadeN Offline
          nikade Top contributor @Pilow
          last edited by

          @Pilow We tried that as well, same problem 😞

          Also tried with a VM on the same newtork, just another VLAN, and we're seeing the same thing. At first we figured it was because one of the xcp-ng's was on a remote site which is connected through an IPSEC VPN, but that wasn't the case.

          poddingueP 1 Reply Last reply Reply Quote 0
          • poddingueP Offline
            poddingue Vates 🪐 @nikade
            last edited by

            Reviving this one because it never really got a clean ending. The fix for the Body Timeout Error on full backups went into xapi-project/xen-api#6786 and shipped with the March 2026 8.3 maintenance updates.

            @nikade, back in March, you mentioned still hitting it on both Linux and Windows VMs even after updating. Is that still the case for you on current versions? And anyone else who landed here: are you still seeing it, or did the update sort it out?

            Mostly trying to work out whether there's still something to chase or whether we can call this resolved. I'm not deep enough in the backup internals to say for sure, so your real-world results would tell us far more than anything I could guess. Thanks!

            last-genius opened this pull request in xapi-project/xen-api

            closed stream_vdi: Only process allocated clusters for VHD and QCOW on XVA export #6786

            G nikadeN H 3 Replies Last reply Reply Quote 1
            • G Offline
              Greg_E @poddingue
              last edited by

              @poddingue

              I need to update a few things and then I plan on trying to see if this was fixed for me. I think I only had 2 Windows machines that were a problem, and only on machines that had a larger disk and were basically empty. The counting zeros seemed to lead to a time out. Just haven't had the time to look at much of anything lately.

              1 Reply Last reply Reply Quote 1
              • nikadeN Offline
                nikade Top contributor @poddingue
                last edited by

                @poddingue My colleage managed to workaround the issue by re-installing the lab on other hardware, I think it is now Cisco UCS-servers. It was HP ProLiant-servers before.

                Maybe it was an issue with some of the NIC or firmware, im not really sure, but it works now.

                1 Reply Last reply Reply Quote 1
                • Tristis OrisT Offline
                  Tristis Oris Top contributor
                  last edited by

                  I get this error with each metadata backup run, but every time it fail on different pool. Only 1 failed pool at once.

                  aa7af767-9150-4e99-a483-5d02524678bb-image.jpeg

                  P 1 Reply Last reply Reply Quote 0
                  • P Offline
                    pierrebrunet Vates 🪐 XO Team @Tristis Oris
                    last edited by pierrebrunet

                    @Tristis-Oris Hi,
                    Can you upload your complete logs from one of these jobs, please? You can DM me if you prefer 🙂

                    1 Reply Last reply Reply Quote 1
                    • H Offline
                      Hex @poddingue
                      last edited by

                      @poddingue I have asked our engineers for feedback. We have left one big VM with 1TB empty disk - and full backups are going without errors for one week.
                      So it seems issue is resolved.
                      I have to mention that during this time we have migrated to XCP-NG 8.3. and are using one of the latest XO builds.

                      poddingueP 1 Reply Last reply Reply Quote 2
                      • poddingueP Offline
                        poddingue Vates 🪐 @Hex
                        last edited by

                        That's excellent news, thanks a lot for the feedback! 🎉

                        1 Reply Last reply Reply Quote 1

                        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
                        • First post
                          Last post