DR process may time out due to exceeding the snapshot limit per region

• Related Articles

• Cross-region DR copy of encrypted snapshot may fail with "Copy failed due to an AWS limitation regarding default encryption key” error

  DR of encrypted snapshots may fail with the following error in the Backup log: Error - <DR Policy>, copy snapshot failed (in Backup account) due to an AWS limitation regarding default encryption key source <source region>, target <target region>, ...

• Complete_VSS operation may fail if snapshot takes more than 45 minutes to complete

  Complete_VSS operation may fail if snapshot takes more than 45 minutes to complete, due to exceeding the default VSS timeout: In order to verify this, you should check the Agent's logs - VSS script should fail with return code "3" immediately after ...

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

• CPM may mark a successful RDS DR as failed

  On rare occasions, CPM may mark a successful RDS DR as failed in Backup Monitor. When this happens, you can see the following messages in the backup log: Error - RDS DR copy snapshot failed for region “RegionName”….Reason: Cannot create the snapshot ...

• Snapshots may fail with "Reason: Maximum allowed active snapshot limit exceeded."

  Snapshots may fail with "Reason: Maximum allowed active snapshot limit exceeded." This means that you have exceeded Amazon's limit of snapshots per account (10000 by default). ...