N2WS-20766 - RDS export fails due to error "RestoreDBInstanceFromDBSnapshot operation: No default subnet detected"

• Related Articles

• N2WS-22770 - MySQL 5.7 RDS export to S3 fails

  Issue: RDS MySQL 5.7 export to S3 fails with "Failed to get DB schema or users from eks-website-prod: mysqldump failed with error code 2" Solution: v4.2.2 - install attached patch and do below steps

• Cross-Region DR RDS backup may fail with "Copy failed due to an AWS limitation regarding default encryption key” error

  RDS DR backup of encrypted snapshots between different regions may fail with the following error in the Backup log: Error - RDS DR, copy snapshot failed (to DR account) due to an AWS limitation regarding default encryption key (source US East (Ohio), ...

• N2WS-21963 - Copy to S3 fails with Failed to stop processor(s)

  Issue: Copy to S3 is failing with following error ERROR: add_error(segment_handler.py:322) copy of md table of segment 1 of volume vol-12345678, instance i-0987654321, backup 123 fail : Failed to stop processor(s): not all blocks were processed ...

• N2WS-21357 - Patch installation fails with Internal Server Error

  Issue: Patch installation fails with this error in the UI Solution: 1. Connect to the N2WS server via SSH, username is cpmuser and your selected keyPair 2. Run the following command sudo grep PrivateTmp /lib/systemd/system/apache2.service 3. If ...

• Cross region copy of RDS snapshots may fail with error: RDS DR copy snapshot failed (in Backup account). No matching KMS alias in target region

  Issue: The Following error may appear in the CPM Server logs: ERROR: start_copy_region(dr_rds.py:301) RDS DR copy snapshot failed (in Backup account). No matching KMS alias on target region (source EU (Frankfurt), target Asia Pacific (Singapore), RDS ...