To perform Microsoft SharePoint item recovery, Veeam Explorer requires a Microsoft SQL server as a staging system to create a temporary Microsoft SharePoint content database.
The server you are going to use as a staging system must conform to the following:
- A staging system must have the same or later version of Microsoft SQL Server that hosts restored Microsoft SharePoint databases.
- Microsoft SQL Server that is included in Microsoft SQL Server Failover Cluster cannot be used as a staging system.
- Nodes participating in AlwaysOn Availability Groups are supported. However, using Availability Group Listeners as staging servers is not recommended.
|
You can use the Microsoft SQL Server 2012 Express edition which is shipped with Veeam Backup & Replication as a staging system. However, due to Express edition limitations, the maximum database size that can be attached is 10GB. For more information, see this Microsoft article. |
A BLOB store must either be included in the SharePoint backup created by Veeam Backup & Replication or Veeam Agent for Microsoft Windows (for automated discovery) or stored on a local machine running Veeam Explorer (for manual discovery).
|
Third-party RBS providers are not supported in the current version. |
Make sure the staging SQL Server configuration meets the following requirements:
- FILESTREAM must be enabled on a database server, as described in the following articles:
- For SQL Server 2017 for Windows, see this Microsoft article.
- For SQL Server 2016, see this Microsoft article
- For SQL Server 2014, see this Microsoft article
- For SQL Server 2012, see this Microsoft article
- For SQL Server 2008R2, see this Microsoft article
- RBS Client Library must be installed on the database server.
For Microsoft SQL Server 2014 and later, the Remote Blob Store setup is included in the installation media. For other versions you can use the corresponding Microsoft SQL Server Remote Blob Store installation package (RBS.msi):
- For SQL Server 2012, see this Microsoft article
- For SQL Server 2008R2, see this Microsoft article
