The following system requirements should be met.
Microsoft SQL Server
AlwaysOn Availability Groups are supported for Microsoft SQL Server 2012 and later. See the Considerations and Limitations section for details.
For export to selected point in time and for export/restore to the state before selected transaction, Veeam Explorer for Microsoft SQL Server uses a staging Microsoft SQL Server. By default, local Microsoft SQL Server deployed with Veeam backup server will be used as a staging system.
If you plan to use another server as a staging Microsoft SQL Server, then it should have the same or later version as the original Microsoft SQL Server. Besides, if the source database uses any edition-specific features, then staging system should be of the same or higher edition than the original SQL Server. See the Staging SQL Server section for details.
Also, consider the following:
- By default, the AUTO_CLOSE option for SQL Server databases is set to False. However, check that this setting is False for the database you plan to restore (if AUTO_CLOSE is turned on, this may lead to database being skipped from processing).
- If you plan to restore database items from an SQL Server VM running Microsoft Windows ReFS, consider that Veeam backup server or management console (that is, the machine where Veeam Explorer and the mount service are running) must be installed on the Microsoft Windows Server 2012 or later.
- To restore from a server running Microsoft Windows ReFS 3.x, Veeam backup server or management console (that is, the machine where Veeam Explorer and the mount service are running) must be installed on the Microsoft Windows Server 2016.
- SQL Server 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.