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.
Statistics: Posted by david.domask — Apr 25, 2025 11:55 am