N2WS-17670 - Worker volumes might not get deleted after S3 copy job

• Related Articles

• How to retreive support logging from a CPM Worker Machine

  In cases where an S3 copy is failing, support may request logging from the CPM S3 worker appliance. This logging can be collected from the retained root volume of a failed worker or by setting termination protection on a running CPM worker instance. ...

• N2WS 3.1.x - worker reported error: failed processing segment 0 : Failed to load blocks meta-data

  Issue summary When running copy to S3 on version 3.1 it might fails with below error: Issue description and troubleshooting This error is usually caused by communication issues with the EBS Direct API endpoint. In version 3.1 we have started to use ...

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

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

• "Worker did not establish connection" and " worker did not complete initializing" errors during S3 and FLR

  During S3 operations, you may encounter the message "Worker i-... did not establish connection" in the log of an S3 copy or S3 restore operation. Error - Worker i-1234567890abcdef did not establish connection - terminating operation During File Level ...