VDI was introduced in SQL Server 7.0 and is supported and enhanced in later versions. It enables third party vendors to achieve the same performance characteristics as the SQL Server native backup/restore, and makes the full range of backup/restore functionality available. The virtual device interface (VDI) provides the highest online backup throughput with minimal degradation to the transaction workload, as well as the fastest possible restore times.
Informational: Shedding light on VSS and VDI backups in SQL Server Application vendors can consult the following guide for additional information about using VSS for SQL server backups.This section contains the specifications for SQL Server application programming interfaces intended for use by third-party backup software vendors. The Microsoft SQL Server product team is evaluating this requirement for the next major version of SQL server, and this Microsoft Knowledge Base (KB) article will be updated when additional information is available.įor additional information about SQL Server backup and restore operations, consult the following Microsoft TechNet webpage:īACKUP (Transact-SQL) For additional information about Volume Shadow Copy Service (VSS) and VDI backups in SQL server, consult the following MSDN blog post. The VDI connection requires the Sysadmin permission because the connection itself is capable of executing more than simple backup operations and involves shared resources between the client and server. This is a design limitation in the current versions of SQL Server. This may not be desirable in all environments and may cause third-party backup applications that use VDI to fail if the service accounts of the applications are configured to only have the db_backupoperator fixed database role.
Backup or restore operations that use the Microsoft SQL Server Virtual Device Interface (VDI) require that the server connection for SQL Server that is used to issue the BACKUP or RESTORE commands must be logged on as the sysadmin fixed server role.
0 kommentar(er)
