System Requirements
This section lists system requirements for Veeam Explorer for Microsoft SQL Server.
Component | Requirement |
---|---|
Microsoft SQL Server | For more information about supported versions of Microsoft SQL Server, see the Supported Applications subsection of the Veeam Backup & Replication User Guide. |
|
AlwaysOn Availability Groups are supported for Microsoft SQL Server 2012 and higher. |
Consider the following:
- By default, the AUTO_CLOSE option for SQL Server databases is set to False.
If AUTO_CLOSE is enabled, your databases might be skipped from processing.
- To restore database items from an SQL Server that is running Microsoft Windows ReFS, the Veeam backup server or a management console must be installed on Microsoft Windows Server 2012 or higher.
- To restore data from a server that is running Microsoft Windows ReFS 3.x, the Veeam backup server or a management console must be installed on Microsoft Windows Server 2016.
- Nodes participating in AlwaysOn Availability Groups are supported, but using Availability Group Listeners as staging servers is not recommended.
Staging SQL Server Requirements
- Make sure that the staging Microsoft SQL Server has the same or later version as the original SQL Server.
- An SQL Server included in Microsoft SQL Server Failover Cluster cannot be used as a staging system.
- Mind domain trusts configuration when planning to add databases to the Veeam Explorer scope manually. For more information, see Configuring Staging SQL Server.
- The following Microsoft SQL Server Express Editions can be used as a staging system:
- Microsoft SQL Server 2012 Express Edition.
For Microsoft Windows 2008 R2 and Windows 7.
- Microsoft SQL Server 2016 Express Edition.
For other higher versions.
Both editions come as part of the Veeam Backup & Replication distribution package.
- An SQL Server instance can be used as a staging system.
|
Databases that exceed 10 GB cannot be attached to the Microsoft SQL Server 2012/2016 Express Edition due to Express Edition limitations. For more information, see the following Microsoft articles: |