How to copy VMs deployed in AWS or Azure back to VMware


How to copy VMs deployed in AWS or Azure back to VMware


How to copy deployed VMs back to a VMWare server.


Boomerang offers two separate functions for moving previously replicated/deployed VMs from AWS/Azure.  To move a VM that has been replicated but not deployed the ‘Restore’ option can be used.  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 the ‘CopyBack’ option.
The Boomerang CopyBack option allows for copying deployed VMs in AWS/Azure back to VMware.   This option moves a previously deployed VMs from the cloud provider back to the local VMware environment and creates a new running VM in the process.  Of the two restore options, Restore/CopyBack, the CopyBack option will require more time to create the new local VM but it will create a VM that contains the latest state of the VM running in the Cloud.  The CopyBack option can only copy VMs that were replicated and deployed using Boomerang.


When a Protection Group has been deployed into AWS or Azure the dashboard will show how many VMs are deployed and available for copying back. 
First, click the name of the Protection Group containing the VMs you wish to copy back into the local VMware environment.
User-added image
Then, select “CopyBack Now”
User-added image
The next screen shows the list of Protection Group’s VMs that are deployed. Select VMs you wish to copy back into VMware.
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.  
For Azure environments the target environment screen above is the same except there is no ‘Ephemeral Subnet’ selection option as shown below.
AWS CopyBack parameters
User-added image
Azure CopyBack parameters
User-added image
Once the CopyBack operation starts, the progress will be displayed on the dashboard
Here is a sample AWS CopyBack progress screen
User-added image
Here is a sample Azure CopyBack progress screen
User-added image
Once the task has completed successfully, the newly created VMs can be found in the VMware environment. The VMs are named using the original VM name and the ID of the instance in AWS/Azure.
While a CopyBack task is running, the VM name has a prefix "Boomerang Copyback in progress" to help you identify VMs being updated. Do not delete or attempt to modify these VMs while the CopyBack is in progress. Doing so will result in the failure of the CopyBack operation.
User-added image

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