Item has been changed during the backup

[Beheer]

Hello,

Since the upgrade of Veeam for M365 from 7.1.0.2031 to 8.1.1.159 (and later 8.1.2.180) we have some issues with files that Veeam reports as "Item has been changed during the backup." Causing warning emails that have to be looked into every day which is annoying.

I opened a case (Case #07770683) wanting to report this as a bug.
But I got back a list of actions to undertake to make these files not in use anymore. I was a bit annoyed about the assumption that the files must have been in use during backup, in particular cases I was shure they where not in use.
Finally removing the files and uploading them again to where they belong was the solution to get rid of the warnings. In all cases the files were stored in a Team or Onedrive and shared elsewere.

So after that I started testing with one file. The file is part of a Team. As soon as I create a link to that file and put the link in a Teams Chat, the file is reported as modified during backup.
Whereas in my opinion Veeam somehow THINKS the file is modified, just because it cannot handle the fact that there is a link to it. Because the file was definitely not in use by anyone during nightly backup.

Just wanted to report this, and I am in fact curious if others have the same issue.
The way we use files in Teams and Chats hasn't changed in recent months, the backup job hasn't changed, just the version of the Veeam software.
Since we are going to transfer our 6TB fileserver to Sharepoint/Teams, I expect these file modified issues to show up much more often in the future.

Regards,
Han

[Mildur]

Hi Han,

I see that you requested support to close the case.
To continue investigating the situation and confirm whether it is indeed a bug, the case should have been escalated to our QA team along with your findings. This is no longer possible, as the uploaded logs have now been automatically deleted.

If you encounter the same issue again, please open a new case and describe in details why you believe this has happened. If support can confirm that the root cause is related, we can then request an escalation to QA together with the logs files provided in your case.

Best,
Fabian

[Polina]

The issue should be fixed in the next product update.