Skip to main content
Question

NAS calculator (v1.7.0.1): Proxy values differ between result card and Result Detail – bug or by design?

  • October 2, 2026
  • 2 comments
  • 19 views
Forum|alt.badge.img

Hi Calculator team ,

First of all, thank you for providing such a great set of calculators. We use them all the time for customer sizing and really appreciate the continuous improvements.

I'm sizing a NAS backup with the Veeam Calculator (v1.7.0.1, Advanced mode) and noticed that the proxy requirements shown on the result card differ from the values in the Result Detail dialog.

Result card (summary): Proxy – Cores 2, RAM 16 GB
Result Detail: Proxy x1 – Cores required 8, RAM required 16 GB

Screenshot attached.


Questions:

1.Is this difference a bug, or is it intended?
2.If it is intended, how should the two values be interpreted? For example, is one of them a per-proxy minimum or recommended spec, and the other the total compute required? Or are they based on different criteria, such as incremental vs. full, or throughput vs. walk-the-tree?
3.Which value should we use when presenting the proxy sizing to customers?

Optional:
4.For "Network speed", should we enter the link speed per proxy or the aggregate bandwidth between all proxies and the source arrays?
5.Is "Array max IOPS" used only for the walk-the-tree estimation, or does it also affect throughput and proxy sizing?


I noticed the v1.7.0 release notes mention "the details dialog no longer repeats the proxy figure," so I wanted to check whether this is related.


Thanks in advance.

Hirohito

      2 comments

      Chris.Childerhose
      Forum|alt.badge.img+23
      • Chris.Childerhose
      • Veeam Legend, Veeam Vanguard
      • October 2, 2026

      ​@david.tosoff should be able to help answer this.

      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
      Forum|alt.badge.img+1
      • adamC
      • Veeam MVP
      • October 2, 2026

      Hi,

      Thanks for flagging this, and for the clear screenshot. This is a bug, not by design. I traced it in the calculator code. With the updated formula, there was a mix up in the data aggregation from old logic to new logic.

      The intended display for both is the proxy count times the per-proxy size, so 1x proxy with 8 cores and 16 GB RAM in your case. 

      This has been fixed and published now.

      For the network speed, use the speed per proxy. This is the lowest speed that would be encountered on the trip from a single proxy to the repository. 

      IOPs is used for Proxy sizing and estimate of Walk-The-Tree. This comes from extensive QA testing where the key factor in proxy sizing and backup speed was the IOPs limits we would run into during backup. 

      -AC

        Terms & ConditionsAccessibility statement