Building a repository for around 50 clients and have some ?

[willrun4fun]

I am thinking of building another repository just for my endpoints to hit and get it off of my main VMware destination. I would also like to expand this to more than the few clients I have been evaluating it on. After saving myself a day of work rebuilding a workstation due to a corrupt registry I am sold!

In the past I have been building Windows Server 2012r2 servers using storage spaces and HGST 4TB drives. It has been working well for me and will do that again unless somebody has a different idea. I could throw 6-8 drives in a system and meet my needs for now.

The plan is for around 50 Windows 7 clients to backup to this repository.
How will it handle this. Will it queue them up so it does not get overloaded?
Is it up to me to manage the schedules manually to avoid this?
Will they benefit from de-duplication on the repository?
What are the best practices to limit cryto-malware risks.

Thanks!

[Dima P.]

Hi Andy,

I am glad to hear you are looking into Veeam Endpoint Backup as a potential solution.

How will it handle this. Will it queue them up so it does not get overloaded?

Veeam B&R repository's load control settings affect the VEB jobs, so you can throttle VEBs activities by setting the ‘Limit maximum concurrent tasks’ and ‘Limit read and write data rates’ to the desired values.

Will they benefit from de-duplication on the repository?

Definitely, since you are backing up the same operating systems.

What are the best practices to limit cryto-malware risks.

This post might help you.