Processing archive mailbox XXXX completed with warning: Mailbox XXXX is already processed by another job

[lmendel]

Issue started for us on 15/10 with single tenant, now about 10 tenants are affected. From what I can see only mailboxes that don't have mail archive enabled.

[Pete@DPY]

There is a KB on this now when I went to lodge a support request. https://www.veeam.com/kb4787

[lmendel]

Fix was released over this weekend, however it hasn't resolved the issue, at least for us.

Same KB as above - https://www.veeam.com/kb4787

[Polina]

@lmendel

Are you using a different VB365 version, or does the problem persist after applying the fix?

[Pete@DPY]

Solution

Customers who are running Veeam Backup for Microsoft 365 8.1.2 or older, are advised to upgrade to the latest 8.1.2 release, build 8.1.2.3301, available from KB4711.
Customers who have already upgraded to Veeam Backup for Microsoft 365 8.2 are advised to continue allowing the backup jobs to operate as usual despite the errors. A fix for v8.2 will be made available soon, and this article will be updated when it is released.
Note: Veeam Backup for Microsoft 365 cannot be downgraded to a previous version.
Customers using Veeam Data Cloud for Microsoft 365, please monitor https://vdcstatus.veeam.com/ for further updates.

[admd]

@lmendel

Are you using a different VB365 version, or does the problem persist after applying the fix?

Hello,
We updated yesterday to 8.1.2.3301.
The problem persist after the fix. Case #07828325
Fresh logs are available.

Thanks a lot !

[lmendel]

@lmendel

Are you using a different VB365 version, or does the problem persist after applying the fix?

I forgot to update the proxies, after proxy update jobs are completing fine.

Thanks

[admd]

Hello,
We updated yesterday to 8.1.2.3301.
The problem persist after the fix. Case #07828325
Fresh logs are available.

Thanks a lot !

I also forgot to update the proxies ! Well I think that's the answer

[pat_ren]

I updated all of our servers to 8.1.2.3301 - including the proxies, the issue remained however I tried rebooting everything later that evening and it was resolved after a reboot.
I suspect something did not restart properly in the update process. Issue now solved for me.