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

    Continuous replication fails every time

    Scheduled Pinned Locked Moved Xen Orchestra
    31 Posts 8 Posters 7.5k 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.
    • txsastreT Offline
      txsastre @rizaemet 0
      last edited by

      @rizaemet-0 could you tell me how have you reverted to 5.50.1 ? thanks

      rizaemet 0R DanpD 2 Replies Last reply Reply Quote 0
      • rizaemet 0R Offline
        rizaemet 0 @txsastre
        last edited by rizaemet 0

        @txsastre I'm taking snapshot of XO vm before every update. Simple revent it.

        Because it is from source so I have no support subscription. I recommend this to you.

        txsastreT 1 Reply Last reply Reply Quote 1
        • txsastreT Offline
          txsastre @rizaemet 0
          last edited by

          @rizaemet-0 thanks you've got the right. I already doing this, but I didn't know if you uninstalled it and installed a previous version.

          it was just curiosity. So I'm gonna rollback to a previous snapshot too.

          Thank you

          1 Reply Last reply Reply Quote 1
          • DanpD Offline
            Danp Pro Support Team @txsastre
            last edited by

            @txsastre I outlined the procedure here --

            https://xcp-ng.org/forum/post/18974

            txsastreT 1 Reply Last reply Reply Quote 1
            • txsastreT Offline
              txsastre @Danp
              last edited by

              @Danp thanks ! but I have rolled back to a previous version ( 5.50.1) and now I'm testing the backup again.

              1 Reply Last reply Reply Quote 0
              • F Offline
                Fungusware
                last edited by Fungusware

                Can any comment on the fact that all of these issues are caused because 'import_raw_vdi' doesn't support Chunked transfers?

                This used to be fine casuse the loophole that allowed a massive Content-Length has been closed.

                (here: xapi-project/vhd-tool@f978789#diff-a1476b2332c40710d3f1791146a29aeaL484 ).

                Regards.

                0 jonludlam committed to xapi-project/vhd-tool
                XSI-19 locate VHD footer based on file size
                
                I order to locate the footer in a VHD file or stream, the total length
                of that file or stream must be known. This commit passes it when it is
                known. This depends on a corresponding change in the ocaml-vhd library.
                
                Signed-off-by: Christian Lindig <christian.lindig@citrix.com>
                1 Reply Last reply Reply Quote 0
                • R Offline
                  RKENS
                  last edited by

                  I saw this note relating to ZFS: It is not yet possible to import, migrate or export a VDI to/from a ZFS SR

                  Could that be why my continuous replication is failing? I'm trying to replicate from one ZFS SR to another on a different server.

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

                    No, since few release, ZFS should support all operations.

                    1 Reply Last reply Reply Quote 0
                    • R Offline
                      RKENS
                      last edited by

                      That's too bad. I don't see where anyone really had any solution.

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

                        Your CR issue might be related to a XO bug on master, not too a XCP-ng issue 😉

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