How to do a Full Server Restore to Amazon EC2

This post applies to CloudBerry Backup 4.5 and later.

In this post, we explain how to do Full Server Local to Cloud Restore on Amazon Elastic Compute Cloud (Amazon EC2) service for Disaster Recovery (DR) with CloudBerry Backup, a powerful solution that allows you to automate your backup and restore processes.

First of all, you need to create a snapshot of your server by taking advantage of the CloudBerry Image Based Backup feature. Once it is done, you can go ahead and restore this server snapshot to Amazon EC2 service as shown below.

How to do Full Server Restore to Amazon EC2 with CloudBerry Backup

1. Launch CloudBerry Backup, click Restore button on the toolbar and follow the Restore Wizard steps to create a new restore plan.

2.  In the "Type of Data" step of the Wizard, select Restore Image Based Backup option.

3. Then select the Restore as Amazon EC2 Instance option.

You may as well want to create the Amazon Machine Image (AMI) by using the Create AMI option. This option allows you to automatically run a restored virtual machine and finally you will have a running system with a personalized IP address. Without that option, you will have to configure an IP address (Elastic IP) and start the restore machine manually in the AWS EC2 Management Console.

To create the AMI while restoring your server as EC2 Instance, just select Create AMI (Amazon Machine Image) check-box and set up the vmimport role: How To Configure VMimport Role.

Note: The Restore as Amazon EC2 Instance option does not support Desktop Windows 7/8. Whereas the Restore as Amazon EC2 Instance along with the Create AMI option does not support Windows 10.

4. Specify Target EC2 Instance details:

Complete the rest of the Restore Wizard steps to create and customize your restore plan!

5. You can find the restored server in Amazon EC2 Management Console

admin :

View Comments (24)

  • Woah, what's the cost of doing this on Amazon? It would be a great way to demonstrate to clients that their machine is being backed up successfully.

        • This question was posted 2 years ago, in the interim - has there been any changes?

          Will it ever be possible to restore a Hyper-V backup directly to EC2 or Azure? If not, is there a way to convert it?

          • Unfortunately that can be performed with VM edition.
            The only workaround in this situation is to
            - install CloudBerry Image-based backup to Hyper-V guest system,
            - perform an Image backup
            - restore this image to EC2/Azure VM

        • Sure, but you need to have CloudBerry Backup installed on the VM that you want to backup and back it up using Image based backup mode.

          • i was confused on that , i tried to backup using the Hyper-v Backup but then did not have a restore option to Amazon E2 makes sense now that i read this post, i did test backup having the software installed on a Hyper-V image and was able to restore to Amazon E2 instance, but need to open some RDP ports up in Amazon for it to work, FYI

          • By default 3389 is opened in Amazon ACLs thus you only need to open it if you've closed it earlier. By the way, during the restore process we open port 3389 on the restored instance.

  • This is great! We currently use Google as our storage provider and would prefer not to need to setup another account with Amazon to do something like this. Do you have any plans to provide similar functionality on Google's cloud platform?


  • I would love to see a tutorial video or demo video of this online, does anyone have a video example of this in use?

  • When you restore a Windows image to Amazon EC2 it does bring over the license also ?
    Thank you,

    • Hi Igor,
      I suppose this happens because you have quite slow connection to the Internet.
      First it downloads the image from S3 to local computer then it processes it locally and then pushes processed image from local computer to EC2. In other words it has to transfer an entire image through a slow connection twice.
      If you run a VM in EC2 and initiate the process from that VM it will work much-much faster.

      • Hey Anton, I know this is an old thread, but just our of curiosity (as I'm documenting this process) whey does the restore process require that I download the instance and push it back into the AMI / EBS? I understand that it's compressed but can't you execute the restore from the aws command line directly? Just wondering what's going on under the hood. We're trying to move a very large server to AWS and we only have 1 weekend to do it. It's a Gen 2 Hyper-V as well which makes it very hard to complete in that window. Any suggestions?

        • Now we have an option to run temporary EC2 instance that will allow you to save a lot of time on transfers. Just make sure to pick the right instance size for the temporary machine.
          Also there's 1TB AWS limitation on image size import (uncompressed).