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

    Too many snapshots

    Scheduled Pinned Locked Moved Backup
    19 Posts 5 Posters 199 Views 3 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.
    • J Offline
      jr-m4
      last edited by

      Throwing my two cents into the hat, as well.

      I had a similar situation. Snapshots would't be rotated out of retention, regardless of what I set on the retention setting (on a subset of VMs ie not all of the).. The thing that solved it for my, was to recreate the affected schedule.
      Do note that this will mark the previous backups taken by that technically deleted schedule, as being abandoned/orphaned.

      But after I did this, snapshots would be properly rotated as expected.

      M 1 Reply Last reply Reply Quote 0
      • M Offline
        McHenry @Pilow
        last edited by

        @Pilow

        396d876a-3faf-43c6-afcc-e7f372a6477d-image.jpeg

        SR is local storage
        8160315f-ad51-46dd-b1d9-2b6449af50b8-image.jpeg

        1 Reply Last reply Reply Quote 0
        • M Offline
          McHenry @jr-m4
          last edited by

          @jr-m4

          Recreated, testing now.

          1 Reply Last reply Reply Quote 0
          • M Offline
            McHenry @Pilow
            last edited by

            @Pilow
            Was there an announcement about the change in how these CR backups are done with snapshots now?

            I'd love to read up on it.

            P 1 Reply Last reply Reply Quote 0
            • P Offline
              Pilow @McHenry
              last edited by Pilow

              @McHenry screenshot the GENERAL tab of "Disaster Recovery" SR please
              just to see how many VDIs it hosts... at least 288

              it was announced here
              https://xen-orchestra.com/blog/xen-orchestra-6-3/#💾-backup
              but it is not explaing in details, I gathered information in another topix in this forum from @florent

              you also have the Changelog of 6.3.0
              https://github.com/vatesfr/xen-orchestra/blob/master/CHANGELOG.md#630-2026-03-31

              points to PR9524
              [Replication] Reuse the same VM as an incremental replication target (PR #9524)

              M 1 Reply Last reply Reply Quote 0
              • M Offline
                McHenry @Pilow
                last edited by

                @Pilow

                I am rerunning the backups after recreating the schedule to see if the error clears

                6f0d3051-1254-4d10-989b-c77a832378c9-image.jpeg

                1 Reply Last reply Reply Quote 0
                • tjkreidlT Offline
                  tjkreidl Ambassador @Pilow
                  last edited by

                  @Pilow Yes; it's been my understanding that this has been the default for many years now.

                  P 1 Reply Last reply Reply Quote 0
                  • P Offline
                    Pilow @tjkreidl
                    last edited by Pilow

                    @tjkreidl yeah, but he has 16 snapshots.
                    but the documentation also talks about vdi chain length

                    but it seems to me impossible to have only 16 snaps and a vdi chain length >30

                    thats why I wondered perhaps is it a cap limit of snapshots per SR, but I didn't find relevant info about this possibility

                    you know a lot about Xen, ever heard of this type of per SR limit of snapshots ?
                    Only info I found is that more than 100/150 VDIs in production per SR can degrade performance

                    tjkreidlT 1 Reply Last reply Reply Quote 0
                    • tjkreidlT Offline
                      tjkreidl Ambassador @Pilow
                      last edited by

                      @Pilow Yes, you are correct that the chain length is also limited. You might try to manually delete some of the snapshots and though the limit is supposed to be 30, perhaps there are other factors involved? Does that VM have a particularly large amount of storage and a lot of changes between snapshots? Are any other of your VMs experiencing similar issues? Your SR appears to be mostly empty, correct? Are there any related errors showing up in /var/log/SMlog ?

                      M 1 Reply Last reply Reply Quote 0
                      • M Offline
                        McHenry @tjkreidl
                        last edited by

                        @tjkreidl

                        I wish to maintain 16 restore points using CR, being an hourly restore point over the last two days (8 per day)
                        I perform a full backup nightly to reset the chain.
                        08c8a44a-4c6a-4509-9b44-cbe28fd6c4be-image.jpeg

                        It appears that each CR creates a new snapshot and the old snapshot is removed when a new one is crated
                        The documentation states this error is shown then there are more than 3 snapshots on a VM
                        https://docs.xen-orchestra.com/manage_infrastructure#too-many-snapshots

                        Is this a problematic backup strategy?

                        1 Reply Last reply Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better 💗

                        Register Login
                        • First post
                          Last post