Estimated repository size for o365?

[lando_uk]

Hi

I'm wandering what the compression/depude ratios are on average for OneDrive and Sharepoint? If we had 30TB of OneDrive data, what sort of repro size will i need for 30 days worth of retention or is it impossible to calculate?


Thanks

[Mike Resseler]

As always, the answer is: It is impossible to calculate

But you can make some calculations.
First: Each repository is technically limited to 64 TB per year (we split up the repository databases per year).
So the 30 TB will most likely be spread out over multiple 64TB databases depending on the age of the items. (Files modified in 2018 will be in the 2018 repository, files in 2017 in the 2017 repository and so on...)

The 30 days of retention is the trick issue here. How much churn will you have on those 30 days (PS: Don't forget that the retention in VBO is different than the retention in VBR so you might want to read up on that first...). If you have much churn (new files, modified files...) then you will need more additional space. If not, then the amount of additional space will be limited.

Last but not least, we use inside compression which delivers around 15%

Hope it helps
Mike

[pesos]

Mike, I have seen in numerous threads where you recommend using B&R to back up the VBO machine itself in order to have the kind of retention we are used to and integrate into b&r for restores etc, which sounds great.

But what I don't understand is how this will work from an efficiency standpoint - will we not be duplicating the amount of repository storage eaten up with this approach?

Thanks,
Wes

[Mike Resseler]

Yes and no...

If you keep a 3 year retention then you will have lots of duplicate. However, if you start with a full backup (no retention) then things will change after a while. Don't forget that the mean reason for the recommendation is not really the retention, but the 3-2-1 rule. We do need to work on a better system however, just haven't figured out yet what is best for this type of backup (application data backup versus image level backup)

[pesos]

But would 3-2-1 apply here if our o365 repository is on the same hardware as our b&r repository?

[Mike Resseler]

No, that wouldn't. But is your VBO VM running at the same storage as you have for VBR repository?

[pesos]

We have VBO installed on one of our B&R servers currently. It is using one of our hyper-v hosts as proxy, writing to local storage (the same hyper-v host that writes b&r to the same local storage). So even if we were to back up the VBO server, we wouldn't be backing up the VBO repository?

[Mike Resseler]

Correct. You would need to backup the proxy. And since that is your Hyper-V host, then you would need Veeam Agent for Windows to do that backup

[pesos]

And we'd be backing up one folder on the repository hardware to another folder on the repository hardware

[pesos]

Is there a writeup somewhere where I can read up to get my head wrapped around how retention works in vbo together with b&r? thanks!

[Mike Resseler]

No. There isn't. You can read how the retention works in our userguide for VBO. For VBR, you have to think it differently because it is image-based. You can find that also in the documentation for VBR