Restore Image-Based Backup as EC2 Instance in Management Console

Management Console offers a cloud restore functionality that enables restoring the disk image backups to Microsoft Azure.

Note that the procedure varies depending on the type of data source (disk image backup or VM snapshot).

This chapter describes the disk image restore in Management Console as EC2 Instance including preparation and related technical details.

Before You Begin

This procedure is based on the AWS VM Import/Export ability. It requires the IAM permissions to the EC2 operations for the AWS credentials or AWS IAM role used. There is no need to allow all EC2 actions: the scope of the needed permissions can be confugured using the Policy Designer.

When adding a new S3 Account, we strongly recommend that you use an IAM role with a policy that grants minimum permissions required for proper functioning of MSP360 (CloudBerry) Backup.

The IAM role should have the following permissions to be able to successfully use EC2 services:

• ImportInstance
• ImportImage
• DescribeInstances
• MonitorInstances
• RequestSpotInstances
• RunInstances
• StartInstances
• TerminateInstances
• ModifyInstanceAttribute
• CreateTags
• CancelImportTask
• StartInstances
• DescribeConversionTasks
• DescribeImportImageTasks
• ImportVolume
• DescribeAvailabilityZones
• DescribeSecurityGroups
• DescribeSubnets
• StopInstances
• DescribeKeyPairs
• ImportSnapshot
• DescribeImportSnapshotTasks
• CreateVolume
• DescribeImages

You can use MSP360 (CloudBerry) Explorer to create an IAM role and grant it the required permissions, or manually create a new user role using AWS Management Console. See the following articles for more information:

• How to Use an External ID When Granting Access to Your AWS Resources to a Third Party
• How To Setup a VMimport Role

The special vmimport role is required to be created in the AWS account before the import started - this allows the AWS import service to have access to the customers data. This role is one for all the AWS account and regardless to the region. If it was not created, the import fails with the error. The Management Console can create vmimport role automatically if the S3 storage account is created by the option IAM role (MBS Wizard).

Without Create AMI (Amazon Machine Image) option, you will have a restored EC2 instance but there will be no image on Amazon. For the restored EC2 instance you will have to configure a public IP address (Elastic IP) manually in the AWS EC2 Management Console.

Create a Restore Plan

1. Open the Management Console.
2. On Backup select Restore to Cloud (or Computers > Restore to Cloud if you are using legacy menu).
3. Click Amazon EC2 Restore option

4. As the restore wizard opens, specify the data source parameters:

• Plan Name. The plan name is displayed on the Restore to cloud dashboard
• User. Select the user with backup data (disk image) to restore
• Destination. Select the backup destination that contains the required backup data
• Computer. Select the computer (prefix) containing the data to be restored.
• Point in Time. Select the backup version that is to be restored

5. Click Next.

6. Specify disk partitions to restore. As you are done, click Next.

   • GPT

* Convert to MBR enabled

7. Specify the target instance parameters:

* **AWS Account**. The account under which a new EC2 instance will be stored
* **AWS Region**. The region that is to store the newly created EC2 instance
* **Temp Destination**. Storage destination to store temporary disk for VM import. Use + to create new bucket, if necessary.
* **Instance Type**. The type of instance required. Learn more about EC2 instance types [here](https://aws.amazon.com/ec2/instance-types/)
* **Subnet**. Select one of the subnets available. Learn more about EC2 subnets [here](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html)
* **Security Group**. Select the default security group or the custom one you created yourself.

Click Next.

8. Specify encryption password if you have encrypted objects. Consider, there is no password validation on this step. In case of wrong password, the restore will fail.

9. Specify the temporary instance parameters:

* **AWS Account**. The account under which a new EC2 instance will be stored
* **AWS Region**. The region that is to store the newly created EC2 instance
* **Temp Destination**. Storage destination to store temporary disk for VM import. Use + to create new bucket, if necessary.
* **Instance Type**. The type of instance required. Learn more about EC2 instance types [here](https://aws.amazon.com/ec2/instance-types/)
* **Subnet**. Select one of the subnets available. Learn more about EC2 subnets [here](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html)
* **Security Group**. Select the default security group or the custom one you created yourself.
* **AMI**. AMI (Amazon Machine Image) allows you to create an Amazon machine image (based on your image backup configuration) in addition to a restored EC2 instance. The restored EC2 instance will be run automatically and it will have a public IP address. The created Amazon machine image can be used for setting up other EC2 instances in the future. You can find Amazon machine images on the IMAGES section of the AWS EC2 Management Console

10. Review all settings specified across the restore wizard and ensure that they are accurate. Click Save and Run to execute the restore to an EC2 instance.

Restore Progress

During plan execution, you can follow the progress on the Restore to cloud dashboard.

Manage EC2 Instance

You can access and manage the instance from Amazon web console.

In case you have Backup or Restore Agent on restored EC2 instance you also can use the Remote Management or Backup > Computers tab in the same way you usually manage your regular computers.