This method takes two parameters as input and returns a void. The component in this article has one method named ExecuteCommand which, as the name implies, executes a backup or restore command to the VDI. Since the nature of the VDI is streaming data into and out of the SQL Server, it made sense to me to use a System.IO.Stream for communication between the. NET wrapper for the VDI using Managed C++.

Since the API for the VDI is designed to be consumed by C/C++, it made sense to develop a. Once you have a firm handle on the technologies outlined here, you can see this reference for more details on the VDI specification. There are many other capabilities of the VDI such as multiple input and output streams, and various performance tweaking opportunities. As such, only a very small subset of the VDI API is covered in this article. This article is meant to cover the basics of the VDI API and how to integrate it into a. With that being the case, I set out to develop a Managed C++ component which will act as a bridge between the 'Virtual Device Interface' (VDI) API and the. The only catch is that to the best of my knowledge, there is no easy way to access this API via the. Microsoft has published an API to access this functionality of SQL Server. This access allows you to perform any number of tasks on this data though the most common tasks are compressing and/or encrypting the data before it is written to disk.

Having access to these virtual devices gives you access to the raw data that is passed into and out of SQL Server during a backup or restore operation. The virtual device interface of SQL Server allows developers to define 'virtual devices' for SQL Server to backup and restore databases and transaction logs.

Sql server vdi backup