Backup warning: ...is already processed by another job

[navillus]

One of my user's OneDrive is not being backed up. I receive the following warning with every backup job:

11/14/2018 8:45:24 AM :: Processing OneDrive Doe, Jane completed with warning: OneDrive Jane, Doe (https://tenantname-my.sharepoint.com/pe ... ane_domain) is already processed by another job

No data is backed up from this user's OneDrive. I only have 1 job backing up my Office 365 tenant. Any ideas?

Thanks,
Michael

[Polina]

Hi Michael,

The issue is not typical, so no ideas on the fly. Please create a support case and provide logs to our engineers for investigation (and share your case ID in this thread).

Thanks!

[Mike Resseler]

Hi Michael,

Is Jane Doe in some group? (Maybe a team or so). If so, it might be that it is being protected through that. Can you look in your selection?


Thanks
Mike

[esalinas]

Hi Michael,

Do you resolved the issue?

I'm having the same problem with Veeam Backup for Microsoft Office 365 v2.0 both with mailbox and OneDrive

Thanks
Eduardo

[Polina]

Hi Eduardo and welcome to the community!

As Mike responded above, this may happen if the same user is included in several backup jobs (separately or as a member of some group) and those jobs are running simultaneously. The job which started to process this user's data first will complete successfully, while the second one will complete with a warning that the object has already been processed by another job.

[m.novelli]

Hi guys, I'm having the same issue with a couple of customers:

"Processing site xxx finished with warning: Site xx is already being processed by another job"

The Backup Job is unique for each customer, every customer with a dedicated Backup Server.

I've installed right now latest cumulative patch 2.0.0.814 , tomorrow I'm going to check again

Ciao,

Marco

[Polina]

Hi Marco,

If the issue remains, to troubleshoot we'll need to see your configuration and logs. To provide the logs, please open a support case and post its ID here.

Thanks!

[m.novelli]

Seems that latest cumulative update solved the issue! Thanks

[Polina]

Good news!
Thank you for getting back on this, Marco