N2WS-22879 - DR retention is not working as expected
Issue:
When DR retention setting is different from the general retention setting, the DR snapshots are deleted too early.
Solution:
- v4.2.1: Patch is available and attached to this KB.
- v4.2.0: Upgrade to 4.2.1 and apply 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 ...N2WS-23140 - incorrect dr cleanup message
Issue: during DR cleanup, there is an incorrect error message saying there might be issues because all backups succeeded. Cleanup did not mark any AWS dr backup for deletion for AWS policy testing. Only 7 of 7 dr backups completed successfully. ...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: ...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 ...