Hardened repo for VBO

[Florent Foulquier]

Hi All,

I just learned that VBO does not support Hardened Linux repository.

What would be the best way to provide hardened/lock/immutability/worm feature to the VBO repository?

Regards

Florent

[Mildur]

Use a VM or physical machine to backup O365 Data.
Then create an image level backup with VBR to the Linux Hardened Repo (or use SOBR with Object Storage).

Only Way possible today.

[Florent Foulquier]

Thanks for your quick reply Mildur!

[Mike Resseler]

@Florent Foulquier Just for my information, are you using a jet DB based repository at this point in time or an object storage based repository? I assume Jet (which means Linux is not possible) and if so, are you thinking about object storage repository at a certain point in time?

[Florent Foulquier]

Hi Mike,

Sorry for late reply I was on holidays.

The customer is not using VBO right now since it is a new project. So we are just thinking about the best architecture.

The issue with object storage is that if the customer don't already have it available at home (since the aim of using VBO is to protect On prem its cloud datas) it would be hard to build it only for VBO usage because VBO size is generally small and it is not that easy to build a small object storage solution (where Aretesca may change the game). So the Mildur suggestion might be the easiest to implement....

Florent

[Mike Resseler]

@Florent Foulquier

If it is indeed a small M365 organization, then probably building an S3-object storage compatible solution is not the best for the customer, although they might take advantage of it for other solutions also. In that case, Jet DB repository will do fine. In larger environments, object storage is a better approach to overcome the "limitations" of the jet DB repository when it comes to large scale.