Windows VSS backup failed (EC2)
What AWS reports
application-consistentvolume shadow copyMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
Application-consistent Windows backups rely on VSS and the SSM Agent. Failures come from missing permissions, an old SSM Agent, or the instance being too busy when the snapshot is taken.
How to fix it
- Give the EC2 instance profile / backup role the permissions needed for VSS backups.
- Install the latest SSM Agent and AWS Tools for PowerShell on the instance.
- Retry at a quieter time if the system was overloaded during the snapshot.
- Check the SSM Agent logs under C:\ProgramData\Amazon\SSM\Logs for the underlying error.
What AWS documents
AWS advises updating the SSM Agent, checking role permissions and reviewing the SSM logs for VSS failures.
Source: AWS Backup Developer Guide — Troubleshooting (Windows VSS)
Stop finding this one failure at a time
BackupLens watches every AWS Backup job across every region, matches each failure against this catalogue automatically, and sends you the cause and the fix — instead of a job list you have to read line by line at 3am.
Start free trial