N2WS-21940 - S3 Cleanup failing to start

• Related Articles

• 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-22420 - Copy to S3 failing with local device /dev//dev/xvdf (/dev/xvdf) does not exist

  Issue: Copy To S3 is failing with the following error: Solution: Patch for v4.1.1a is available and attached to this KB. Click here to go back to the Release notes: Release notes for the latest v4.1.x CPM release

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

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

• N2WS-23140 - incorrect dr cleanup message

  Issue: during DR cleanup, there is an incorrect error message saying there might be issues because all backups succeeded. Cleanup did not mark any AWS dr backup for deletion for AWS policy testing. Only 7 of 7 dr backups completed successfully. ...