Cleanup process may abort due to timeout

• Related Articles

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

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

• 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): … ...

• CPM v3.0.x may launch unnecessarily large Cleanup workers, resulting in extra costs

  CPM v3.0.x may launch unnecessarily large Cleanup workers, resulting in extra costs. In order to reduce the costs, please use the following procedure: Connect (via ssh) to the machine running cpm (you will need to execute "sudo -i" to gain the root ...

• S3 backups may be skipped and S3 Cleanup may fail due to a locked policy

  Customers may experience problems with S3 operations leaving backup chains locked, preventing further operation on that chain. Theses issues are especially prevalent in v2.4.x, please upgrade to the latest version ASAP to significantly reduce ...