Background
When a new Team is created in Teams, a linked SharePoint site of the same name is automatically created. When a user creates a private channel or shared channel within that Team, however, a different site named {team name}-{channel name} is created. This is a Microsoft security measure to prevent any user who is a member of the Team but not of the private/shared channel from accessing the files housed in the private/shared channel's Files tab.
Because Redstor backs up Teams based on their linked SharePoint sites, this security measure means that the Files tabs of private/shared channels are not currently protected as part of Teams backups.
Note: All standard Teams channels are fully protected. This issue is limited to the Files tab of private/shared channels within a Team.
Workaround
These private/shared channel files are protected as part of SharePoint, but not of Teams. As such, the files are fully recoverable if you also back up SharePoint with Redstor. You will need to manually add the separate private/shared channel SharePoint sites to your backup set.
If you back up only Teams with Redstor and your organisation regularly makes use of private/shared channels, you will need to add SharePoint backup to your Redstor subscription to ensure that those files are protected.
The backup process then works as follows:
- Private/shared channel files are backed up using the SharePoint backup set.
- Private/shared channel messages and metadata are backed up using the Teams backup set.
- When recovering private/shared channels, the best option is to do a New Folder/Overwrite recovery. If you use InstantData, private/shared channel messages and metadata will be restored as .json files.
Comments
0 comments
Article is closed for comments.