Backing up O365 data to on prem Linux harden repo

[skurtzal]

I recently discovered a limitation with on VBRO365 console. I had to put in a ticket with support to confirm this just in case. I was just simply missing where to configure a new Linux repo on prem. For backing up our O365 data to because currently. I only have it backing up to our main Windows repo server which isn't an ideal solution. Especially since Windows isn't a very secure OS but also only have one copy of that data. Now we have two Linux VBR servers that are currently being used as aux copies for. All of our on prem vSAN data that gets backed up to those servers for redundancy.

I know that we could use either Blob storage or some other form of cloud storage for. Backing up our O365 data but we currently aren't there yet and that's easier said than done. We also don't have the current budget for adding another subscription base cloud tier for storing our O365. Eventually I would like to go that route but even when we are able to do that. I still would want to be able to backup and keep copies of our O365/ Azure Tenant data. On prem Linux repos as well, so that we also don't have to solely rely on cloud vendors to hold onto our data.

To have to have multiple different cloud vendors to hold onto your O365 data. In order to follow the 3-2-1 best practice rule I find kind of silly. When we should be able to take advantage of our preexisting storage devices to hold onto our data. I hope that Veeam will take this into consideration and implement it into. The next major release update for VB0365 since I can't imagine that we are the only ones who are waiting for this ability. Plus I can't imagine that there's any sort of limitation in O365 data structuring on why it couldn't be saved to the XFS file system.

[Mildur]

Hi Scott,

There are no plans to support Hardened Repositories with VB365.
With local disk storage, VB365 uses Jet databases to store its backups. These database files must remain open for write operations and can never be made immutable, which excludes Hardened Repositories as a possible repository. Using backup files (VBK/VIB) as in Veeam Backup & Replication is also not an option due to performance reasons for the type of source data in Microsoft 365.

As a workaround, you can use a VM or Agent backup job in Veeam Backup & Replication to back up the entire VB365 machine and store its backup on a Veeam Hardened Repository. This gives you an immutable copy of the entire VB365 server. From the Veeam Backup & Replication console, you can also initiate a restore of Microsoft 365 data directly from the backup of your VB365 machine.

I know that we could use either Blob storage or some other form of cloud storage for.

For immutability and backup copy support, you’ll need an Object Storage Repository.
Object storage repositories can be local in your own datacenter or as a service in a public cloud. There are many options to choose from, there is even the possibility to build your own Linux based object storage with MinIo:
- Unofficial object storage compatibility list
- Veeam Ready List

Best,
Fabian