Issues: 1. In some rare cases, worker's volumes are not removed after worker instance is terminated 2. Unnecessary alert is raised when none default worker type is used: Worker i-12345 was launched for FLR as t2.micro, which may not an optimal ...
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. ...
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 ...
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 ...
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 ...