Snapshots may not get deleted if cleanup is running for more than 1 hour

If snapshots which are out of retention are not deleted by cleanup, please download CPM logs from GUI.

Please check for the “Last Cleanup” time in “General Settings”, next to the “Run Now” button.

Please search the logs for these 3 errors approximately 1 hour after the “Last Cleanup” time:

ERROR: get_status(connection.py:<Line Number>) 400 Bad Request
ERROR: get_status(connection.py: <Line Number> <?xml version="1.0" encoding="UTF-8"?><Response><Errors><Error><Code>RequestExpired</Code><Message>Request has expired.</Message></Error></Errors><RequestID><Reques ID></RequestID></Response>
ERROR: cleanup_function(.\cpmagent\agent.py:<Line Number>) Failed to delete snapshot snap-<Snapshot Number> (policy <Policy Name>), delete operation failed. Reason: Request has expired. (error: RequestExpired)

To resolve this issue, please upgrade to latest 2.X.X version.

Reference defect number - 4a17dc5357, fixed in v2.1.2

Link to the Release Notes and the latest patch - https://support.n2ws.com/portal/kb/articles/release-notes-for-the-latest-v2-1-x-cpm-patch

Related Articles
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 ...
How cleanup works and why it might not delete snapshots older than the defined retention in CPM 3.0 and above
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 ...
Snapshot and backup records may not be deleted during cleanup - although snapshots are deleted in EC2 and backups are hidden in GUI
If you have CPM Server v2.1.3a, snapshot and backup records may not be deleted during cleanup from CPM's internal database - although snapshots are deleted in EC2 and backups are hidden in GUI If you have v2.1.3a, please upgrade to the latest 2.1.X ...
Cross-account replicated RDS snapshots may not get deleted or get tagged for deletion
Cross-account replicated RDS snapshots may not get deleted or get tagged for deletion during Cleanup. If you face this issue, please upgrade to latest 2.X.X version Reference defect number - N2WS-619, fixed in v2.2.0 Link to Release Notes and the ...
CPM may mark a successful RDS snapshot as failed
CPM may mark a successful RDS snapshot as failed. In the backup log you may see the following error: Error - snapshot of database <DBname> failed. There may also be a "rate exceeded" error in the CPM server logs: ERROR: get_list(connection.py:1180) ...

Snapshots may not get deleted if cleanup is running for more than 1 hour

Snapshots may not get deleted if cleanup is running for more than 1 hour

Related Articles

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

How cleanup works and why it might not delete snapshots older than the defined retention in CPM 3.0 and above

Snapshot and backup records may not be deleted during cleanup - although snapshots are deleted in EC2 and backups are hidden in GUI

Cross-account replicated RDS snapshots may not get deleted or get tagged for deletion

CPM may mark a successful RDS snapshot as failed