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

    CBT: the thread to centralize your feedback

    Scheduled Pinned Locked Moved Backup
    455 Posts 37 Posters 409.1k 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.
    • 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 Online
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Today

          A 1 Reply Last reply Reply Quote 0
          • A Offline
            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 Offline
                    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 Online
                      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
                          • M Offline
                            manilx @manilx
                            last edited by

                            @manilx restart toolstack did it. Thx for pointing this out 🙂

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

                              @rtjdamen That was a big sprint 🌶

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

                                @olivierlambert indeed but the first version is here!

                                I allready noticed some strange behavior, when a backup job is running with both switches on (cbt and data destroy), the first run the job processes succesfull but some snapshots stay orphan after the job is finished and coalesced. @florent any idea what is causing this?

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

                                  @olivierlambert With today's update (feat: release 5.96.0, master 96b7673) things are working well again. I have not seen any Orphan VDI/snapshots or stuck Control Domain VDIs (but it may take time to test). Thanks to the Vates team!

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

                                    @Andrew need to do some more testing but second run does clean them out, keep u all posted on the results over the weekend!

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

                                      I did some digging on this orphan snapshots. i found this error in the backup logging for these vms

                                      Couldn't deleted snapshot data
                                      error
                                      {"code":"VDI_IN_USE","params":["OpaqueRef:d52c23f7-4008-45e0-9852-6ecb3aeb8567","data_destroy"],"call":{"method":"VDI.data_destroy","params":["OpaqueRef:d52c23f7-4008-45e0-9852-6ecb3aeb8567"]}}
                                      vdiRef
                                      "OpaqueRef:d52c23f7-4008-45e0-9852-6ecb3aeb8567"

                                      i do not see them currently on normal vms and also not on second run

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

                                        It worked just fine for me during an overnight unattended backup. I also did a manual backup to watch things.

                                        Couple questions:

                                        1. If NBD is used, is there a 100% chance that CBT will also be used, or is it possible to have a NBD backup without CBT?
                                        2. Can it be added to the xo-server-backup-reports emails that NBD/CBT was used?
                                        R 2 Replies Last reply Reply Quote 0
                                        • R Offline
                                          rtjdamen @ajpri1998
                                          last edited by

                                          This post is deleted!
                                          1 Reply Last reply Reply Quote 0
                                          • R Offline
                                            rtjdamen @rtjdamen
                                            last edited by

                                            It seems the orphan vdi is showing when the data_destoy fails, maybe the vdi is not yet ready? @florent Is this something you can look into? Maybe a retry when it fails?

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