Problem description
EC2 instance backups initiated from Druva CloudRanger may fail at the step aws/monitor/consistentinstancesnapshot. When this step fails, the backup job halts with errors such as InvocationDoesNotExist reported in the job traceback.
Cause
This issue occurs when one or more required AWS components on the EC2 instance are either missing or outdated.
The most common causes include:
AWS CLI is not installed or is running an outdated version.
AWS Tools for PowerShell are not installed or are outdated.
AWS Systems Manager (SSM) Agent is missing or outdated.
The EC2Launch folder structure is missing.
EC2Config is not updated to the latest version.
Traceback
{
"step": "aws/monitor/consistentinstancesnapshot",
"is_success": false,
"status_code": "InvocationDoesNotExist",
"started_at": "2023-04-27T18:30:24.000Z",
"finished_at": "2023-04-27T18:30:24.000Z"
}Additional signs include failures in SSM Run Command execution or inability to create AMIs.
Resolution
Follow these steps to update or install the required AWS components and resolve the issue.
1. Upgrade the AWS CLI
Install the latest version using the AWS CLI installation guide.
Verify with:
aws --version
2. Install or Upgrade AWS Tools for PowerShell
Follow the steps in the AWS Tools for PowerShell setup guide.
Verify with:
Get-AWSPowerShellVersion
3. Install or Update the AWS SSM Agent
On Windows, check the service status with:
Get-Service AmazonSSMAgent
4. Install or Update EC2Launch (Windows AMIs)
For Windows AMIs launched after 2016, refer to the EC2Launch download guide.
5. Install or Update EC2Config (Older Windows AMIs)
For pre-2016 AMIs, use the EC2Config installation guide.
6. Reboot the EC2 Instance
After updating all components, reboot the instance to ensure the services are running properly.
Verification
After reboot:
Run
aws --versionto verify AWS CLI.Run
Get-AWSPowerShellVersionto verify PowerShell tools.Confirm SSM Agent is running.
Verify EC2Launch or EC2Config version in the system.