Considerations and Limitations

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

General

  • 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.

Restore

  • 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, the nodes of such a group must be located in the same time zone.

Publishing

  • During publishing, Veeam Explorer for Microsoft SQL Server mounts VMs disks from the backup file to the target machine (under the C:\VeeamFLR directory), retrieves required database files and attaches associated databases directly to your SQL server so that you can perform required operations using Microsoft SQL tools such as Microsoft SQL Management Studio.

When publishing to a cluster, all VMs disks become part of the target cluster.

  • You can publish the same database more than once.
  • After you unpublish a database, Veeam Explorer for Microsoft SQL Server 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 for Microsoft SQL Server 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 with the Recovery pending state.
  • If published databases have been renamed manually via SQL tools (for example, in Microsoft SQL Management Studio), then Veeam Explorer for Microsoft SQL Server 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.
  • Veeam Explorer for Microsoft SQL Server does not back up published databases.
  • 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.
I want to report a typo

There is a misspelling right here:

 

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