Skip to main content
All CollectionsKnowledge BaseAWS WorkloadsTroubleshooting - AWS Workloads
EC2 Consistent AMI Backups Failing with 'Failed to Run Commands: Exit Status 1'
EC2 Consistent AMI Backups Failing with 'Failed to Run Commands: Exit Status 1'
Updated over a month ago

Problem description

When an EC2 instance assigned to a backup policy for consistent AMI backups encounters the following error:

Resolution

  1. Make sure Amazon SSM Agent and VSS processes are excluded from Sentinel One, Symantec and SAP Application.

  2. We expect all the VSS writer statuses to be in a stable state, basically we shouldn't be observing any "Waiting for completion" status.

  3. On the server, start the following services

    1. Background Intelligent Transfer Service,

    2. COM+ Event System,

    3. COM+ System Application,

    4. Cryptographic Services

    5. Volume Shadow Copy

    6. Microsoft Software Shadow Copy Provider

  4. If any anti virus application is installed on the Ec2 instance . We would recommend as a best practice to exclude the following from anti virus:

    1. VSS processes ( vssadmin.exe, vssvc.exe, swprc.dll etc )

    2. Folder "C:\ProgramData\Amazon\SSM\"

    3. Process to be excluded 'amazon-ssm-agent.exe'

  5. If the VSS writer status is still Waiting for completion, we would recommend rebooting the server once.

Related Articles
Set up EC2 instance for Consistent Snapshots
EC2 backups with VSS enabled fail in CloudRanger with the Error 'An error occurred in the SSM command. no AMI was created'
EC2 Instance Backup fails in CloudRanger at the step 'aws/monitor/consistentinstancesnapshot'
EC2 backups with VSS enabled fail in CloudRanger with the Error 'You cannot call a method on a null-valued expression At C:\ProgramData\Amazon\SSM\InstanceData\...\document\orchestration\...\awsrunPowerShellScript\0.awsrunPowerShellScript script.ps1'
SQL backup failed: Vss Error: Operation timedout of gathering writer metadata
Did this answer your question?