A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Purview is not the right tool for creating traditional backups of SharePoint, OneDrive, and Exchange. Purview focuses on compliance, eDiscovery, and governance, not operational backup/restore.
For Microsoft 365 data (SharePoint, OneDrive, Exchange), use Microsoft 365 Backup instead of Purview:
- Microsoft 365 Backup overview
- Backs up selected or all SharePoint sites, OneDrive accounts, and Exchange mailboxes.
- Provides fast backup and restore with full-fidelity rollback of sites and mailboxes to prior points in time.
- Retention and recovery points:
- SharePoint and OneDrive: 1-year retention; recovery points every 10 minutes for the last 2 weeks, then weekly snapshots for weeks 2–52.
- Exchange: 1-year retention; recovery points every 10 minutes for the last 52 weeks.
- Restore granularity:
- SharePoint: full site restore; file-level restores via versions (coming soon).
- OneDrive: full account restore; file-level via versions (coming soon).
- Exchange: full mailbox or item-level (mail, contacts, calendar, tasks).
- Performance expectations
- Backup: once a protection policy is activated, initial backup typically completes within hours, with about 15 minutes per 1,000 protection units initially or incrementally added.
- Restore:
- Up to 1,000 average-sized SharePoint sites or OneDrive accounts at 1–3 TB/hour.
- Up to 1,000 average-sized Exchange mailboxes at 1–3 TB/hour.
- Single-site/OneDrive express restore points can complete in 10–120 minutes depending on size.
- How to actually back up SharePoint, OneDrive, and Exchange with Microsoft 365 Backup
At a high level:
- Create protection policies that include:
- The SharePoint sites to protect.
- The OneDrive accounts to protect.
- The Exchange mailboxes to protect.
- Activate the protection policy.
- Wait for the initial backup to complete (typically within the timeframes above).
- Use the restore workflows to:
- Restore SharePoint sites in-place (same URL) or to a new URL.
- Restore OneDrive accounts in-place or to a new URL.
- Restore Exchange mailboxes or individual items to the same mailbox or a new folder.
- Create protection policies that include:
- If a backup/restore appears stuck
- For SharePoint Server on-premises, canceling a restore in progress is not recommended because it can leave the database in an unknown state; the guidance is to let it run to completion. The same principle applies conceptually to cloud restore operations: interrupting a long-running restore can leave data in a partially restored state.
- If a Microsoft 365 Backup operation appears to be running far longer than the documented expectations, open a support ticket with Microsoft 365 support so they can inspect the job state and cancel or remediate it from the service side if necessary.
- Alternative for on-premises SharePoint (if applicable)
If the environment is SharePoint Server on-premises rather than SharePoint in Microsoft 365, use farm/site collection backup tools instead of Purview:
- Use PowerShell
Backup-SPSiteto back up site collections:Backup-SPSite -Identity <SiteCollectionGUIDorURL> -Path <BackupFile> [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-Verbose]-
-Identityis the site collection URL or GUID. -
-Pathis the backup file path. -
-UseSqlSnapshotis recommended when using SQL Server Enterprise for more consistent backups.
-
- Ensure required roles:
securityadminon SQL instance,db_owneron relevant databases, and local Administrators on the server.
- Use PowerShell
Summary:
- Purview is not the correct platform for operational backups of SharePoint, OneDrive, and Exchange.
- Use Microsoft 365 Backup to protect and restore SharePoint sites, OneDrive accounts, and Exchange mailboxes in Microsoft 365.
- For on-premises SharePoint Server, use
Backup-SPSiteand related farm backup tools instead of Purview. - If a long-running restore/backup appears stuck, avoid force-canceling from the client side and instead involve Microsoft support.
References: