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

    Continuous Replication fails with XO update (June-20)

    Scheduled Pinned Locked Moved Backup
    14 Posts 6 Posters 873 Views 5 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.
    • florentF Offline
      florent Vates 🪐 XO Team @Andrew
      last edited by

      @Andrew said in Continuous Replication fails with XO update (June-20):

      Here's part of the log....

                "message": "transfer",
                "start": 1718906431567,
                "status": "failure",
      

      HI Andrew,

      can you try this branch https://github.com/vatesfr/xen-orchestra/pull/7763 ?

      regards

      fbeauchamp opened this pull request in vatesfr/xen-orchestra

      draft fix(backups): handle undefined VDI #7763

      A 1 Reply Last reply Reply Quote 0
      • S Offline
        scot1297tutaio
        last edited by

        I am also having issues with Continuous Replication:

        ⚠️ the writer IncrementalXapiWriter has failed the step writer.checkBaseVdis() with error Cannot destructure property 'other_config' of 'undefined' as it is undefined.. It won't be used anymore in this job execution.
        ⚠️ Retry the VM backup due to an error
        ⚠️ the writer IncrementalXapiWriter has failed the step writer.checkBaseVdis() with error Cannot destructure property 'other_config' of 'undefined' as it is undefined.. It won't be used anymore in this job execution.
        Error: Cannot destructure property 'other_config' of 'undefined' as it is undefined.

        I am on commit a14c4 using XO from sources.

        Scot

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

          @scot1297tutaio please try the branch @florent gave 🙂

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            scot1297tutaio @olivierlambert
            last edited by

            @olivierlambert I updated to that branch and it is working again. Thank you!

            1 Reply Last reply Reply Quote 1
            • A Online
              Andrew Top contributor @florent
              last edited by

              @florent @olivierlambert That branch works again for me. No errors any more.

              D 1 Reply Last reply Reply Quote 1
              • D Offline
                Delgado @Andrew
                last edited by

                I can confirm I upgraded to this branch and replication works again.

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

                  Great news, this is helpful for our dev team, thanks for your feedback! Keep an eye on the PR to see when merged 🙂

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

                    @florent @olivierlambert While this fixes one problem it adds a new one.

                    I am now getting the error VDI must be free or attached to exactly one VM on more than one VM. Which is correct because the CR process (and also sometimes delta backup) is leaving a VM attached to the Control Domain.

                    This problem shows up under the Dashboard->Health page. Manually deleting these stuck VDIs resolves the backup issue.

                    Now that the backup/CR process checks for this condition it becomes more of a problem that the process leaves VDIs attached to the control domain.

                    So, this update does fix the other_config issue but adds checks for other unrelated problems that exist and need to be resolved (Stuck VDI on Control Domain).

                    A 1 Reply Last reply Reply Quote 0
                    • A Online
                      Andrew Top contributor @Andrew
                      last edited by

                      @olivierlambert Any updates on this issue?

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

                        Sadly I'm not supervising this part, maybe @julien-f is aware

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

                          @julien-f @florent I tried the current XO commit 818a5b7f5bf29c021bc1612608c607022bac9c2b and still have the same problems, so I went back to fix_sr_vdi_undefined.

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

                            Got it. We might ship that in a patch release if it's bundled in our tomorrow's latest XOA release.

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