Cleanup Log

This feature was added to allow CPM users to better understand whether Cleanup process ran successfully.

It can be found in the “General Settings” tab.

The Cleanup Interval may be set to run every 1 to 24 hours.

Last cleanup timestamp will show the last time the Cleanup completed running.

Cleanup log shows the log of the last run. It provides information about which snapshots or AMIs were deleted and of which type (Volumes, DR snapshots, DB snapshots etc)

The log may be downloaded in csv format.

Run Now- Will start running the cleanup process instantly, regardless of its scheduled time.

The bottom section of the cleanup can help you to define:

      Rotate single AMIs: How often to rotate AMIs.

      Keep deleted records: Whether to keep deleted records for a certain number of days.

     Keep user audit logs: How long should the cleanup process keep audit logs.

Keep Resource Control Records: How many resource control group records you wish to keep

 

 

• Related Articles

• N2WS-21092 - S3 cleanup fails with Out of range value

  Issue: Cleanup is failing with below error in the cpm_server logs ERROR: other_maintenance_tasks(handlers.py:2003) Failed running S3 cleanup for disabled policies, encountered an exception Traceback (most recent call last): File ...

• N2WS-21940 - S3 Cleanup failing to start

  Issue: cleanup process is showing as not started for a long long time in S3 cleanup log 9/10/2022 22:12 Info ===== Cleanup of policy xyz (account: MyAccount, user: MyUser) ===== And error is shown in the logs Traceback (most recent call last): File ...

• Cleanup from S3 or S3 copy fails with error: Worker configuration not found

  Issue: When running a Copy to S3 policy, you may receive an error that states Worker configuration not found Or when S3 cleanup runs, you may see similar error in S3 cleanup logs. Solution The error will specify the region and/or account that a ...

• N2WS-23161 - When server fails to terminate worker, it is failing to add log message

  Issue: When N2WS Server is failing to terminate a worker instance, there is an exception when adding the log Traceback (most recent call last): File "./cpmserver/cpm/backup_copy/proxy_operations.py", line 194, in terminate_proxy File ...

• 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 ...