Greetings everyone...
I am working out the resources for physical backup server with local disks. Might I know if my workout is correct?
Data size: 30TB (Exchange + File Share)
Policy: 30 daily, 4 weekly, 12 monthly, 3 yearly
Source: Sangfor HCI (requires to install agent), single site
As refer to VSE https://calculator.veeam.com/vse/
Backup Server + DB + Repository = 8 CPU, 20GB RAM for Veeam to work
(No Proxy and Enterprise Manager required)
And will add some resources for Windows OS
Regarding storage, 249.43TB from VSE
So I add some buffer and for Windows OS with ~300TB disks space
Assumptions:
ReFS
No backup copy job
Generic Pessimistic: daily change 10%, compress ratio 50%, annual growth 10%
Is my thinking correctly?
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Oct 12, 2023 3:17 am
- Full Name: Tazd
- Contact:
-
- Product Manager
- Posts: 9557
- Liked: 2533 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Backup server planning
Hi Tazd
Our user guide recommends to have at least 1 GB RAM per Task. 20GB with all other components means, you would be able to run backup for approximately 8-10 disks simultaneously to be within our recommendations.
https://helpcenter.veeam.com/docs/backu ... repository
And our Best practice for repository server is to use 4GB RAM per CPU Core. Using it as a RefS repository adds another 0.5GB RAM per 1TB of reFS storage.
https://bp.veeam.com/vbr/2_Design_Struc ... ositories/
Do you have collected information from your current environment to confirm this numbers? Just to be sure that you don't make estimation on wrong numbers.
May I ask, do you have a second backup storage solution in mind. And a backup copy for immutable/air-gapped backups?
Instead of building a windows backup server on this physical host, you could use it as a hardened repository based on Linux. This would give you a immutable backup of your agent backups. the backup server itself can run as a VM on your HCI environment.
https://www.veeam.com/blog/hardened-lin ... tices.html
Best,
Fabian
Our recommendation for the repository server is "4 GB RAM, plus not less than 1 GB RAM for each concurrently processed machine disk". With a lot of Agent backups and their parallel disk processing, a lot of concurrent tasks will be opened.8 CPU, 20GB RAM for Veeam to work
Our user guide recommends to have at least 1 GB RAM per Task. 20GB with all other components means, you would be able to run backup for approximately 8-10 disks simultaneously to be within our recommendations.
https://helpcenter.veeam.com/docs/backu ... repository
And our Best practice for repository server is to use 4GB RAM per CPU Core. Using it as a RefS repository adds another 0.5GB RAM per 1TB of reFS storage.
https://bp.veeam.com/vbr/2_Design_Struc ... ositories/
I see that you have chosen 3TB daily change rate and approximately 3TB yearly growth.Generic Pessimistic: daily change 10%, compress ratio 50%, annual growth 10%
Do you have collected information from your current environment to confirm this numbers? Just to be sure that you don't make estimation on wrong numbers.
May I ask, do you have a second backup storage solution in mind. And a backup copy for immutable/air-gapped backups?
Instead of building a windows backup server on this physical host, you could use it as a hardened repository based on Linux. This would give you a immutable backup of your agent backups. the backup server itself can run as a VM on your HCI environment.
https://www.veeam.com/blog/hardened-lin ... tices.html
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Baidu [Spider], Bing [Bot], kenthsien0909 and 83 guests