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

    CBT: the thread to centralize your feedback

    Scheduled Pinned Locked Moved Backup
    439 Posts 37 Posters 386.5k Views 29 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      The transition to CBT should be done smoothly and without any manual intervention. @florent will provide more details on how 🙂

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

        All tests with 2 vms were so far succesfull, no issues found in our lab. Good job guys!

        1 Reply Last reply Reply Quote 1
        • robytR Offline
          robyt @olivierlambert
          last edited by

          @olivierlambert how many time for us with precompiled XOA?

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

            Tomorrow 🙂

            R 2 Replies Last reply Reply Quote 1
            • R Offline
              rtjdamen @olivierlambert
              last edited by

              @olivierlambert sounds good!

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

                Things are looking good on my end as well.

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

                  @olivierlambert Looks like it's back to single threaded bottlenecks...

                  I see a lot of single core 100% utilization on the XO VM.

                  R 1 Reply Last reply Reply Quote 0
                  • R Offline
                    rtjdamen @Andrew
                    last edited by

                    @Andrew Hi Andrew, can't reproduce on my end, all cores utilized at the same time around 30 to 40 % for 2 simultanious backups.

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

                      @rtjdamen It happens when Continuous Replication is running. The source and destination and network can do 10Gb/sec.

                      I'll have to work on a better set of conditions and tests to replicate the issue.

                      I know it's slower because the hourly replication was taking 5-6 minutes and now takes 9-10 minutes. It's more of an issue when the transfer is >300GB.

                      Just feedback....

                      R 1 Reply Last reply Reply Quote 0
                      • R Offline
                        rtjdamen @Andrew
                        last edited by

                        @Andrew understood! We do not use that at this time.

                        1 Reply Last reply Reply Quote 0
                        • R Offline
                          rtjdamen @olivierlambert
                          last edited by

                          @olivierlambert Hi Olivier, do you have an ETA?

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

                            Today

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

                              @olivierlambert Running current XO master (commit 1ace3), using Backup and running a full backup to a NFS remote, it now ignores the [NOBAK] on a disk.

                              Also, if you cancel the export task the backup is still marked as Successful. I never tried that before so it may have always done that.

                              julien-fJ R 2 Replies Last reply Reply Quote 0
                              • julien-fJ Offline
                                julien-f Vates 🪐 Co-Founder XO Team @Andrew
                                last edited by

                                @Andrew Thanks for your feedback, we are currently investigating this issue, we have difficulties reproducing this issue though.

                                Also, if you cancel the export task the backup is still marked as Successful. I never tried that before so it may have always done that.

                                Yes, this is not supported, the task is only here for informational purposes.

                                1 Reply Last reply Reply Quote 0
                                • R Offline
                                  rtjdamen @Andrew
                                  last edited by rtjdamen

                                  @Andrew i tried the same on our end, changed one of the disk names to [NOBAK] in front but the disk is still processed. Not a big of a deal for us, we do not use this currenlty but wanted to confirm we see the same behavior.

                                  I also tested with a new vm, created 2 disks, added [NOBAK] in front of the diskname, ran backup job and both disks are exported.

                                  @olivierlambert are u still able to deliver the update to latest today?

                                  M olivierlambertO 2 Replies Last reply Reply Quote 0
                                  • M Offline
                                    manilx @rtjdamen
                                    last edited by

                                    @julien-f Updated to Xen Orchestra, commit 1ace3

                                    Running my delta backups now all worked without issues. Also Coalesces finished fine.

                                    The only thing I note is that there is always one (or +1) tasks showb when there is actually none running:

                                    ScreenShot 2024-07-05 at 15.14.25.png

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

                                      @manilx It may be a normal task that's hidden (like SR or ISO scan). Clear out the search box by just clicking on the X. It should show all tasks.

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

                                        @rtjdamen Yes 🙂

                                        R 1 Reply Last reply Reply Quote 0
                                        • R Offline
                                          rtjdamen @olivierlambert
                                          last edited by

                                          @olivierlambert just updated, we will run some jobs with snapshot destroy and will report the results

                                          Compliments to all involved fot this great improvement is such a short time!

                                          olivierlambertO 1 Reply Last reply Reply Quote 0
                                          • M Offline
                                            manilx @Andrew
                                            last edited by

                                            @Andrew ScreenShot 2024-07-05 at 17.39.23.png

                                            How do I get rid of this one?

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