I'm using the Veeam Calculator tool (https://www.veeam.com/calculators/simple/vbr/machines) and need help with two questions:
1) For a Hardened Repository Server or Gateway Server (used for Data Domain immutability), do they require the same CPU/RAM resources?
2) If the estimated CPU and memory requirements are met, can we use only 1 repository/gateway server even when managing over 9PB of data?
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Apr 25, 2025 10:40 am
- Full Name: Kady
- Contact:
-
- Veeam Software
- Posts: 2622
- Liked: 611 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Veeam Calculator tool
Hi Kady, welcome to the forums.
https://helpcenter.veeam.com/docs/backu ... repository
https://helpcenter.veeam.com/docs/backu ... way-server
Check our System Requirements pages for repositories and gateways - the sizing is similar though gateways have a higher initial memory requirement. CPU and memory resources are based on the concurrent tasks you plan to push through, which is where the calculators can help.
Can you explain your setup a bit more for the repository planning? My main concern with a single repository/gateway managing a large amount of backups is how you would handle that repository/gateway breaking? Until it's repaired you wouldn't be able to continue backups or perform restores. If you can tell a bit more about the planned environment, we can better advise. Total amount of data stored is more a consideration for the storage design, for Veeam's processing purposes sizing appropriately for the intended throughput per day from backups/restores is most important.
https://helpcenter.veeam.com/docs/backu ... repository
https://helpcenter.veeam.com/docs/backu ... way-server
Check our System Requirements pages for repositories and gateways - the sizing is similar though gateways have a higher initial memory requirement. CPU and memory resources are based on the concurrent tasks you plan to push through, which is where the calculators can help.
Can you explain your setup a bit more for the repository planning? My main concern with a single repository/gateway managing a large amount of backups is how you would handle that repository/gateway breaking? Until it's repaired you wouldn't be able to continue backups or perform restores. If you can tell a bit more about the planned environment, we can better advise. Total amount of data stored is more a consideration for the storage design, for Veeam's processing purposes sizing appropriately for the intended throughput per day from backups/restores is most important.
David Domask | Product Management: Principal Analyst
-
- Enthusiast
- Posts: 47
- Liked: 4 times
- Joined: Nov 14, 2019 7:12 pm
- Full Name: Chris Lukowski
- Contact:
Re: Veeam Calculator tool
Something else I wish the Calculator Tool did was give direction on which components should be installed directly on physical servers and which should be virtualized.
-
- Veeam Software
- Posts: 2622
- Liked: 611 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Veeam Calculator tool
Hi StoopidMonkey,
You can discuss and leave feedback on the Calculators over on community forums.
A lot of that will depend on your environment and your specific needs, but there are a few known "must not be virtualized" situations that may make sense to be in the calculators.
You can discuss and leave feedback on the Calculators over on community forums.
A lot of that will depend on your environment and your specific needs, but there are a few known "must not be virtualized" situations that may make sense to be in the calculators.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Amazon [Bot] and 73 guests