This article discusses the Export Image option via the Restore tab on the SIRIS web interface.
2. Export Image
The export image restore option is the preferred method for restoring systems in a virtual environment. We provide a few different formats and methods for image exports.
First, you will select the destination for the export:
Network Share: Allows for an image to be exported via CIFS/Samba or NFS. All image files are always thin provisioned on the Datto. However, if the tool used to copy the image files to local storage does not accommodate thin provisioning, they will be copied as thick provisioned. Therefore, make the appropriate storage considerations when copying files to a virtual host or other destination.
USB (SIRIS only): Allows for an image to be exported to an attached USB drive. These are thick provisioned, or can be expanded to the maximum size of the attached disk.
From here, you can select your format. The Time Requirements listed below represent the amount of time your Datto appliance will need to create the export, not the amount of time it will take to transfer the export to your hypervisor.
VMDK-linked: Raw disk image with VMDK pointer file.
Files produced: A single-drive system results in 4 files; boot.datto, boot.vmdk, C.datto and C.vmdk. When restoring a virtual machine, you must attach boot.vmdk as the first drive in the boot order, and C.vmdk as the second drive.
Time Requirement: Instantaneous
There are two reasons to add a boot and a C volume:
Devices do not support UEFI, so if the os volume is GPT, this is necessary.
It fixes virtualization failures for some MBR/BIOS agents. if the NTFS bootstrap code (used for booting) for the C:\ filesystem is corrupted, The production agents do not notice because windows uses a 'system reserved' partition for booting by default.
VMDK: Compacted complete VMDK image (supports resizing and other advanced VMFS features).
Files produced: A single drive system results in 2 files; boot.vmdk and C.vmdk. When restoring a virtual machine, you must attach boot.vmdk as the first drive in the boot order, and C.vmdk as the second drive.
Time Requirement: Up to 15 minutes for 256 GB.
VHD: Converted raw to VHD.
Files produced: A single drive system results in 2 files; boot.vhd and C.vhd
Time Requirement: Instantaneous
VHDx: Compacted complete VHDx image
Files produced: A single drive system results in 2 files; boot.vhdx and C.vhdx
Time Requirement: Up to 7 minutes for 256 GB.
For volumes larger than 2TB, it is required to do a VHDx image export, as VHD virtual disk files do not support volumes larger than 2TB. Please note, regardless of whether VHD or VHDx is selected, image exports currently only support MBR boot, and cannot be used to create a second generation Hyper-V VM. All image exports destined for Hyper-V need to be setup as first generation VMs.
If none of the protected host's volumes exceed 2TB, you can use either VHD or VHDx. Please note that VHD is a quick export process and takes up very little array space. A VHDx export is a full image conversion and will take longer to complete, as well as require the full size of the selected backup to be free on the SIRIS array. This array space will be tied up until the image export is destroyed after the recovery is complete.
3. Export via Network Share
After selecting these options, the Windows Share page should look similar to this:
4. Export via USB Drive
If selected to export to USB drive, select your choice of format and follow the onscreen instructions.
5. Restore using your Export
If using VHD / VHDx export, then there are two paths to restoration, depending on the target.
- VHD Export: Hyper-V For Windows Server 2008 / 2012 & Citrix XenServer
- This also covers Hyper-V using an older method.
- Restore Using A VHD Export
- This process requires Hyper-V Manager.