Cleanup Log

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.


Added in v2.1.3

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

    • Daily Summary/Cleanup Log may alert of false Cleanup issues

      You may receive the following warning in Daily Summary or Cleanup Log: Warning - Cleanup did not mark any backups for deletion for policy DailyPolicy, because out of 3 completed backups, only 1 were marked as successful This warning may be triggered ...

    • Cleanup process may abort due to timeout

      If Cleanup process doesn't end successfully, download the cpm logs and search for the following consecutive messages: ERROR: get_cleanup_data_request(.\common\agentapi_requests.py:146) failed calling url https://127.0.0.1:443/agentapi/cleanup/. ...

    • Cleanup process may end abruptly with UnboundLocalError after upgrade to v2.3.x

      If Cleanup process doesn't complete successfully in v2.3.0/a/b, please download the logs and look for the below print: ERROR: _run_job…"cleanup_function (trigger: interval…, next run at: …" raised an exception Traceback (most recent call last): … ...

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