The MBS web console enables you to restore image-based backups as EC2 instances without having to resort to the desktop client to accomplish that task. Surely, you have to first meet a few requirements to be able to perform the restore. Namely:
- You have to be logged in as a provider, as administrators are unable to do so.
- The user for whom you’re trying to perform a restore should be granted a certain type of license to perform image-based backups on their computer via the MBS desktop agent. To wit, Desktop/Server, Virtual Machine Socket, and Dedup server license types are unsuitable for this purpose. Any other license type will work just fine.
- Ensure that the available for download build’s version number is no less than 5.2 (better just request the latest build).
- Your Amazon AWS account must have the requisite permissions to operate with EC2. Elsewise, you will not even be able to fill out the forms when setting up a restore plan. Thankfully, we have a policy designer that will help you create these permissions.
- While not a requirement, we advise you to store your backup on Amazon S3 to achieve rapid file transfer and greater performance.
Now that your account satisfies all the aforementioned criteria, let’s go ahead and set up a restore plan. Under RMM, click Restore to Cloud.
Now click Add EC2 Restore.
Now select the user and the cloud storage that contains the backup.
In a moment the list of your computers will appear. Click on the little + icon to the left of the computer’s name to expand the list of available image-based backups. Select the backup you need and then proceed to Encryption Options.
If the backup is encrypted, go ahead and select the Decrypt encrypted files with the following password checkbox. Enter and confirm the password.
Next up is Target Instance details. We strongly suggest you first familiarize yourself with Amazon’s Documentation on the matter before you engage with EC2.
If necessary, select the Create AMI checkbox. Do read the Amazon’s article that explains the topic at length.
Select the requisite AWS account for your target instance and specify the instance details:
- instance type — we don't generally recommend using instances that have more computing power than m4.large, unless circumstances require anything in excess of that.
- security group (if you select the default security group — all incoming traffic to the machine will be forbidden).
Last, but not least, is temporary instance details. They usually shouldn’t differ from the target instance details, unless it is explicitly required by circumstances. Once done, click Save to save the plan or Save & Run to, you guessed it, save and run the plan.
The restore should commence, and you can then observe the status of the plan.
When the plan completes executing, expect the instance to be available on Amazon EC2’s web console.