An AWS CopyBack task failed due to "Timeout occurred – Retry may solve it”


An AWS CopyBack task failed due to "Timeout occurred – Retry may solve it”


To move a VM that has already been deployed and may be running in AWS/Azure the ‘CopyBack’ option can be used.  This article discusses a timeout failure of the AWS ‘CopyBack’ function.


If an AWS CopyBack operation runs for a while and ultimately fails with the error “Timeout occurred – Retry may solve it” then there could be an issue with the EC2 subnet configuration specified when configuring the CopyBack.
After selecting VMs, select the destination VMWare server host/datastore/network for the CopyBack. For AWS environments, you must choose an “Ephemeral Subnet” that will be used.  For AWS, Boomerang will create a small EC2 instance that will be used to run commands needed to move VM data from the running EC2 into the S3 bucket defined for the protection group.  This EC2 instance requires full network access to S3 in order to complete the copy; the chosen subnet should have full access (all protocols) to S3.  Without this access the CopyBack will fail, usually with a timeout error. Once the CopyBack completes, the small EC2 instance is removed.  
AWS CopyBack parameters
User-added image

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us