Restore from S3 is launching the worker in the wrong subnet.

Background

A user may configure workers for S3 copy and File level restores, but when doing a restore from S3 the worker may get launched in a subnet other than what is defined in the Worker configuration screen in the CPM Console. 

This is the default behavior for a restore from S3 - The restore jobs Worker configuration overrides the settings defined in the CPM Console screen Worker Configuration.

Resolution

To set the worker configuration on the Recovery screen, there is a tab for the worker configuration, and that's where the subnet is set:

• Related Articles

• Resolving Snapshot Restore Failures from Cold Storage, Error: "not all blocks were processed"

  Issue During the process of restoring a snapshot from cold storage, the snapshot is successfully retrieved from cold storage to the hot tier (S3). However, the restore process may fail when retrieving from S3 to EBS with the following error: Worker ...

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

• How To Test Connectivity from a CPM Worker to AWS endpoints

  The Following Steps will help you Test the outgoing connection from the CPM Worker to AWS endpoints OR the CPM Server if you need to test to ensure that the Worker can reach the CPM server once it launches. Launch Worker First, ensure the CPM Worker ...

• CPM in Recovery Mode error - S3 worker fails with worker i-12345678912345678 stopped communicating - terminating operation

  CPM in Recovery Mode error - S3 worker fails with worker i-12345678912345678 stopped communicating - terminating operation Issue: When CPM is in recovery mode being used for DR drills, the original CPM’s process to detect “zombie” worker’s can be ...

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