Separate requester, writer, and provider roles when reviewing VSS backups

Source facts

Microsoft’s VSS reference separates three roles. A requester initiates shadow-copy operations and is commonly the backup application. A writer prepares a consistent application data set. A provider creates and maintains the shadow copy; that work can occur in software or storage hardware. VSS coordinates the components during shadow-copy creation.

Applicability

Identify the backup product, protected applications, and storage arrangement actually in use. Check the relevant product documentation before assuming that a particular application supplies a writer or that a storage array supplies the selected provider. Keep this component review distinct from decisions about backup retention and recovery objectives.

DSE recommendation

Create a short component map for each protected workload. Name the requester, required writers, selected provider, and administrator responsible for investigating each. During a failure review, preserve the original job details and timestamps before retrying. Ask which component reported the failure and which application data was included, rather than assigning every failure to the backup application by default.

Verification

Record component status around a controlled backup and preserve the corresponding application and backup logs. Restore a representative data set through the approved recovery procedure and have the application owner validate it. Keep successful snapshot creation and successful application restoration as separate results in the evidence record. Document missing components or unexplained errors as unresolved findings.

Official references

Microsoft Learn: Volume Shadow Copy Service. Source reviewed September 8, 2026.