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

    Backup status reporting failure when retry was successful

    Scheduled Pinned Locked Moved Backup
    4 Posts 2 Posters 98 Views 2 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.
    • T Offline
      tmk
      last edited by

      I have noticed an issue in the Xen Orchestra backup job status logic where if an individual VM backup failed for any reason, and was then retried and completed successfully on retry, it is still reported as a backup failure.

      This is seen in both the XO backup status for that job but it also sends a backup failure email, which includes the detail that the vm backup had to retry and was successful (but is still reported as an failure). Can anyone on the Vates team confirm if this is a known issue or if there is a fix in the works?

      Ideally, with any backup job run, if retries are enabled in the job and a VM backup needs to be retried for any reason, and then ends up completing successfully, the final state of the VM backup should be success. The current behavior just has us investigating failures that aren't really failures.

      firefox_OBmGyuEAyI.png

      olk_snGoU4OV1V.png

      Bastien NolletB 1 Reply Last reply Reply Quote 0
      • Bastien NolletB Offline
        Bastien Nollet Vates 🪐 XO Team @tmk
        last edited by

        Hello @tmk,

        Can you tell me which version of XO you are using?
        We made a modification on the task error handling a couple of weeks ago.

        T 1 Reply Last reply Reply Quote 0
        • T Offline
          tmk @Bastien Nollet
          last edited by

          @Bastien-Nollet

          The XOA that handles our backups is still on an older version, 5.113.2. We have separate XOs for day to day management and backup management as we found that if we ever ran into any issues that required a restart of the XO service or server it would cause some serious issues if backups were running.

          We haven't upgraded the XOA responsible for backups yet because this version has been very stable and any time we've encountered issues with backups in the past it's required a very serious time commitment to clean up problems with VDIs (orphaned snapshots, online coalesce not working properly) so we've been hesitant to upgrade that XOA yet.

          That's good to hear that it's been fixed though, which version of Xen Orchestra should we be looking for the fix to land in?

          Bastien NolletB 1 Reply Last reply Reply Quote 0
          • Bastien NolletB Offline
            Bastien Nollet Vates 🪐 XO Team @tmk
            last edited by

            @tmk

            I was able to reproduce the problem, so it seems the modifications we brought a couple of weeks ago didn't fix it.

            I'm working on a fix at the moment.

            1 Reply Last reply Reply Quote 0

            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