Block size for VBO365 repository

[joserizal]

Hi there, I've seen mixed recommendations in terms of block sizing recommendations - 4K in some places and 64K in some places (and NTFS over ReFS). Our preference is to use 64K so that we aren't limited to 16 TB but wondering how big/what the downsides are to this. The rep will be used Sharepoint/Exchange online backups.

Cheers

[Mildur]

Best practice is NTFS with 4k Block Size in the VBO Best Practice Guide. You don‘t have FastClone Features. ReFS is not needed from the Veeam side.
https://bp.veeam.com/vbo/guide/buildcon ... -repo.html

Repository File System should be chosen as NTFS with default settings (4k allocation units).

If you need more, then go for it. I don’t see a problem.
But I recommend to split the backup repo over multiple disks if you can. 64TB is not a low One repo for each Backup Type. Is this environment for a „Backup as a Service“ Scenario?

[joserizal]

Hi Mildur, yes this is for a BaaS ie multi-tenanted repository.

[Mildur]

We are going away from legacy disks for BaaS.
Object Storage will be better for us. It has a higher compression (~50%) as legacy disks (~10%).
I heard rumors in this forum, that one of the next versions of VBO365 should allow the 3-2-1 Rule also with VBO365 and Object Storage.

With Legacy Disk Repo, if you can, create a partition (if it’s a vm) for each tenant. Or at least a dedicated repo per tenant and workload (SPO, ODB, EXO).

[Mike Resseler]

I agree with Mildur. If you want to start a BaaS offering I highly recommend to look into object storage for your service. The running costs will be lower and if you grow well (and we see quite some service providers that grow fast these days, adding lots of customers on their platforms) then object storage is the repository type that will allow you to scale faster, and evenly importantly, it has less limits compared to JET DB repositories for the future features we want to add.