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

    Feedback on immutability

    Scheduled Pinned Locked Moved Backup
    57 Posts 11 Posters 27.6k Views 13 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

      Indeed, because if XO is compromised, then it could disable immutability.

      V 1 Reply Last reply Reply Quote 0
      • V Offline
        vkeven @olivierlambert
        last edited by

        @olivierlambert We tried adding compliance( prevent any file manipulation for X period) directly into bucket but XOA could not do his backup job correctly and the logs are full of access denied probably because of file merging or manipulation refused , so how we should do this ?

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

          @vkeven same problem here, we decided not to proceed with this as it would never work with an incremental delta without doing a full every few weeks. We are going to handle this with s3 and synology internal features.

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

            Thanks for your feedback, we'll discuss internally if there's any other possible approach (and I'm not sure).

            R 1 Reply Last reply Reply Quote 0
            • V Offline
              vkeven
              last edited by

              So what is the deal with these guy ?

              1 Reply Last reply Reply Quote 0
              • olivierlambertO olivierlambert referenced this topic on
              • R Offline
                redneckitguy @olivierlambert
                last edited by

                @olivierlambert
                Any updates on this? We're using Backblaze buckets with compliance turned on at the bucket level, but we keep getting failures once the retention period expires and it starts to remove the old backup chains.

                We tried setting 28 days of retention at the bucket level, 42 in XenOrchestra, and are running a full backup every 2 weeks. I have a ticket open with support but so far a resolution hasn't been found.

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

                  In theory that should work 🤔 Ping @florent

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

                    @olivierlambert
                    So it looks like the issue is not related to object lock or immutability but rather Backblaze not handling the merge requests very well. Not sure why this isn't impacting the other backup job without object lock, but anyways.... guess we're in the market for a different storage provider.

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

                      Sadly, Backblaze is often having issues on S3 (timeout, not reliable etc). We are updating our doc to give a "tiering" support.

                      1 Reply Last reply Reply Quote 1
                      • G Offline
                        gsszuber
                        last edited by

                        We attempted a similar configuration using Wasabi S3 cloud storage as the target. What we discovered is that the Lifecyle Rule we created wiped out metadata.json and encryption.json in the root of the bucket once those files were outside the retention window. It was a global rule and I'm guessing that we need to be more precise and use scoped rules that target just the xo-vm-backups, xo-config-backups, and xo-pool-metadata-backups folders. Does that sound like it would work? I have a ticket open as well on this.

                        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