This article can also be found in the Premium Editorial Download "Storage magazine: Everything you needed to know about object-based storage."
Download it now to read this article plus other related content.
For many Windows Server-based applications, Microsoft provides some core “plumbing” for enabling backups called Volume Shadow Copy Service (VSS). Along with the VSS foundation within the Windows OS, there are three active components:
- VSS Requester includes components typically found in a traditional backup agent (often from a third party) that initiate the backup process.
- VSS Writer components in the application (e.g., SQL Server, Exchange or even the Windows file system) ensure the workload is ready to be backed up by performing tasks such as flushing memory-based transactions or other backup preparation.
- VSS Provider components in the storage layer (OS software based or hardware based) capture a snapshot of the data set to be protected.
Essentially, a VSS-based backup works in eight relatively straightforward steps:
- A backup agent’s VSS Requester queries VSS for workloads that are capable of being backed up.
- VSS enumerates any workloads that have registered their VSS Writer.
- The backup agent’s VSS Requester requests that the workload be prepared for backup.
- The workload’s VSS Writer does what’s specifically required for that workload to be backed up.
- After preparation,
- the workload’s VSS Writer notifies VSS and its VSS Provider that its data is ready.
- The VSS Provider snaps the data set and notifies the VSS Requester that it has the data.
- The VSS Requester references the (usually temporary) snapshot within the VSS Provider and sends the appropriate data to the backup server.
- Upon completion of the backup and acknowledgement by the backup server, VSS can notify the VSS Provider that it’s free to release the snapped data and the VSS Writer that its data is secure. The workload can then do its post-backup maintenance tasks.
This was first published in June 2012