CPM cleanup may fail with delete operation failed. Reason: The snapshot is currently in use by ami- ######## (error: InvalidSnapshot.InUse)

2019-09-30 23:16:54,583:[140578705110784][----------] ERROR:  append_records_to_volumes_snaps_deleted_list(agent.py:3615)  Failed to delete snapshot snap-47212b19 (policy Daily_Snaps), delete operation failed. Reason: The snapshot snap-472ce123 is currently in use by ami-dd3b20bc  

 

 

 Resolution:

This error can be resolved by searching the EC2 console under AMI's for this id  ami-cc3b20ad and then deregister the AMI. 

 

The above message appears in the cpm_agent.log and what you may want to do is download and uncompress the CPM log bundle from the bottom of the CPM Web GUI.

1. Open the logs in a  text editor like notepad++ (free and works great). 

2. Then search all the log files for the snapshot ids or the AMI id. This will help you locate the policy names and narrow down which account to search in if using multiple accounts.

3. The next step after you know the policy name is to look in the configuration.csv and search for the policy name and it shows which account owns the policy

4. Search Under the heading "Policies"  Which will help you locate the account associated with the policy.

This is a screenshot of the configuration.csv and I searched for that policy and you can see the account name circled in red.

5. Open the AWS EC2 console and search that account under AMI's or snapshot ids.

6. Please right-click on the AMI and select deregister AMI and when the next cleanup runs the snapshot should be removed.

• Related Articles

• How cleanup works and why it might not delete snapshots older than the defined retention setting.

  Background This KB Article will explain how the cleanup process works and why sometimes cleanup might not delete old snapshots It includes following sections: About the cleanup process Why Cleanup might not delete old snapshots Examples About the ...

• N2WS-19169 - Cleanup may fail because of "Can't find mapping for account "

  Issue: Cleanup process may fail because server fails to clean cross-region AMI DR: ERROR: get_account_dict(account_utils.py:114) account PolicyName(user root) not found in account map, even after refresh. ERROR: ...

• DR of an encrypted snapshot may fail with the “Not Authorized to use key” error

  Problem: DR copy may fail with errors like “Not authorized to perform” or “not authorized to use key” Example in CPM backup log: 10-24-18 10:11:04 - Error - Volume DR copy snapshot failed for region US East (N. Virginia), snapshot ...

• Cleanup may not delete snapshots older than the defined retention for the policy

  CPM removes the snapshots in accordance with defined retention policies. However, only successful backups are counted towards the retention. It is crucial to understand what a "successful backup" is. A "successful backup" is a backup that has both ...

• Instance recovery may fail with the error "You are not authorized to perform this operation"

  Instance recovery may fail with the error "You are not authorized to perform this operation" : ERROR: recover_ebs_based_instance(.\cpmserver\cpm\recovery.py:749) Run_instance failed. Exception: EC2ResponseError: 403 Forbidden <?xml version="1.0" ...