This article explains how to start a Hybrid Virtualization on a SIRIS or ALTO device.
This feature is the combination of instant offsite virtualization and single click connectivity of an instant local virtualization. You can virtualize a failed system directly from the Datto cloud.
This feature also includes automatic VPN technology that can connect the virtualization from the local network to the Datto Cloud.
- Go to the web interface for the Datto device.
- Click the Restore tab.
- Select a protected system.
- Choose Virtualize (on ALTO) or Virtualize in the Cloud (on SIRIS), and select a Recovery Point to restore from (Figures 1 & Figure 2).
- Click Start Hybrid Virtualization.
Figure 1 - SIRIS Hybrid Virtualization
Figure 2 - ALTO Hybrid Virtualization
- In the Virtualization Options, select the System RAM, the Storage Controller, and Network Options (Figure 3).
- Click Build VM. For VM testing, leave the configuration at the defaults, and set Network Options to No Network Connection
Common Storage Controller Capabilities
Operating System IDE SCSI SATA Windows XP - SP3 Server/SBS 2003 Vista Windows 7 Server/SBS 2008 & r2
ShadowSnap injects SATA controller drivers into all backups. In case the virtualization does not boot with SATA, test other controllers.
No Network Connection The VM is "unplugged" from the network. Virtual Firewall + Internet The VM can reach out across the network but connection cannot be made back to the VM. Bridged to local LAN The VM will be live on the network. This setting is for Disaster Recoveries.
Figure 3 - Virtualization Options
- Click Build VM. When it's ready, it will show the VM Status (Figure 4).
Figure 4 - VM Status
- Choose the Security Options for the VM, as desired.
- Click Mount and Start VM. The VM status will update to allow access (Figure 5).
Figure 5 - Access the VM
- To view and configure the booting VM, click the URL next to RDP Link.
Procedure for Diasaster Recovery Hybrid Virtualization
- If this is a Disaster Recovery and not a test, log in to Windows.
- In Windows, set the VM to have the same IP configuration as the original production machine.
- Make sure that the VM can reach other servers on the same network that it should be on. If there is no connectivity to those servers even when setting the Bridged to LAN Connection, then contact Datto Technical Support for further assistance.
- During the DR, the Datto device should automatically start backing up the virtualization because it is on the same network as the original production machine. However, since the server has been newly virtualized, the first backup will be large because of a large amount of bit level change. This large backup will have to use the downstream bandwidth at the site to backup to the Datto appliance, so it could take some time. There might be some latency with regular use of the Hybrid Virtualized server because it is using the up and downstream bandwidth at the site as well.
- Perform a Bare Metal Restore to restore the production machine. For more information how to do a BMR, please see the following article:
Note: Any changes made to the VM will be lost from this point on
Figure 6 - Unmount the VM
Figure 7 - Delete VM and Changes
Offsite Virtualizations for Microsoft Exchange Servers
Hybrid virtualizations are bridged to the local LAN through the Datto device, and use a VPN to connect the two networks. Since the IP of the virtualized server will show as coming from the internal network, exceptions on the router/firewall must be in place to allow mail to properly relay to the next hop. This can be done by adding port forwards outbound, and allowing the appropriate relay server access to the server inbound. Once this is done, ensure the Microsoft Transport Service (MSExchangeTransport) is running, then restart the service. You can find more information on this service from this Microsoft Technet article.
After this is done, A test email should now run through the server and emails should send/receive properly. If this does not work, there may be a different underlying issue.
Cloud virtualizations not bridged to the LAN
Cloud virtualizations not bridged to the local LAN require port forwards on our server in order to allow SMTP(port 25) traffic inbound/outbound. See this article for assistance.
Once the port forwarding is set up, port 25 will be accessible via the public IP provided in the web UI, above your virtualization. The DNS records must then be updated to reflect these changes. If another server provides mail services, the changes must be made on that server.
https://technet.microsoft.com/en-us/library/ff360662(v=exchg.140).aspx (external article)
https://technet.microsoft.com/en-us/library/aa996349(v=exchg.160).aspx (external article)