Sharepoint List Attachments Corrupt When Restoring

[veeeammeupscotty]

When restoring a Sharepoint list, it completes successfully and list item attachments are all there with the correct sizes, but they are all corrupt and cannot be opened. Doesn't matter what the file types are (pdf, xlsx, jpg, etc). Has anyone seen this behavior?

We are on the latest build (7.0.0.2914). Case 05951404.

[Mildur]

Hi JP

I cannot find similar reports in the latest support cases. It doesn't affect other customers.
Please keep working with support on this issue.

Best,
Fabian

[f.neumann]

We're facing the exact same issue with a customer and a restored sharepoint-list back in 2023. (Case # 07212152)
Now we've noticed, that all attachments, that have been restored, are corrupted and can no longer be opened (in recent veeam explorer-restorepoints as well as in sharepoint online).
Files are still there - exact same size in Bytes, but corrupted...

Luckily we still have veeam 365 restore points from before that restore, so all attachments can be recovered manually using veeam explorer one by one going to every list element and checking every attachment...

Just to make sure it’s no one-time issue from the past, i reproduced the issue within another microsoft-tenant and veeam 365 environment (V 7.1.0.1501):
• Created new sharepoint-list
• Added two Items
• Added one pdf-attachment to each item
• Checked if all attachment can be opened
• Backed up using Veeam 365
• Restored whole list using Veeam 365 to original sharepoint-online list
• All attachments are corrupted – files can no longer be opened in sharepoint online

Please have a look into this - as there are no errors during restore, i expect successfull restore.
And due to the problem itself it might be unnoticed for a longer time.

Very unhappy to see, that this was reported one year ago and still seems to be an issue today!

[f.neumann]

Okay, thanks to very fast Support-Team!
A lot of manual restore/merge work will follow with customer, but for future restores there's a hotfix adressing this issue.
Wish we had this hotfix back in November, when the problematic restore happened.

[Mildur]

Hi Florian

Thank you for the case number.
I checked with RnD. The issue was fixed in march and will be included in our upcoming releases.

Best,
Fabian