Protection of files with microsoft purview sensitivity labels

[lukasholzknecht]

Quick question to all who offer Veeam Backup for Microsoft 365 as SAAS to their customers. Since VBO was unable to correctly backup files with purview sensitivity labels from builds 8.0.2.159 through 8.1.2.180 (see https://www.veeam.com/kb4754), how do you manage your tenants data after the upgrade to build 8.2.0.2008? Since tenants data is processed incremental, already existing documents in the backup repository keeps corrupt since they don't get backed up again. (suggestion from veeam support was to make a minor change in the affected documents to trigger a new, which obviously isn't a implementable way since usually we're talking about thousands of files which are distribuited all over the users onedrives and SPO itself (Case # 07906862)). Has anyone tested, if the affected documents are restorable after a full backup (start-vbojob -job $job" -full:$true) or do you even have to perform a completely new backup to another repository?

Regards,

[Polina]

Hi Lukas,

If you force a full backup:
- New versions of an impacted file (if any) will be re-backed up healthy and restorable
-- Older versions of the same file in previous restore points will remain corrupted
- If there were no changes to an impacted file since the previous backup (i.e. there're no new versions), it'll be skipped from processing and in previous restore points it will remain corrupted.

With the next product update, we are going to deliver a mechanism to repair the older and impacted files.

Thanks!

[lukasholzknecht]

Hi Polina,
any ETA for next product release? We have to evaluate if we have to backup our customers from scratch or if it would be a possible solution to wait until the next version of VBO gets released.

thanks,

[Polina]

I currently expect it within the next two weeks.