This article describes the process of connecting a SIRIS to an ESXi host and running a virtualization via hypervisor offload. These instructions apply to virtual and physical SIRIS appliances.
For Hyper-V instructions, see SIRIS, ALTO, and NAS: Virtualize via Hypervisor for Hyper-V environments.
- Datto SIRIS
First, set up the Hypervisor Connection.
1. Start the ESXi virtualization via the device GUI by selecting the Virtualize via Hypervisor option on the Restore page.
2. Choose a recovery point and the appropriate hypervisor from the drop-down menus, then click START RESTORE.
3. The ESX Virtualization page will open and display the following options:
- CPU Cores
- System RAM
- Network Options
- Create Rescue Agent
For detailed information on each of these options, see our Local virtualization options article.
If you are virtualizing from an agentless system, you can choose to use the original virtual machine configuration. You can also download the VMX file if you wish to review the original configuration settings.
4. Once you have made your selections, click START VM.
The virtualization process
After you start the virtual machine from the device GUI, you can see the tasks in vSphere under Recent Tasks.
1. The SIRIS creates iSCSI targets to the .datto file. The targets then connect to the host via the ESXi iSCSI adapter.
2. vSphere rescans the HBA to get information on the new devices available through the iSCSI adapter.
3. A virtual disk is created through RDM to the .datto file through the iSCSI target on the SIRIS. This procedure attaches the .datto file to the virtual machine created on the ESXi host. If there is more than one disk in the backup, RDM creates a virtual disk for each.
The RDM creation can sometimes fail. This failure will typically produce the status "A specified parameter is not correct. spec.device" under the Create virtual disk task. It will retry up to 3 times for each virtual disk attached to the virtual machine.
If vSphere cannot access backup images on the SIRIS through iSCSI for ESXi virtualization, then it will attempt access through NFS as a failover.
4. vSphere registers the virtual machine with the <agent>-restore naming convention.
5. vSphere powers on the virtual machine
The screenshot verification process works the same way except for step 1, which involves manually starting up the virtual machine from the web interface. The naming convention for the virtual machine may also be slightly different.