Skip to main content
Question

LHR Immutability Calculator

  • June 22, 2026
  • 7 comments
  • 33 views
K
Forum|alt.badge.img

Hi All,

I was working through estimating capacity for a LHR (standalone) in the calculator when I noticed that it doesn’t appear to take into account the fact the the LHR will make GFS points immutable for their entire duration.  I’m assuming this is happening because REFS/XFS are lumped together in one check vs being able to state that you’re using an LHR.

Settings - 14 Dailies, 4 weeklies, 12 monthlies - immutability 14 days - REFS/XFS checked.

For LHR the result below should show all GFS points as immutable.  

 

I am wondering if something should be added that can identify if you are using an LHR to show immutability properly? I know it won’t impact the calculations at all but I think it would help to make sure anyone using an LHR would understand that correct immutability expectations.

      7 comments

      coolsport00
      Forum|alt.badge.img+23
      • coolsport00
      • Veeam Legend
      • June 22, 2026

      I agree ​with your suggestion @katie.baileydietz ...it would also make it less confusing I think. 👍🏻

      Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
        Chris.Childerhose
        Forum|alt.badge.img+22

        This is a great suggestion.  If you want to get feedback quicker to the Product Team, use the send feedback link on the calculator site.  That is the best way to send feedback to them.  Used it many times myself as I want VSPC added to the mapping section. 😁

        Chris Childerhose (Enterprise Architect) - VMCE+ | VMCA | VMCE | VMCE-SP | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 7* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV/VCP-VVF | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
          K
          Forum|alt.badge.img

          This is a great suggestion.  If you want to get feedback quicker to the Product Team, use the send feedback link on the calculator site.  That is the best way to send feedback to them.  Used it many times myself as I want VSPC added to the mapping section. 😁

          So I actually did hit the send feedback button and it sent me here, should it be sending me to something else?

            Chris.Childerhose
            Forum|alt.badge.img+22

            This is a great suggestion.  If you want to get feedback quicker to the Product Team, use the send feedback link on the calculator site.  That is the best way to send feedback to them.  Used it many times myself as I want VSPC added to the mapping section. 😁

            So I actually did hit the send feedback button and it sent me here, should it be sending me to something else?

            Oh, that is weird as it should not from what I remember.  Hmmm 🤔

             
             
             
            Chris Childerhose (Enterprise Architect) - VMCE+ | VMCA | VMCE | VMCE-SP | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 7* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV/VCP-VVF | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
              M
              • maurodriguez
              • Not a newbie anymore
              • June 22, 2026

              This has been reported multiple times. By me and by others, for example:

              Calculator seems off for S3 Immutable GFS Backups | Veeam Community Resource Hub

              Calculator for Real Physical Immutable Linux Hardened Repository | Veeam Community Resource Hub

              We have yet to see improvements or an acknoledgement of this problem.

                coolsport00
                Forum|alt.badge.img+23
                • coolsport00
                • Veeam Legend
                • June 22, 2026

                That’s interesting. Hmm...maybe tag ​@david.tosoff or ​@adamC directly would help?

                Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
                Michael Melter
                Forum|alt.badge.img+12

                Though this being a valid point, we could also agree on it being a purely cosmetical issue. You won't see any additional storage consumption as all GFS points currently are immutable and also present for their entire duration.
                Though for the short term retention one might well set immutability longer than the short term retention and get the Chan out of sync, for GFS it is always in sync.
                In addition, for S3 repos you now even have the option to put immutability only onto short term retention. Maybe (hopefully) we’ll also get this option for the VHR aka LHR. 
                So, calculator would have to ask a lot of additional questions just to put the lock symbol next to the GFS point of not. 

                Michael Melter - #VeeamLegend #veeam100 | VMCT | VMCE9 | VMCE2020 | VMCE2023 | VMCE2021 | VMCAv1 | VMCA2022 | VMCA2024 | VCP | MCP | DCIE | PhD | VDST TL3
                  Terms & ConditionsAccessibility statement