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

    XOA 5.107.2 Backup Failure via SMB and S3 (Backblaze)

    Scheduled Pinned Locked Moved Backup
    8 Posts 3 Posters 100 Views 3 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.
    • planedropP Offline
      planedrop Top contributor
      last edited by

      This is a new one, just updated XOA to 5.107.2 and now my backups are no longer working.

      I have support and can put in a ticket, but figured it's better to try here first.

      I am getting an error: Fail to connect to any Nbd client on the backups to Backblaze and on my SMB backups I just get a Footer1 !== footer2 error.

      What's important here is that it's only about half my VMs, and this is a single host setup, so the NBD client issues don't really make sense to me, unless I'm misunderstanding something about NBD.

      Anyone else seeing issues with backups after this update?

      Also not seeing anything consistent, not like an issue with Windows VMs in specific, it seems random.

      planedropP 1 Reply Last reply Reply Quote 1
      • planedropP Offline
        planedrop Top contributor @planedrop
        last edited by

        Going to give it more time, but restarting all the backups seems to have fixed the issue. Unsure why they would fail once and then resume just fine though.

        planedropP 1 Reply Last reply Reply Quote 0
        • planedropP Offline
          planedrop Top contributor @planedrop
          last edited by

          Still seeing this issue, trying to pinpoint it but haven't had any luck. It seems like each VM is about a 50/50 chance if it fails or succeeds, but the logs don't really lead me to anything and there's no consistent reason why it would be happening that I can find.

          This is only since going to 5.107.2 as well, wasn't happening on the previous version (which I unfortunately don't recall the version number of).

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

            Do you have the issue on stable release channel?

            planedropP 1 Reply Last reply Reply Quote 0
            • planedropP Offline
              planedrop Top contributor @olivierlambert
              last edited by

              @olivierlambert Good question, I am on Latest by mistake in this environment actually.

              Is it safe to roll back to Stable channel even though I am already on latest?

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

                Yes it should be safe 🙂

                planedropP 1 Reply Last reply Reply Quote 0
                • planedropP Offline
                  planedrop Top contributor @olivierlambert
                  last edited by

                  @olivierlambert I will give this a shot and report back. It may be a day or so, one of the backups is still running (very large VM over S3 so takes a while) but once it's done I will go back and see if the failures go away.

                  1 Reply Last reply Reply Quote 1
                  • R Offline
                    ravenet
                    last edited by

                    I was seeing similar broken backups in 5.107. Reverting to 5.106.4 seems to have resolved so far. Have a case open with logs submitted

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