Veeam M365 unarchives Teams - makes no sense

[StephanG]

Hi everyone,

just for discussion - as this makes no sense and is nowhere documented as KB(?).

-- Ticket answer --
Reviewed the behavior you described against a matching Veeam Data Cloud for Microsoft 365 case pattern, and what you are seeing aligns with a known VDC M365 issue where archived Microsoft Teams can be unarchived during backup processing because the archival-related property is not preserved correctly on the Microsoft 365 side.
This means the archive or unarchive entries in Purview are not expected user activity from your side; they can be generated by Veeam Data Cloud for Microsoft 365 while processing already archived Teams.
To prevent further status changes for archived Teams, open the Veeam Data Cloud for Microsoft 365 web interface and exclude the archived Teams from the backup configuration so they are no longer processed by backup jobs. This is the current workaround available for this issue.
-- Ticket answer --

We have about 16k Teams and many of them are archived because of project end whatsoever - a manual exclusion is not possible. Did this issue also come up with some of you? And how did you fix it?

BR
Stephan

[Polina]

Hi Stephan,

To address your question, I need to understand first what the issue is - please provide you support case ID.

To protect an archived team, VDC indeed needs to temporarily unarchive it. The only way to avoid it, exclude such a team from processing.

Thanks!

[StephanG]

Hi Polina,

the ID is 08092307 - but it seems like some of them stay unarchived. Also - if a Teams is Read Only there are no changes to the files and Teams anymore. So it just needs to be backuped once.

[Polina]

If there're occurrences when a team's archived status is not preserved after backup, RND will investigate it. Assigning the archived status back to a team is the last step in its backup process, and in some rare cases if the operation was interrupted or some glitch occured, VDC may not be able to complete such an archival. Nevertheless, we'll look into it.

For incremental backup, VDC relies on change tokens saved for an object rather than it's state (i.e. archived or read-only). Tokens indicate if any changes occurred to the object since the last backup run and they need to be saved to backup.