Skip to main content
Question

Appliance sizing results

  • April 28, 2026
  • 3 comments
  • 25 views

In the sizer for the backup server it shows  the appliance as needing 12 cores and 24Gb of memory, does that also include the proxy and repository that is also shown in the vm workloads?

3 comments

Forum|alt.badge.img+1
  • Veeam MVP
  • April 28, 2026

Hi,

The appliance sizer is sizing specifically sizing the management plane based on the total estimated workloads it will be managing. Proxy and Repository are not included. They are calculated in the specific workload calculators (i.e. VM, Agent, NAS, etc.).

 

If you wish to have the backup server, proxy, and repository sized together, please use the Scenario Builder for best results.

 

-Adam


  • Author
  • Not a newbie anymore
  • April 28, 2026

So my question now then  is that do I need the backup appliance which is 12 cores 24 GB memory and then also add proxy requirements which for site A  is a further 6 cores and 12GB of memory and for Site B I need a further 4 cores and 8 GB memory.

 

So total of 12 + 6 = 18 cores and 24*12 = 36Gb memory for Site A

and

12 + 4 = 16 cores and 24*8 = 32Gb memory for Site B

 

 

are these assumptions for proxys running as either VM or physical or if the veeam appliance is being the proxy, these are the addtional CPU/ram requiremnts for that applaince?


Forum|alt.badge.img+1
  • Veeam MVP
  • April 28, 2026

First, I just double-checked the sizing & confirmed with R&D that we left off the “Under 100” workloads. That is handled by the minimum spec (8 core, 16GB RAM) sizing. I’ll update the calculators to reflect that ASAP. 

 

Each component is sized individually. There are some caveats to consider:

  1. The Calculator does individual sizing at no smaller than minimum requirements. 
  2. Scenario Builder gives the raw, required compute to achieve the desired outcome. It does not account for minimum requirements or OS requirements. 

To answer your question: Yes, you need all the resources that are output for each component.

However, the resources can be combined or assigned to dedicated machines. If you use the Scenario Builder to build this out, you’ll have a much more accurate view of the required resources that you can combine into a single box.

Scenario Builder also allows the distinction between physical or virtual as there are several factors that play into the throughput achieved by each.