This document is not maintained any longer.Examine Considerations and Limitations
In this article
- Transaction log backup is not supported for Windows Server 2008 or earlier guests on Hyper-V 2012 R2.
- 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.
- By default, system databases (master, model, msdb) are skipped from transaction log processing and are not a part of Veeam Explorer restore workflow. These databases can be restored using file-level restore, as described in the Veeam Backup & Replication User Guide (https://helpcenter.veeam.com/backup/vsphere/performing_guest_restore.html). If you want to exclude other database(s) from transaction log processing workflow, please refer to this Veeam Knowledge Base article: https://www.veeam.com/kb2104. (Consider that exclusion configured this way will be treated as a global setting.)
- 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).
- Currently, point-in-time restore and restore to the state before selected transaction is not supported for replica VMs and for restore points created by backup copy job.
- If you want to restore a database from AlwaysOn availability group node to the state as of prior to selected transaction, all nodes of the group should be located in the same time zone.
- If you plan to restore an encrypted database using Veeam Explorer for Microsoft SQL Server, consider information provided in this Knowledge Base article.
- Table-level recovery is supported only for database tables with no external dependencies.
- If you plan to restore database schema objects, consider that 'Replace' logic is not supported - that is, if an object with the same name exists in the production database and in the backup, then a backup object will not replace the existing one, but an object with a different name will be created instead, as described in the Restoring Database Schema and Data. Also, consider that when objects are renamed, relationships between them are not renamed.
- If both Microsoft SQL Server and Oracle Server are installed on one VM, and this VM is processed by a job with log backup enabled for both applications, Veeam Backup & Replication will back up only Oracle transaction logs. Microsoft SQL Server transaction logs will not be processed.