Recommended Configuration for a MSP

[tsukraw]

Hey guys.

Wanted to throw this out to the group and see if there is anyone who is either doing a similar deployment or could provide recommendations.
I'll be the first to admit I don't know Veeam for Microsoft 365 as well as I know VBR.
And for support, this is in reference to case #05375303

We are an MSP who is looking to utilize Veeam for Microsoft 365 to backup our customers O365 environment data.
Using our infrastructure customers are built with their own storage repository, to make it easy to report space utilization.
Current we are running is 6.0.0.367
We have 2 servers involved. One server is running the console, and one server is acting as the proxy/repo server.
Both servers in question have 40GB of RAM.
We have approximately 40 organizations within the console so far which is equating to 21.5TB of date it appears.

What we are running into is horrible performance and constant Veeam.Archiver.Proxy crashing daily.
On the Veeam Proxy server the machine sits at maxed memory all day long until the Veeam.Archiver.Proxy service crashes, at which point we restart it and the memory climbs back to max.

I'm not necessary looking for help troubleshooting the issue, but a better understanding of how to structure the solution as I think we are outside the recommendations. (I am being handed what was already there, so don't shot me if the setup is incorrect)

1) In reading the recommendations from the below link.
It says the recommended number of JET databases is 250 with a max of 750 per proxy.
Is it correct to assume a .abd file is a JET database?
The article doesn't make it very clear as to what a JET database is. I'm just going off other information.
https://bp.veeam.com/vbo/guide/design/m ... tml#fn:adb

2) If an .adb file is indeed a JET database, it appears that each year creates a new database withing the organization that is being backed up.
Of the 40 organizations we currently are backing up, we have 1053 files ending in .abd
This would mean we are well over the recommended limit and max correct?

3) I have done a fair amount of looking and I could not find much information out there on a proper setup of Veeam of Microsoft 365 from a MSP prospective where you are going to have many organizations.
Is there a recommended number of organizations per proxy?

4) With the current setup.
Would it be recommended to reduce the number of organizations per proxy server and try to have the number of Jet databases in the 250-750 range?

5) If we were to do number 4 and break the organizations out between multiple proxies, as the years go on wouldn't the database count continue to grow and potentially re-introduce its self?

6) With direct to object storage being added to Veeam for Microsoft365.
This had me wondering if that would be a better direction to go? That route would not utilize JET databases correct and would be more scaleable?
Would Object-Storage ultimately take less local resources (Ram/CPU/Proxy servers)

Any recommendations on this topic are welcome.
We are ultimately hoping to make Veeam work for our customer offering, but understand if we are pushing it beyond what it was designed to do.

Thanks

[Mike Resseler]

Hey,

First: Since you are a MSP, and I assume you are a VCSP then you can request access to the service provider forum. This will give you access to a forum where specific configurations for VB365 are being discussed.

Some answers already.

0) For your issue, I assume that support will give you CP1 to install on VB365 v6 (this will be online this week for everyone, but support has it already), please keep us updated if that solves the proxy issues

1) Correct, an .adb file is a jet DB. But since, you are a MSP, and seeing that you already have 40 organizations, I would recommend you to dive into object storage (either S3-compatible on-prem or one of the bigger cloud vendors) as the size of those organizations will grow, the amount of data will grow and jet DB repositories might get you into various performance and scalability issues in the future.

2) Correct. Each year has at least 1 jet DB file (and if one year is full, a second one will be created for that year). Again, see my recommendation above for looking into object storage. Also, considering the amount of DBs you already have, consider creating a second proxy and moving x amount of organizations

3) Not a recommended amount of organizations (you can have lots of small ones but also little big ones so it is difficult to put a number on it). The BP guide should help you getting further and ofcourse contact your Veeam sales rep as we have very good system architects that can help with the setup/ design of such an environment

4) If you are keeping the current setup, then my advice would that be indeed. But I'm repeating myself, it will get you into trouble going forward and growing the service (and we learned the last years that such a service is getting popular real fast

5) See above, the only difference is what your retention range is. If it is 7 years for example, then after a period the ADB files that are year 8 will dissappear

6) I guess I answered that already . And yes, it has indeed those advantages

Conclusion: Talk to your Veeam sales or technical rep, so that our architects can work with you for a good design. These guys have designed much bigger environments and we have a few that are specialized in service providers

Hope it helps
Mike

[jorgedlcruz]

Hello,
Not much to add to an exceptional reply by Mike. In my years as a Veeam Systems Engineer I have used all the next documents to help Customers with sizing:

• A really good Excel-based calculator, Community based but good for estimation
• https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=60
• https://bp.veeam.com/vbo/guide/design/sizing/
• There is some light information here

But as Mike said, reading you guys are a VCSP, please reach out to your local Veeam Cloud SE, who can engage a Solutions Architect if required, who are extremely knowledgable about sizing like yours.

Good luck, keep us posted!