Creating A Sandboxed Local Virtualization

Follow

1. How to Start a Local VM

Take these steps to perform a sandboxed local virtualization:

1. From the local Datto SIRIS web console click the Restore tab.

Top_Tab.JPG

2. Select the machine, restore type, and snapshot of your virtual machine instance.

3. After a few seconds of processing the VM, the browser will refresh and display a Connect via RDP link.

4. Click this to download an RDP file.

5. Open the file to connect directly into the virtual machine.

1.1. Connect to VM via RDP

  • You can connect to any VM via RDP.
  • These RDP connections will work regardless of the type of network adapter configuration, including the default Disconnected network adapter.
  • The RDP link provides a connection into the SIRIS device's virtual box host service and not directly into the VM itself.
  • If the virtual machine is rebooted, the RDP connection will not be lost.

1.2. Connect to VM via VirtualBox

When you connect to a local VM via VirtualBox, the console starts up in a locked session. To create an unlocked session that you can control via VirtualBox, connect directly to the Datto device. From there, power down the VM, and start it back up.

1.3. Backing up a Virtualized Machine

  • Continue to back up the virtualized server while running a VM off of a Datto Siris device.
  • ShadowSnap will take a new base image of a local virtualization.
  • Make sure that the backups resume once the machine has been stabilized.
  • Repeat this whenever you are attempting to restore the virtual machine to either a physical or virtual environment.

1.4. Virtualization Storage Controller

  • Set the Virtualization Storage Controller type for machines protected by ShadowSnap.
  • The AHCI SATA controller type is set at default.
  • If this fails to virtualize a disk, the LSILOGIC SCSI controller will be able virtualize it.

1.5. Available Storage Controller Types

  • AHCI SATA - default controller type
  • This provides the most efficient virtual machine with highest performance.
  • The AHCI SATA is native to Windows Vista and newer operating systems.
  • LSILOGIC SCSI - For use on 2000, XP, 2003 machines where default AHCI SATA driver is not native to the OS.  
  • The LSILOGIC SCSI driver is native to Server 2003 and XP machines.
  • PIIX4 IDE - Usage is rare
  • PIIX3 IDE - Usage is rare
  • ICH6 IDE - Usage is rare

The Datto SIRIS web console provides another advanced option by choosing the Virtualization Network Controller. The VM will use as its NIC driver. This option can be selected from the Advanced Options for each protected system in the Agents tab. This feature should be changed if a VM is unable to acquire any type of network connectivity when set using any of the network configurations (excluding disconnected).

Intel PRO/1000 MT Desktop (82540EM) - default, 1000Mbps. There are 6 available network controllers available for selection:

  • Intel PRO/1000 T Server (82543GC), 1000 Mbps
  • Intel PRO/1000 MT Server (82545EM), 1000 Mbps
  • AMD PCnet-PCI II, 10Mbps
  • AMD PCnet-PCI III, 100Mbps
  • Paravirtualized network, 1000Mbps, requires special drivers
Note: The Paravirtualized network controller is reserved for rare virtual network configurations which will require Datto Support's assistance for configuration.
The AMD PCnet-PCI II network controller is available for Windows 2000 systems that are not compatible with the PCnet-PCI III driver.

Selecting a network controller should be performed depending on the operating system as these will have various drivers installed.

Operating System PRO/1000 MT PRO/1000 T Server PRO/1000 MT Server PCnet-PCI III
Windows 2000       GreenCheck.jpg
Windows Server 2003 / Windows XP   GreenCheck.jpg   GreenCheck.jpg
Windows Vista GreenCheck.jpg RedXMark.jpg    
Windows 7 / Server 2008 GreenCheck.jpg RedXMark.jpg    

Server 2012 / Windows 8

GreenCheck.jpg RedXMark.jpg GreenCheck.jpg  

2. VirtualBox Sandbox

  • If you are looking to test virtual machines in a sandbox environment, there are steps you'll need to take for the machines to have internet access.
  • You can start VMs up in a sandbox without internet access by selecting the option to be firewalled on a private subnet with no internet access.
  • This will use an internal VirtualBox network that allows communication between VMs without WAN connectivity.

No_Internet_Access.JPG

2.1. Hardware Needed

  • In order to create an isolated environment, a separate network segment is needed to allow for communication of the virtual machines.
  • An isolated subnet must be created to gain internet access.
  • The network circuit should be configured to act as a demilitarized zone (DMZ) and then connected directly to the internet for WAN access.
  • Create the default gateway on the router that is connected to the internet. Have it assigned via the router interface.
  • You will need another cable to connect a secondary NIC from the device to this switch. This acts as a secondary gateway.

2.2. Starting the VMs

1. Set the secondary NIC up on the device to act as a VirtualBox adapter. You'll want to set this as a secondary device with a second subnet.

2. Create the VM from the Restore tab as normal.

3. Set it up to be bridged to a secondary Ethernet device that will act as the gateway for the environment.

4. Once the VMs are spun up, go in and configure their IP addresses to be on a separate subnet.

5. Verify their connectivity between themselves and then check their connectivity to the internet.

IP_Gateway.JPG


Was this article helpful?

3 out of 3 found this helpful

You must sign in before voting on this article.

Want to talk about it? Head on over to our Community Forum!