Skip to main content

Hello,
I am working as System, Virtu and Backup engineer.
Currently designing a VBO architecture for a customer who has a huge amount of data in Azure O365.
I see everywhere on the forums problems with VBO 1st backup speed even on quite small environment.
Do you have any reference or use cases about customers with more than 5000 users, or 5000 SharePoint sites and how long it took to perform the fisrt backup ?

Is VBO well suited for this kind of customer with more than 100 TB of data in AZURE to INGEST ?

Would it be a good strategy to fix a short retention (5 days) to catch few object on the first run and then change it to 10 days for the 2nd run and so on in order to reduce the overall amount for each run ? Or does not make sense as after each retention change the job will start as if it is the first time ?

As I noted before splitting things up is the best route as that amount of data will take time for backing up.

See this site for best practices for Architecture - https://bp.veeam.com/vbo

On that site this page outlines job sizing, etc and you should not exceed 4000 users per job - https://bp.veeam.com/vbo/guide/design/sizing/

https://bp.veeam.com/vbo/guide/design/maxconfig

 

Great page including a reference to the calculator site to see how much storage is required but it is recommended to use object storage.


I see my tip to post this in the community was correct 😎


Comment