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

    Backup don't work in 5.74.x

    Scheduled Pinned Locked Moved Xen Orchestra
    5 Posts 2 Posters 279 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.
    • robytR Offline
      robyt
      last edited by olivierlambert

      Hi, i've upgraded to 5.74 at 9/1 but then backup stop his work (the process remain at start).
      I see 5.74.1, i've upgraded (the old process is closed by upgrade) but nothing..
      i've started one backup, the lolg say:

      {
        "data": {
          "mode": "full",
          "reportWhen": "always"
        },
        "id": "1662361878014",
        "jobId": "9726d27c-6718-4323-b804-f054461b0741",
        "jobName": "Backup IMAP",
        "message": "backup",
        "scheduleId": "cf9db42b-e53d-404d-8b2b-95acb8fb51e3",
        "start": 1662361878014,
        "status": "pending"
      }
      

      Pending for...?

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

        Hi,

        There's 0 chance we can assist without more context. Are you using XO from the sources or XOA? Which edition?

        robytR 2 Replies Last reply Reply Quote 0
        • robytR Offline
          robyt @olivierlambert
          last edited by robyt

          @olivierlambert xoa, channel in xen orchestra latest.
          I always upgrade from xoa, never by source
          10d72038-1a22-4228-99f2-d25110dd7d00-immagine.png

          for the new imap VM i've the correct async.vm.snapshot call for the old backup, no call for the backup from 9/1

          ../xensource.log.8.gz:Aug 29 00:00:06 ctx6 xapi: [debug||17186116 HTTPS 91.102.48.67->|Async.VM.snapshot R:d999bc56b63f|audit] VM.snapshot: VM = 'bf73a0d2-63c2-c6ed-b7df-f9833404ec8a (New IMAP)'; new_name = '[XO Backup Backup IMAP] New IMAP'
          
          1 Reply Last reply Reply Quote 0
          • robytR Offline
            robyt @olivierlambert
            last edited by robyt

            @olivierlambert i've tried the Microsoft rule and i downgrade to 5.73 (nothing change) and the reboot xoa VM.
            now work fine 🙂

            now i do some backup job and reupgrade to 5.74

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

              If you use XOA, I would strongly suggest to open a support ticket. This way, we can investigate properly on your XOA and see what's going on.

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