Have I missunderstood Veeam Backup for Microsoft 365?

[bhlgr015]

Ok so I have been using Veeam B&R for 10+ years and possibly naively assumed VB for M365 was similar, but it seems like its extremley limited (at least compared to our use case).

With B&R we backup each job to local storage (with job retention policies), secondary copy to Tape then backup copy to a repo at a remote site/DC. We are also going to add Veeam vault + Immutable repo for additional protection. All good no issues.

Now with M365 software we only have either local disk or object storage. We dont have any object storage so have a local disk based repo, thats fine so we now have 1 backup copy. But no secondary copy option, no copy job for additional repo's at external sites/dc. No option for veeam vault either???

Also no job retention policy or backup type (incremental/full etc..) and seems like its a simple retention policy based on the repo. So I need a repo for each job type if I wanted different rententions.

Have I missed something here or do I need to now backup M365 repo's with B&R? Just for clarity we are looking to only back OneDrive folders at this time as B&R does everything else (we are on prem for exchange, servers, etc..).

[Polina]

Hi Michael,

VB365 is indeed very different from VBR.
It supports backup copy functionality as well, but it works for object storage repositories only (see more here: https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80).
Veeam vault is not supported.
The first backup is always full, all the subsequent are incrementals. Note that unlike VBR, VB365 does not maintain any backup chains and does not create any period or syntethic fulls.
Retention is specified on the repository, not on the job level.

Hope it helps.

[bhlgr015]

Thanks for the update, such a shame this is a seperate product and nowhere near as comprehensive as B&R. As a middleground... could B&R backup the local disk repository of M365? If so.. is this a similar repo to B&R with vbk vbr files etc..? or would it have to be the entire folder structure / db's?

And lastly I believe we can use veeam vault (in B&R) but its only for jobs via B&R / vbk, vbr files etc.. correct?

[bhlgr015]

So I've been doing a little more digging and found a post on this forum from 2018 talking about tape backups (suprised in the 7 years nothing has progressed in this area) and it is suggested that VBO is run on vm and backup that vm with VBR with application awareness then VBR see's VBO db etc.. and can then do restores. I pressume we dont need to migrate VBO to a vm and it can reside on the VBR host still and still backup this host (and repositories) and we will still get the same result?

Is this still the only method / recommended way to get VBO repo's to Tape, Veeam Vault etc.. ?

[Polina]

Hi Michael,

We do not recommend running the two products on the same host for performance reasons.
Note also, that niether it's recommended to use the same PGSQL instance for both solutions.
Sending backup of VB365 server/repositories to tape was tested with the community efforts, and I cannot guarantee that it works in all possible scenarios.
Protecting a VB365 Jet-based repository with VBR using app awareness is possible and there were a number of posts on this topic here on forums.

Thanks!

[bhlgr015]

Thanks @Polina, not too concerned with performance. Is there a serious issue with using the same PostgreSQL or again for performance reasons / future complications? I suppose we could spin up a new VM just for VBO but I'll just need to figure out where I want the data to sit as this could be a less than ideal usage of SAN storage over local disks on the VBR physical host (although saying that could I still use the VBR server as a repo for VBO?).

I'll see if I can find the posts that talk about tape backups, and any vault threads to see if I need to consider anything or can learn from others that are doing what I am proposing.

[Polina]

Michael,

Using a separate PGSQL will help to avoid future complications. We have already have several customer cases where the PGSQL shared between VB365 and VBR caused issues. Also, VB365 should have its own repositories, it's not compatible with VBR repos.
The following resources should be helpful for you to better plan your deployment:
https://helpcenter.veeam.com/docs/vbo36 ... 365-server
https://bp.veeam.com/vb365/

Thanks!