Site is already being processed by another job

[akguy]

I have a very small Office 365 environment which I have been backing up successfully for several months with no errors. I have not made significant changes to the Office 365 instance recently. A couple of weeks ago, my backup server was running poorly so I cancelled this Veeam Office 365 backup job to restart the server. Ever since then, the daily job has failed every day with the same warnings:

Processing site xxxxxxx finished with warning: Site https://xxxxx.sharepoint.com/sites/xxxxxxxxxxx is already being processed by another job

Processing site finished with warning: Site https://xxxxx-my.sharepoint.com is already being processed by another job

I have tried to isolate these individual sites and create them as separate individual backup jobs (as I read worked for someone else in these forums) but I get the same error/warning when running those backup jobs. It seems to me like maybe there is a flag/file created in Azure that tells Veeam the job is currently being backed up and that flag was never removed because of the forced cancellation I did a couple of weeks ago? I would really appreciate some help.

I have also opened a support ticket for this with Veeam but I received an email encouraging me to post it here in case the community had insight into the issue.

[Mildur]

Is it possible, that you are using dedicated Teams Backup Job and a Sharepoint Backup Jobs? And they are running at the same time?

Veeam has build in a logic, that the same site will no be backuped twice at the same time.

You will find some information here to this warning:
veeam-backup-for-office-365-f47/backup- ... ml#p304777

[rairiau-omr]

Hello,

I think I have the same issue, some SP sites are not backup since the first full job execution was cancelled:

Processing site ##### processus finished with warning: Site https://####### is already being processed by another job

I will open a support case, but do you find a solution ?
Thanks.

[nielsengelen]

@rairiau-omr it means you have configured multiple jobs covering the same site(s) and they ran at the same time.

[rairiau-omr]

Thanks for your reply.
Yes we have 2 different jobs, one for SharePoint an one for Teams, but they don't ran at the same time.
Also we have this issue since the beginning of the SP backups, Teams backup were launched few days after.

[rairiau-omr]

I think I've find the issue.
When I look the first full SharePoint job session log, I can see that some SP sites backup are still in progress (since 525 hours ...) but the session is stopped and no jobs running.
After services restart the status in this old session is still running ... so something is blocked in the Veeam VBO database ...

I'v 4 sites still running in the log session, the 4 sites who are not backup ...

28/04/2021 13:36:27 :: Processing site: https://####.sharepoint.com/sites/####.. :: 525:20:00
28/04/2021 13:38:13 :: Processing site: https://####.sharepoint.com/sites/####... :: 525:18:14
28/04/2021 13:44:37 :: Processing site: https://####.sharepoint.com/sites/####... :: 525:11:50
28/04/2021 13:55:44 :: Processing site: https://####.sharepoint.com/sites/####... :: 525:00:43

[nielsengelen]

That looks like those backups may be stuck but you will have to work with support to analyze it. Can you open a case and let us know the support case ID?

[rairiau-omr]

Yes, i will do it.

[rairiau-omr]

That looks like those backups may be stuck but you will have to work with support to analyze it. Can you open a case and let us know the support case ID?

Hello,

Case #04821792 opened.
Thanks.

[rairiau-omr]

Hello,

Finally the solution was simple, he have to launch a new full sync session on the job with the command "Start-VBOJob -RunAsync -Full", after that the backup is now Success for all of our SharePoint sites.

Thanks Veeam Support team.