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

    XO Backup [NOBAK] for full backups

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    38 Posts 13 Posters 10.0k Views 10 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.
    • julien-fJ Offline
      julien-f Vates 🪐 Co-Founder XO Team @olivierlambert
      last edited by

      Hey everyone, [NOBAK] should work for all types of backup: Rolling Snaphost, Disaster Recovery, Continuous Replication, Full Backup and Delta Backup.

      Unfortunately, due to the way the snapshot process is implemented in XCP-ng, ignored VDIs will still be snapshotted before being deleted, which takes time and space unnecessarily, but we have discussed with the XCP-ng team and they are working on improving this 🙂

      In the meantime, XO tries to work around this by temporary detaching these VDIs from the VM during the snapshot, but this only work when the VM is halted (see offline backup in the advanced settings of a backup job).

      C B 2 Replies Last reply Reply Quote 0
      • C Offline
        CptHyper @julien-f
        last edited by CptHyper

        Hi does the Backup job still create the Snapshot (and therefore required time and space) when not doing an offline backup or has this been improved by now ?

        1 Reply Last reply Reply Quote 1
        • B Offline
          bnerickson @julien-f
          last edited by

          @julien-f said in XO Backup [NOBAK] for full backups:

          Hey everyone, [NOBAK] should work for all types of backup: Rolling Snaphost, Disaster Recovery, Continuous Replication, Full Backup and Delta Backup.

          Unfortunately, due to the way the snapshot process is implemented in XCP-ng, ignored VDIs will still be snapshotted before being deleted, which takes time and space unnecessarily, but we have discussed with the XCP-ng team and they are working on improving this 🙂

          In the meantime, XO tries to work around this by temporary detaching these VDIs from the VM during the snapshot, but this only work when the VM is halted (see offline backup in the advanced settings of a backup job).

          Ironically enough in my case, the VM I have that has a passthrough disk attached to it (a VDI I would like to [NOBAK]) is the VM that is setup as the remote for the backup job in XOA. So shutting it down wouldn't exactly work 🙂 .

          That being said I'm sure I could implement a workaround, but is there a feature request or tracking ticket URL somewhere where I can track XCP-ng team's work on this issue?

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

            I don't remember the status about this. I'm adding @marcungeschikts so he can tell us where it is in the backlog, when he's back from holidays 🙂

            marcungeschiktsM 1 Reply Last reply Reply Quote 0
            • marcungeschiktsM Offline
              marcungeschikts Vates 🪐 Project mgmt @olivierlambert
              last edited by marcungeschikts

              ☑ Done in XO Release 5.71 delivered in May, this year.

              5.71Release Note

              Internal Ref. only NOBAK support for all backup modes with snapshots

              B 1 Reply Last reply Reply Quote 0
              • olivierlambertO olivierlambert marked this topic as a question on
              • olivierlambertO olivierlambert has marked this topic as solved on
              • B Offline
                bnerickson @marcungeschikts
                last edited by

                @marcungeschikts I understand that this issue has been solved by halting a VM before taking the snapshot. Per this comment by @julien-f , "[...] but we have discussed with the XCP-ng team and they are working on improving this", is there an issue or feature request or ticket to track XCP-ng's work to improve the implementation so that halting a VM is no longer required?

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

                  Not sure to understand. The potential XAPI side improvement is to allow a VM.snapshot command to add extra parameters, excluding some disks.

                  You don't need to halt a VM to make a snapshot, it's completely unrelated. Maybe I'm missing something? 🤔

                  1 Reply Last reply Reply Quote 0
                  • marcungeschiktsM Offline
                    marcungeschikts Vates 🪐 Project mgmt @bnerickson
                    last edited by

                    Hi @bnerickson ,

                    The xcp-ng part to Exclude VDI from snapshot has been done on XAPI project and can be seen in github https://github.com/xapi-project/xen-api/issues/4551 , but will be only embedded in xcp-ng 8.3 planned around 6 month (+/- 3).

                    For the XO part, [Backup] Use ignore_vdis param when snapshotting, I will see with the XO Team and Olivier to synchronize the delivery

                    benjamreis created this issue in xapi-project/xen-api

                    closed [Feature proposal] Ignore some VDIs when snapshoting a VM #4551

                    B 1 Reply Last reply Reply Quote 2
                    • B Offline
                      bnerickson @marcungeschikts
                      last edited by

                      @marcungeschikts Thanks, that's perfect!

                      M 1 Reply Last reply Reply Quote 0
                      • M Offline
                        MichaelCropper @bnerickson
                        last edited by

                        @julien-f @marcungeschikts @olivierlambert

                        Commenting as I feel my recent error (https://xcp-ng.org/forum/post/53557) is somehow related to this thread reading through the comments and history.

                        cc. @Tristis-Oris

                        1 Reply Last reply Reply Quote 0
                        • M Offline
                          murarkavast
                          last edited by

                          Does the [NOBAK] need to be in the "Name" or "Description" section? This is not really mentioned anywhere.

                          Thanks

                          3b208940-6a16-4101-bf18-177c09427cf2-image.png

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

                            It is in the official doc: https://xen-orchestra.com/docs/backups.html#exclude-disks

                            just edit the VM disk name

                            1 Reply Last reply Reply Quote 2
                            • M Offline
                              markhewitt1978
                              last edited by

                              Found this by googling. Is there any news on being able to exclude disks at the snapshot level?

                              I have a couple of big SQL server VMs that are too big to snapshot, but the OS disk is relatively small and the attached disks are backed up by a seperate process anyway. So literally just need the OS image backing up.

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

                                See https://xcp-ng.org/blog/2022/11/18/xcp-ng-8-3-alpha/#✨-vm-snapshot-with-disk-exclusion

                                It's already used/supported by Xen Orchestra. If you want it for production, you'll need to wait for XCP-ng 8.3 to be available 🙂

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