Introduction
On previous blog “Veeam Backup & Replication: Restore Backup” there are general steps on how to restore Veeam Backup file into AWS as follows:
Introduction
On previous blog “Veeam Backup & Replication: Restore Backup” there are general steps on how to restore Veeam Backup file into AWS as follows:
1. Restore backup-file into VMDK file
2. Convert backup-file into OVF with VMware OVF Tool
3. Import VM as an Image to EC2
4. Configure Instance VPC
The complete process can be pictured like below:
This writing will describe Step-2 above.
Prerequisite
· For VM import into EC2, you need to have AWS account.
· To sign-up and configure EC2 use this guide: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/get-set-up-for-amazon-ec2.html
· Registered EC2 location configured there, must match with destination target that being used in tools of “Amazon EC2 CLI”.
· VM need to be prepared so it can be restored in EC2, use this guide: http://docs.aws.amazon.com/vm-import/latest/userguide/prepare-vm-image.html
· Configure AWS VPC so it will match your DR scenario (and your VM subnet).
Convert backup-file into OVF with VMware OVF Tool
1. Get Vmware OVF Tool.
a. Import of VMDK files into Amazon EC2 can only be done with files that were created through the OVF export process in Vmware.
b. If normal VMDK file (direct output from Veeam restore) is processed with Amazon EC2 CLI, it will stop and generate this error message “ERROR: This does not appear to be a Stream Optimized VMDK. It contains invalid magic number <several-digits-code-here>”.
2. Install OVF Tools on (for this example) Standby Notebook.
It will be located on C:\Program Files\Vmware\Vmware OVF Tool\ (for 32-bit system) or C:\Program Files (x64)\Vmware\Vmware OVF Tool\ (for 64-bit system)
a. Input: VMXF file; configuration file of the VM – supplemental, that read by OVF Tools and convert VMDK file based on that.
b. Output: OVF file (Open Virtual Machine Format); a virtual machine distribution format that supports sharing virtual machines between products and converted VMDK file.
3. Run it with the following parameter:
a. Syntex: ovftool “<drive/folder-location>\<vm-name-source>.vmxf” “<drive/folder-location>\<source-file-name>.ovf”
b. Example of running command: ovftool “C:\VM-source\windows-2k8r2.vmxf” “C:\VM-destination\AWS-WIN2k8-disk1.ovf”
4. Conversion process will generate OVF and VMDK file that can be processed on Amazon EC2 CLI