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. and by default launch it with a role if not configured otherwise.

The way copy to S3 works is, there are 2 accounts involved in copy operation: the account of the copied snapshot (or policy) and the account that owns the repository. These may be the same account, or they can be different. In case they are different, the server would provide the worker with 2 sets of credentials (the way it works in 4.1.1), one for each account.

However, when using instance role(new 4.2.2 option), there’s only a single role, and user has to make sure that this single role has access to both accounts. If using worker with IAM role was not intentionally configured, then setting proper permissions was most likely not done.

A possible solution is to make sure you have configured a worker configuration for the user/account/region(1) combination, and selected "No role" option(3) in the worker role(2) dropdown

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

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

• N2WS-21382 - S3 copy worker issues

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

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

• S3 Cleanup fails with error on worker - No progress was reported - terminating operation

  Issue: S3 cleanup fails and reports error from worker - No progress was reported - terminating operation This occurs in version 4.2.2 and the error occurs when the worker reaches its 1 hour timeout while attempting to cleanup large snapshots. To fix ...