Can't work out why certain items were excluded?

[jimmyhurr]

I have one tenant setup in Veeam Backup for Microsoft Office 365, backing up to a local repository. This backs up the entire organization at 5am, no issues. Has been running for several months and the log in the GUI states that no items were excluded as expected.

I recently started to investigate the ability to backup to AWS S3 via an object repo. So I added an additional backup job to the organization and started off backing up a few items in the org such as selected mailbox and sites purely to test. I set this to run at 1am. This seemed to work OK.

However, I noticed in the log for the original backup job saving to a local repo that a number of items were being excluded. This exclusion started when I introduced the additional AWS S3 job. The items that were excluded pretty much matched the items that were being backed up in the AWS S3 object repo job.

As soon as I deleted the AWS S3 job and re-ran the original local backup, there were no excluded items.

Is this behaviour I'm seeing expected?

[nielsengelen]

This is normal behavior. An object (User or site) can only be processed by one job at the time. By adding it in 2 jobs, it was excluded by one.

[jimmyhurr]

Thanks Niels, that explains it. Bit disappointed though. I was hoping to be able to backup the org direct to S3 as well as local, but it looks like I need to choose between one repo or the other. Is that right? Any way around it? Can you add the same org twice and configure the required jobs in each?

[nielsengelen]

This is not possible currently by product design. You can't add the organization twice to resolve this. We will take your request as a feature request.

[Polina]

Hi James,

We agreed with Niels that I'll get back to you with a more detailed response on this case.

The option you're looking for is possible, but with a different backup job configuration. Let me explain it:
If you add an entire organization to a job using the radio button in the wizard, the behavior you see is by design, as Niels confirmed above. Objects backed up by other jobs will be excluded from this 'main' job, no matter if those jobs are targeted at the same or different repositories.

However, there's another way to set things up and avoid any automatic exclusions - by adding an entire organization as an object. This configuration will allow you to have as many jobs as you need and all items will be preserved and protected as you need it.

[jimmyhurr]

Thanks Polina. I will give this a try and report back! Great service.

[Hydrogen]

Hello Everyone,

Is it possible to have multiple backup jobs targeting the same O365 organization/tenant to backup the organization to either:

1. Different repositories (e.g. one local, one object store in cloud blob storage)

2. Backup from different locations (e.g. proxy server on-premise backing up same 365 org. as a proxy server running on a VM in another location backing up the same 365 org.)

Thank you!

[nielsengelen]

Hi @Hydrogen - I merged your topic. Please have a look at a solution provided by Polina for point 1.

Point 2, this is possible. You can deploy a proxy in a specific geo location and assign specific backup jobs to it.