The chicken and egg of VSS
From Wikibon
Originating Author: David Vellante
With Exchange 2007, Microsoft has indicated that Volume Shadow Copy Services (otherwise known as VSS) is the future data protection methodology. VSS allows organizations to make point-in-time backups of an Exchange database (EDB) using third-party backup software. The VSS framework has evolved but by many accounts still is not robust enough for users.
The VSS framework has three main parts:
- A Requestor, which initiates and controls the creation of a copy of the EDB (typically a backup software application);
- A Writer, which does all the database housekeeping to prepare the EDB for a copy (typically the Exchange database or SQL); and,
- A Provider, which handles the actual copy function itself (typically an external storage array).
This backup ecosystem comprised of Microsoft, third party backup providers, and array vendors, is evolving but too slowly. As such, many users are uncomfortable betting the farm on VSS, and this will slow the adoption of next generation data protection approaches in Exchange 2007 environments. The industry needs to push the sophistication of VSS in general and storage providers specifically need to understand Exchange 2007 use cases and customer requirements.
Action Item: Microsoft's VSS framework represents an opportunity for backup vendors and array companies to partner with Microsoft to advance copy services and near continuous data protection. However the industry in general and Microsoft in particular must more aggressively push the sophistication of VSS and the integration within Exchange 2007 environments. Only when users have good visibility that this framework will meet future business requirements will Microsoft's VSS mandate be substantiated by market adoption.
Footnotes:
