N2WS-22770 - MySQL 5.7 RDS export to S3 fails

• Related Articles

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

  Issue: When trying to export RDS instance to S3 bucket, it fails with the following error: Error Process reported error: Failed to create DB instance from snapshot cpm-policy-1-db1-2011-1-11-1-11: An error occurred (InvalidSubnet) when calling the ...

• Read Only user for RDS to S3 feature

  Info Starting at version 4.x, N2WS now support exporting RDS MySQL database to S3 for long term cost saving, this is done using two steps: Using the existing AWS RDS export to S3 feature to copy the data to the S3 bucket Exporting the schema ( as ...

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

• EBS/RDS DR & Recovery with KMS key

  When copying cross account an EBS/RDS Volume encrypted with custom KMS, a KMS key should also be available in the other account. There are 2 ways that CPM uses for checking KMS key - Alias & Tag KMS Tag When using custom tag, you are telling CPM to ...

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