Best strategy for taking a full backup of 20+ SharePoint Team sites?

[Peter Grew]

Hey everyone,

We are preparing for a major infrastructure cleanup and audit, and I need to take local offsite backups of 20+ active SharePoint Team sites. This covers document libraries, custom lists, subsites, templates, and permissions across all site collections.

In the past, running manual site exports or scripting PowerShell downloads for this many sites resulted in frequent throttling issues, missing version history, and messy folder structures. I’m looking for an automated, multi-site approach to streamline the task.

For this project, I’m planning to use the Shoviv SharePoint Backup Tool. My goal is to set up a job-based batch export of all 20+ Team sites down to local or network storage, ensuring we have an exact, incremental restore point.

For those who have managed multi-site backups at this scale with Shoviv, I’d love your input on a few things:

1. What is the most efficient way to batch-add and run concurrent backup jobs for 20+ sites without hitting API throttling limits?
2. Does the tool reliably preserve deep subfolder hierarchies, metadata, and version history across all document libraries out of the box?
3. How well does the incremental backup option handle ongoing changes if we need to run secondary passes during off-peak hours?

Any advice, recommended job configurations, or pre-check tips before I trigger the bulk backup would be greatly appreciated! Thanks in advance.

[Author]

Posts