XCP-ng

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    New Smart Backup failure

    Xen Orchestra
    backup xenorchestra smart backups
    7
    14
    303
    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.
    • V
      vmpr @Andrew last edited by

      I've got the same error for a delta job since the 11th of March. cheers Ringo

      1 Reply Last reply Reply Quote 0
      • olivierlambert
        olivierlambert Vates 🪐 Founder & CEO 🦸 last edited by

        Okay we found the issue, @florent will prepare you a branch ASAP so you can test and report 🙂 If it's OK, we'll merge in master!

        1 Reply Last reply Reply Quote 0
        • olivierlambert
          olivierlambert Vates 🪐 Founder & CEO 🦸 last edited by

          And it's merged! Please try again on latest master's commit!

          A 1 Reply Last reply Reply Quote 0
          • V
            vmpr last edited by

            great job guys on a saturday! I am just updating my xo but your response times are great, keep up the good work!

            1 Reply Last reply Reply Quote 1
            • J
              JVComputers last edited by

              WOW - I'm amazed and impressed at how quickly this was addressed, simply from a community forum post! Thank you to all! Everything is working, once again.fantastic

              1 Reply Last reply Reply Quote 1
              • A
                Andrew Top contributor 💪 @olivierlambert last edited by

                @olivierlambert Thanks! Master commit 5f2b1 looks good now. Continuous Replication works. Delta backup works. S3 backup works. Have a good weekend.

                florent 1 Reply Last reply Reply Quote 1
                • florent
                  florent Vates 🪐 XO Team 🔭 @Andrew last edited by

                  @Andrew yes , thank you
                  @JVComputers thank you for helping us fix it

                  1 Reply Last reply Reply Quote 1
                  • mguyatt
                    mguyatt last edited by olivierlambert

                    I had the same error and updated to the latest commit on the master branch which fixed the error. But I am now getting the following error and wondering if anyone else is seeing it as well? Can't even do meta or config backups at this point.

                    BACKUP.SMART_BACKUP is not defined in the AUTHORIZATIONS object

                    More details:

                    metadataBackup.runJob
                    {
                      "id": "473fb5d5-1a8e-4e1e-888a-55078f4a7638",
                      "schedule": "e8611046-3f4c-4f51-9cf2-671915c2abe7"
                    }
                    {
                      "message": "app.createUserConnection is not a function",
                      "name": "TypeError",
                      "stack": "TypeError: app.createUserConnection is not a function
                        at Jobs.apply (file:///opt/xo/xo-builds/xen-orchestra-202203161420/packages/xo-server/src/xo-mixins/jobs/index.mjs:283:30)
                        at Jobs._runJob (/opt/xo/xo-builds/xen-orchestra-202203161420/node_modules/golike-defer/src/index.js:85:19)
                        at Jobs.runJobSequence (file:///opt/xo/xo-builds/xen-orchestra-202203161420/packages/xo-server/src/xo-mixins/jobs/index.mjs:333:18)
                        at Api.callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202203161420/packages/xo-server/src/xo-mixins/api.mjs:314:20)"
                    }
                    
                    1 Reply Last reply Reply Quote 0
                    • olivierlambert
                      olivierlambert Vates 🪐 Founder & CEO 🦸 last edited by

                      Are you sure you did a rebuild after getting the latest commit?

                      1 Reply Last reply Reply Quote 0
                      • mguyatt
                        mguyatt last edited by

                        I did for sure. But I noticed that a new commit(886ff2cd7) was made literally in about the last hour and after updating again to that version all is good!

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