This article provides details and guidance for setting the Local Options of a Local Virtualization on a SIRIS device. You set these options when you initially start a new virtualization. You can also change these options after the VM has been created. The Local Options section allows modifications for the following:
- Number of CPU cores
- Amount of RAM
- Volume Letter to boot the Virtual Machine
- Storage Controller
- Network Options
To change the network controller, see Agent Configuration - Virtualization Options.
2. Local Options
When you start a local virtualization, you will see a screen to set the Local Options. You can also access these options after a VM is created: Go to the Recovery tab of Remote Web, and click the Manage Restore button.
Figure 1 - Local Virtualization
If the VM is running, you must click the Stop button before you can change the Local Options.
2.1. CPU Cores
Choose the number of CPU cores. It cannot exceed the number of CPU cores that you have available. See the indicator in the upper right of your screen for that amount.
2.2. System RAM
For best results, set the RAM in increments of gigabytes (1024, 2048, 3072, 4096, etc). Refer to the available RAM resources shown in the upper right of your screen, and make sure you leave at least 3072 MB free to allow the screenshot process to work for other agents on the device. Alternatively, you can disable screenshots while you are running the VM. In either case, do not set the RAM to more than is available on your SIRIS. Otherwise, the VM will not boot.
2.3. Boot Disk
The drop-down menu lists all available boot disks. Choose the one you wish to use. The default disk on Windows machines for operating systems is C.
2.4. Storage Controllers
If you change the storage controller, you should also perform an incremental backup of the machine. The reason for performing a backup is to ensure that the backup updates the boot sequence with the proper boot controller configuration.
2.5. 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.
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.