N2WS-23140 - incorrect dr cleanup message

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

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

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

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

• DR may delay replication of some snapshots (showing them as "pending") with "Too many snapshot copies in progress"

  DR may delay replication of some snapshots (showing them as "pending") with the following message printed in the logs: "Volume DR We reached the max limit of snapshot copy requests for region US East (N. Virginia) (policy POLICY_NAME,in Backup ...