This article describes the Local Virtualization options available on SIRIS appliances. For Alto devices, see Restore: Starting a Cloud (Hybrid) Virtualization on a Datto Appliance.
The Local Virtualization options page becomes available after you start a Local Virtualization. You can return to the page at any time by clicking the Recovery tab in the GUI, and then clicking the Manage Restore button. From this location, you can customize the following virtualization settings:
- Number of CPU cores
- Amount of RAM
- Storage Controller
- Network Options
- Video Controller Options
- Create Rescue Agent
To change the network controller, see Agent Configuration - Virtualization Options.
If the VM is running, you must click the Stop button before you can change the Local Options.
1. CPU Cores
Select the number of CPU cores. This number cannot exceed the number of CPU cores that the Datto appliance has available to it. The Available Resources pane displays the number of physical CPU cores available to your appliance.
2. System RAM
For best results, set the RAM in increments of gigabytes (1024, 2048, 3072, 4096, etc). Do not set a RAM value that is equal to or greater than the amount of RAM shown in the Available Resources pane. Leave at at least 3072 MB free to allow the screenshot process to work for other agents on the device.
If you cannot leave 3072 MB or greater free, you can disable screenshots while you are running the VM.
3. Controllers (Storage)
Choose from IDE, SATA, SCSI, or VirtIO. The storage controller value should match the configuration used on the production machine.
4. Network Options
By default, the VMs have Disconnected as the network setting to avoid accidental network conflicts with the production instance of the machine on the local network. However, if the production machine is down and you want the VM to take its place, you have the following network options:
- Bridged to the Primary NIC
When using this option, do not give it the same IP address as the SIRIS, as it will cause a network conflict.
- Bridged to eth1
Uses the secondary NIC on the Datto appliance to create a network connection. When using this option, do not give it the same IP address as the primary NIC on the SIRIS, as it will cause a network conflict. With bridged networking, the SIRIS uses a device driver that filters data from its physical network adapter. This device driver effectively creates a new software network interface that makes the VM appear as if it is physically connected to the interface via a network cable.
- Firewalled on a private subnet
This option configures the Virtual Machine for NAT (Network Address Translation) mode which creates an isolated virtual network with internet access for the VM on the SIRIS. This will allow the VM to have outbound access without conflicting with the production systems. The IP address will be 10.0.2.15.
- Firewalled on a private subnet, with no internet access
This option configures the Virtual Machine for NAT (Network Address Translation) mode which creates an isolated virtual network without internet access for the VM on the Datto SIRIS. The VM will boot up with a 169 address by default as it will not be able to reach any DHCP server. Statically assign an IP address and subnet to configure two or more VMs hosted on the SIRIS to communicate with each other.
5. Video Controller Options
The Video Controller Options menu allows you to choose between VGA and Cirrus controllers. By default, VGA is selected. The Cirrus option is primarily intended for compatibility with legacy systems.
6. Create Rescue Agent
Selecting this option allows you to create a virtual Rescue Agent from the selected snapshot of a Source Agent, and take crash-consistent backups of your disaster recovery VM. This feature creates a new backup agent on the Protect tab of the Datto appliance's GUI, and writes all of the Source Agent's configurations and data changes to automatic incremental snapshots. See the Restore: Create Rescue Agent article for additional information.
After you configure the VM's networking options, and start it, you will need to use the Connect via RDP button to connect to the running virtualization, and configure it with a static IP within Windows.