We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Backup

How to Restore VMware and Hyper-V Backups to Amazon Web Services

  • Last updated on


This article refers to the Barracuda Backup firmware version 6.4.05 or newer, VMware and the vSphere Data Recovery API, supported versions of Microsoft Hyper-V, and Amazon Web Services (AWS).

This article assumes you have replicated data to AWS.


  • Virtual machines (VMs) must be fully replicated to Amazon Web Services before restore
  • Hyper-V VMs with VHDX files are not supported
  • Hyper-V generation 2 VMs are not supported
  • VMware UEFI-boot VMs are not supported

See the AWS article VM Import/Export Requirements for a complete list of VM import requirements.

Restore VMware or Hyper-V Backups to Amazon Web Services Video


Restore VMware or Hyper-V Backups to Amazon Web Services

Use the steps in this section to restore either a VMware or Hyper-V backup.

  1. Log in to the Barracuda Backup web interface, and go to the Restore > Restore Browser page.
  2. Expand the VMware data source or the  Hyper-V data source  in the left pane, and continue to navigate until you find the VM you want to restore.
  3. Click on the VM, and click View all revisions up to at the top of the page:
  4. All available revisions display. Click Restore to the right of the revision you want to restore.
  5. In the Restore dialog box, in the Restore to section, select AWS Account, and select the AWS account to restore to from the drop-down menu:
  6. Specify the AWS Region, and enter a name to identify the AMI in the AMI Name field:
  7. Click Start Restore. Go to the Reports > Restore page to monitor the progress of the restore:

    During the restore process, Barracuda Backup creates a temporary S3 bucket in the specified account where the virtual machine image(s) will be reconstructed. After the image(s) are reconstructed, they are imported into EC2 as AMIs and the temporary S3 bucket is deleted.

  8. Once the AMI is created, it is accessible from within AWS and can be launched as an EC2 instance:

Last updated on