DR may fail with "DR encountered an internal problem and failed" instead of printing the actual permissions issue

DR may fail with "DR encountered an internal problem and failed" instead of printing the actual permissions issue with CPM role.

You may find the error message below in backup log. This message is not informative.

Error - DR encountered an internal problem and failed

If you see the above error in the backup log, please open the server log and search for the below error

ClientError: An error occurred (AccessDenied) when calling the DescribeOptionGroups operation: User: arn:aws:sts::346423605891:assumed-role/CPM_full_backup/i-00e0c16af762b269c is not authorized to perform: rds:DescribeOptionGroups

Please check the AWS permission's policy for the account mentioned so as to find insufficient ones:

After adding all necessary permissions for the failed account, the policy should run properly.

Reference defect number – N2WS-3578, fixed in v2.4.0

Link to Release Notes and the latest patch – https://support.n2ws.com/portal/kb/articles/release-notes-for-the-latest-v2-4-x-cpm-release

• Related Articles

• DR of an encrypted snapshot may fail with the “Not Authorized to use key” error

  Problem: DR copy may fail with errors like “Not authorized to perform” or “not authorized to use key” Example in CPM backup log: 10-24-18 10:11:04 - Error - Volume DR copy snapshot failed for region US East (N. Virginia), snapshot ...

• Backups may fail with "CPM Server identified this backup as orphaned: marking as failed" after upgrade to v2.3.x

  Backups may fail with "CPM Server identified this backup as orphaned: marking as failed” error after upgrading to 2.3.0X and logs may show the below prints: update_request(agentapi_requests.py:<line_number>) failed calling url ...

• DR of encrypted snapshots may fail with the “No matching KMS alias” error

  DR of encrypted snapshots may fail with the following error in the Backup log: ERROR: start_copy_region(.\cpmserver\cpm\dr_volume.py:<line number>) Volume DR copy snapshot failed (in Backup account). No matching KMS alias on target region (source ...

• DR may fail due to the "snap-0123456789abcdef failed, has status error" error

  If Cross-Region DR fails with the following error in the Backup Log: Error - Volume DR copy snapshot failed for region <Region Name>, snapshot snap-<snapshot_ID>e (status: error).” Please download the logs from CPM GUI and search for the following: ...

• Cross-account DR may fail with the "RequestLimitExceeded" error

  The Cross-Account DR may fail with the following error in the Backup Log:  Error,"Volume DR copy snapshot failed for region <Region Name>, snapshot snap-<Snapshot Number> (to DR account). Reason:       Failed adding share permission to snapshot ...