Veeam Backup & Replication 9.5 Update 4
Veeam Explorers User Guide
Related documents

Considerations and Limitations

This section lists considerations and known limitations of Veeam Explorer for Microsoft SQL Server.


  • When Veeam Explorer for Microsoft SQL Server is installed on a server on which both Veeam Backup & Replication and Veeam Backup for Microsoft Office 365 are installed, the notification settings will be inherited from the Veeam Backup and Replication Global Notification settings.


  • Veeam Explorer for Microsoft SQL Server does not support restore via PSDirect, VIX or Sphere API.
  • Table-level recovery is supported only for database tables with no external dependencies.
  • To restore an encrypted database, consider reading this Veeam Knowledge Base article.
  • The Replace logic is not supported when restoring schema objects.
  • To restore a database from the AlwaysOn availability group node as of the selected transaction state, make sure that all the nodes of such a group is located in the same time zone.


  • You can publish the same database more than once.

Mind that when a database that is already published is being republished with the same name, then all the changes that have been made to this database will be lost on a target SQL server, as it will be published anew.

  • After you unpublish a database, Veeam Explorer detaches such a database from the target SQL server but the restore point will continue to remain on the target machine for the next 15 minutes.
  • If a Veeam Explorer session has been terminated in any way other than by clicking Exit in the main menu (or by clicking the X button in the upper-right corner), then all the published databases will continue to remain attached to the target SQL server having the Recovery pending state.
  • If published databases have been manually renamed via SQL tools (for example, in Microsoft SQL Management Studio), then Veeam will not be able to unpublish such databases properly. In this case, all the renamed databases will continue to remain attached to the target SQL server and you will have to remove them manually using the SQL tools.
  • Databases cannot be published to a SQL cluster.
  • Published databases are ignored during backup.
  • Upon closing the Veeam Explorer console, all the published databases will be detached from the target SQL server automatically. The corresponding mount points will also be dismounted from under the C:\VeeamFLR directory.
This Document Help Center
User Guide for VMware vSphereUser Guide for Microsoft Hyper-VEnterprise Manager User GuideVeeam Cloud Connect GuideVeeam Agent Management GuideVeeam Explorers User GuideBackup and Restore of SQL Server DatabasesVeeam Plug-ins for Enterprise ApplicationsPowerShell ReferenceVeeam Explorers PowerShell ReferenceRESTful API ReferenceRequired Permissions ReferenceQuick Start Guide for VMware vSphereQuick Start Guide for Microsoft Hyper-VVeeam Backup for AWS DocumentationVeeam Availability for Nutanix AHV DocumentationVeeam Backup for Microsoft Office 365 DocumentationVeeam ONE DocumentationVeeam Agent for Windows DocumentationVeeam Agent for Linux DocumentationVeeam Management Pack Documentation
I want to report a typo

There is a misspelling right here:


I want to let the Veeam Documentation Team know about that.