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

    XCP-ng 8.3 public alpha πŸš€

    Scheduled Pinned Locked Moved News
    264 Posts 43 Posters 176.5k Views 39 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 Online
      olivierlambert Vates πŸͺ Co-Founder CEO
      last edited by

      jhansen About the disk excluded: I can confirm it's not a PEBKAC. At least, not you or myself, since I can reproduce the problem. I can't find anything in XO code base despite we announced it, so maybe the issue is a PEBKAC elsewhere in the XO team πŸ˜… I'll keep you posted!

      jhansenJ 1 Reply Last reply Reply Quote 0
      • stormiS Offline
        stormi Vates πŸͺ XCP-ng Team @ajpri1998
        last edited by stormi

        ajpri1998 said in XCP-ng 8.3 public alpha πŸš€:

        I have a minor feature request…
        Can we get the xen-cmdline (/opt/xensource/libexec/xen-cmdline) added to the default PATH? I don’t use it too often but having it would save me a google remembering? I’ve also added to my bashrc with the name xcl.

        I would rather have it symlinked from /usr/sbin or such rather than altering the default PATH. However, it's minor enough for now for me not to want to diverge from XenServer on this, so ideally we should try to push this change upstream. Unfortunately, this is a packaging matter and it's not the most open part of XenServer, so contributing there is hard. Not impossible, but requiring efforts that may be above the gain, here.

        If you want, you could still open an enhancement request on XCP-ng's bugtracker. Maybe others will join you and at some point maybe the gain will be bigger than the effort πŸ™‚

        Sorry, sometimes we must be lazy to keep time for bigger topics.

        1 Reply Last reply Reply Quote 0
        • jhansenJ Offline
          jhansen @olivierlambert
          last edited by

          olivierlambert

          Great relief, I was beginning to have doubts about myself 😨 πŸ˜€

          olivierlambertO 1 Reply Last reply Reply Quote 0
          • olivierlambertO Online
            olivierlambert Vates πŸͺ Co-Founder CEO @jhansen
            last edited by

            jhansen said in XCP-ng 8.3 public alpha πŸš€:

            olivierlambert

            Great relief, I was beginning to have doubts about myself 😨 πŸ˜€

            So, it works but ONLY for snap taken during a backup, not a manual snapshot πŸ™‚

            jhansenJ C 3 Replies Last reply Reply Quote 0
            • jhansenJ Offline
              jhansen @olivierlambert
              last edited by

              olivierlambert
              I'm trying that this weekend.
              Thanks in advance.

              1 Reply Last reply Reply Quote 0
              • jhansenJ Offline
                jhansen @olivierlambert
                last edited by

                olivierlambert
                Here as promised a test of the [NOBAK] function.

                About the SR:
                NVME Raid
                Size: 2.4 TB used of 5.5 TB total (2.9 TB allocated)

                About "SRV-Test" VM:
                0 "SRV-Test" "NVME Raid" 50GB /dev/xvda
                1 "[NOBAK] SRV-Test Drive" "NVME Raid" 1.5 TB /dev/xvdb

                Manual snapshot takes both drives and ignores the [NOBAK]
                Backup via Xo works, only the first drive is backed up.
                You can follow this under TASKS in the XO.
                Under "File Restore" in the XO there are no data for the second drive.

                So beautiful - so good. The idea would actually be to back up a server with very large drives partially.

                So I change my VM to the following:
                0 "SRV-Test" "NVME Raid" 50GB /dev/xvda
                1 "[NOBAK] SRV-Test Drive" "NVME Raid" 1.5 TB /dev/xvdb
                2 "[NOBAK] SRV-Test second test drive" NVME raid 2 TB /dev/xvdc

                My SR looks know:
                NVME Raid
                4.4 TB used of 5.5 TB total (4.9 TB allocated)

                Exactly the same result as the first test, both with the manual snapshot and with the XO backup.
                Actually, the manual snapshot should not work at all, because there is not enough space on the SR to include all the drives, but due to thin provisioning it works because the drives are almost empty.

                Now I'm filling the drives with data so I'm sure there isn't enough space on the SR for a full snapshot of all the data.

                As expected, I get the error message "The specified storage repository has insufficient space" when taking a manual snapshot Everything is understandable since the manual snapshot saves the entire VM and there is no space for the 3.5 TB snapshot on the SR.

                Now I make another backup with XO, which previously only backed up the 50 GB of the first drive.
                UPS ... After a few seconds, the error "SR_BACKEND_FAILURE_44(, There is insufficient space, )" and the backup was aborted.

                So, XO seems to first test whether a complete backup/snapshot can be created with all drives and then backs up the 50 GB of the first drive.
                In my opinion a bit suboptimal because it doesn't solve the problem to always have twice the space on the SR as you used, even if I only want to back up the system disk of a VM with a few GB, for example. 😒

                Conclusion of the test:
                A) Manual Snapshot with only part of drives ([NOBAK]), does not work.
                B) Backup with XO with only part of the drives ([NOBAK]), works, but only if there is enough space for a complete snapshot of the VM on the SR.

                Hope you can use with my little test for something. 😊

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Online
                  olivierlambert Vates πŸͺ Co-Founder CEO
                  last edited by

                  Do you mean that the VM snapshot space is computing with all disks despite we decided to ignore one? If that's the issue, then it's a XAPI bug/something that we should add in the first place πŸ™‚

                  jhansenJ 1 Reply Last reply Reply Quote 0
                  • jhansenJ Offline
                    jhansen @olivierlambert
                    last edited by

                    olivierlambert
                    Exactly, it looks like the snapshot of the entire VM is always calculated first. If there is enough space then only the selected drive is taken in the backup, if not the Backup is aborted.
                    In other words, only if you can take a manual snapshot of the VM, XO's backup will then only backup the selected drive.
                    It would be good if the backup only checked whether there was enough space for a snapshot of the selected drive.

                    1 Reply Last reply Reply Quote 0
                    • olivierlambertO Online
                      olivierlambert Vates πŸͺ Co-Founder CEO
                      last edited by

                      Okay so it's not on XO, but on XAPI then. psafont and BenjiReis I assume it's a basic check in VM.snapshot that's not doing the right computation since we can ignore disk πŸ™‚

                      jhansenJ psafontP 2 Replies Last reply Reply Quote 0
                      • jhansenJ Offline
                        jhansen @olivierlambert
                        last edited by

                        olivierlambert
                        Seems like that to me too. Let me know if you found a solution. I leave the test VM on my Xen server so that I can test again at any time.

                        1 Reply Last reply Reply Quote 0
                        • psafontP Offline
                          psafont @olivierlambert
                          last edited by

                          olivierlambert Snapshot is in essence a VDI clone, I don't see any checks being done before the filtering for ignored VDIs is done. And that is done pretty early on, not sure why there are operations affecting virtual block devices from ignored VDIs: https://github.com/xapi-project/xen-api/blob/master/ocaml/xapi/xapi_vm_clone.ml#L416

                          1 Reply Last reply Reply Quote 1
                          • olivierlambertO Online
                            olivierlambert Vates πŸͺ Co-Founder CEO
                            last edited by

                            I will try to reproduce it locally with xe and keeping you posted, thanks!

                            1 Reply Last reply Reply Quote 0
                            • olivierlambertO Online
                              olivierlambert Vates πŸͺ Co-Founder CEO
                              last edited by

                              Okay so it works with xe. I'll see with XO doing a backup now.

                              1 Reply Last reply Reply Quote 0
                              • olivierlambertO Online
                                olivierlambert Vates πŸͺ Co-Founder CEO
                                last edited by olivierlambert

                                I can't reproduce the bug with XO. Here is my test setup jhansen :

                                1x VM with 2 disks:

                                • 1x 10GiB disk on a SR with plenty of space
                                • 1x [NOBAK] 900GiB local LVM disk (thick) on a 1TiB SR (you can't snapshot the disk without SR disk space failure)

                                I did a delta backup with XO and it worked.

                                jhansenJ 2 Replies Last reply Reply Quote 0
                                • jhansenJ Offline
                                  jhansen @olivierlambert
                                  last edited by jhansen

                                  olivierlambert
                                  I will make a retry of the test.
                                  Is the drive empty or filled with data
                                  If the disk are empty it works for me to.

                                  1 Reply Last reply Reply Quote 0
                                  • jhansenJ Offline
                                    jhansen @olivierlambert
                                    last edited by

                                    olivierlambert
                                    by the way: which version of XO are you using, not that I am using an older one and that the cause is there.
                                    My drives are also local LVM so should be "Thick" too.

                                    1 Reply Last reply Reply Quote 0
                                    • olivierlambertO Online
                                      olivierlambert Vates πŸͺ Co-Founder CEO
                                      last edited by

                                      XOA on latest

                                      jhansenJ 1 Reply Last reply Reply Quote 0
                                      • jhansenJ Offline
                                        jhansen @olivierlambert
                                        last edited by jhansen

                                        olivierlambert
                                        Hello,
                                        I created a new SR and installed a new VM and
                                        installed a new XO.
                                        The last one was definitely the answer.
                                        It's working now, so as far as backup via XO goes.
                                        I tested everything extensively, with different VM, SR and different drive fill levels, all ok.
                                        A manual snapshot won't work, but that's what it is.
                                        My old XO installation, unfortunately I didn't write down the version, was from January. Also, when I reinstalled, I switched from stable to latest as you indicated.
                                        Unfortunately, I can't say whether the pure stable update or the change to latest was the solution.
                                        But the main thing is a happy ending. 😊
                                        Greetings Joerg

                                        1 Reply Last reply Reply Quote 2
                                        • lawrencesystemsL Offline
                                          lawrencesystems Ambassador
                                          last edited by

                                          I did some testing with the 8.3 and it all went smooth except for one thing. We did a backup of a VM on 8.3 and if we try and restore it to version 8.2 I get the error

                                          "IMPORT_INCOMPATIBLE_VERSION"
                                          

                                          which makes sense and it's just a lab system so nothing critical. Is there a way to bring it back to 8.2 or should I update the rest of my lab to 8.3? πŸ™‚

                                          1 Reply Last reply Reply Quote 1
                                          • olivierlambertO Online
                                            olivierlambert Vates πŸͺ Co-Founder CEO
                                            last edited by

                                            What kind of backup? Delta should work (CR and warm migration too). Only basic backup with XVAs aren't able to be restored on an older version (like many things in XAPI world, it's only forward compatible)

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