Combine teams and SharePoint backup for teams

[kirderf]

It has come to our attention that when protecting a MS365 team with just a teams backup job, not all objects of the team is backed up. As an example, Class Notebooks and files stored outside the Documents folder (i.e. in the root SharePoint folder) is not backed up. The only way to protect thes items I mentioned is with a SharePoint backup job. So, to be able to protect all data in a team, including messages, a team must be protected with both a teams and a SharePoint job. This has been confirmed by Veeam support (case# 07569284).

This is all fine and not a big deal, but the issue is that if we create two jobs for the same team (teams+SharePoint) and they happen to run at the same time, we get a warning saying that the team/site "is already processed by another job". It makes no difference if we combine them into a single job or separate them in two jobs. This could be resolved by chaining jobs, but that is not a feature of Veeam Backup for MS365. Another approach is to set the start times so far apart that they are unlikely to run at the same time, but this is a bit hit and miss and can lead to skipped restore points.

According to support, there is currently no real solution or best practices for this scenario. My questions to you guys is how you handle teams backups? Do you just stick with the pure teams backup job and accept that not everything is backed up? Or do you not backup messages and just have a SharePoint job? If you are using two jobs for each team, how do you implement this to avoid the "is already processed by another job" message? Appreciate any suggestions we can get.

I would also like to propose a feature request, as I believe it is related: allow jobs to be chained, similar to how it is in VBR.

[Polina]

Hi Fredrik,

There should not be any overlapping issues when you protect a team and its site in a single job. If you see it differently, we should investigate it. Can you still collect logs confirming it? if so, please reopen your case, add logs there, and let me know once it's done.

Thanks!

[kirderf]

Hi Polina,

I did a couple of tests now and you are completely right. I ran three different jobs which included both teams and sites for the corresponding teams and there were no issues. I have no idea why I got different results this time around, but I guess it made some mistakes during my initial testing. When monitoring the backup job it seems that it processes the sites first and the teams are on hold until the sites and subsites finish.

Thank you for getting back to me and sorry for any confusion caused by my post.

[Polina]

I hope now your backups will go smoothly and all the data you need will be protected