N2WS-21382 - S3 copy worker issues

• Related Articles

• Copy backup to S3 may fail with the error message "Workers could not be launched"

  During backup copy to S3 a worker creation may fail with the error (backup.log): - Error - Workers could not be launched The worker usually fails right after it was started. There are several possible issues that gives you this error. 1) The was an ...

• Copy to S3 fails after upgrade to 4.2.2

  Issue: Backup of snapshots to S3 bucket is failing after upgrade from 4.1 to 4.2.2 Solution: One possible reason for such an issue is the change in default behavior. In 4.2.2 we introduced the option to launch a worker with a IAM role attached to it. ...

• N2WS-23161 - When server fails to terminate worker, it is failing to add log message

  Issue: When N2WS Server is failing to terminate a worker instance, there is an exception when adding the log Traceback (most recent call last): File "./cpmserver/cpm/backup_copy/proxy_operations.py", line 194, in terminate_proxy File ...

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

• How to change instance type of S3 worker instances CPM

  Some clients may need worker instances with more ram and CPU power. You can use this process to modify the ec2 instance type used for worker instances. We highly recommend not to change size unless it was suggested by the N2WS support team. Otherwise ...