Staging SQL Server

To restore or export application item (database, schema or data) to the state as of the current restore point (that is, as of in the VM backup which is currently mounted to Veeam backup server), no extra configuration is needed. However, as described in the How Veeam Explorer for Microsoft SQL Server Works section, to support other scenarios, Veeam Explorer for Microsoft SQL Server needs a staging Microsoft SQL Server. In particular, it is required for the following operations:

• Restore to the state before selected transaction
• Export to selected point in time
• Export to the state before selected transaction

As a staging system, you can use the Microsoft SQL Server 2012 SP3 Express Edition that is shipped with the Veeam Backup & Replication setup - this will be the default staging server.

Check that the staging system meets the following prerequisites:

1. Make sure that staging SQL Server has the same or later version as the original SQL Server (the VM processed by Veeam job).
2. If the database you plan to restore utilizes any SQL Server feature that is supported in the certain edition of SQL Server, then the staging SQL Server must be not only of the same (or higher) version as the original SQL Server but also of the same (or higher) edition. For example, if the database was created with Backup Compression built-in feature of SQL Server, then you can use SQL Server 2008 R2 Standard Edition and higher as a staging system, but you cannot use SQL Server 2008 R2 Express Edition, as it does not support that feature. So, when planning for the staging SQL Server, check for edition-specific features of your source databases and make sure the staging system meets the above requirement.
3. SQL Server included in Microsoft SQL Server Failover Cluster cannot be used as a staging system.
4. Specific ports on staging server will be used during restore session, as described in the Used Ports section.
5. If you plan to add database(s) to Veeam Explorer scope manually, consider domain trusts.