Configure Networking Type of Virtual Machine on Datto SIRIS. It’s easy

Configure-Networking

All you need to know about Configure Networking Type of Virtual Machine on Datto SIRIS

Just read this article and learn everything you need to know about Configure Networking Type of Virtual Machine on Datto SIRIS.

The Configure Networking button provides the ability to configure the type of networking for the Virtual Machine to use.

Tip: During a true DR scenario, when Virtualizing locally on the Datto SIRIS, it is important to select the network adapter type to be Bridged to the Primary NIC or Bridged to eth1 so that the VM can have it’s IP address set to the same IP address it previously was set to.  This ensures that the ShadowSnap Agent can resume backing up the system which will be useful when the time comes to perform a Bare Metal Restore (BMR).

Note: By default, the VMs are configured to boot as Disconnected to avoid accidental network conflicts with the production instance of the machine on the local network.

Each of the network adapters that a VM can be configured to use provides different networking modes for the VM.Available Network Adapter Choices

Disconnected

By default, a configured virtual machine is configured for the network adapters to be disconnected.
This allows for the Virtual Machines to boot without causing any conflicts with the production instance of the machine on the local network.

Tip: To virtualize a machine with network connectivity, select the Configure Networking button which will display options for configuring the Virtual Machine’s networking adapter.

Bridged to the Primary NIC

Bridging the Virtual Machine to eth0 (Primary) NIC of the Datto SIRIS provides the Virtual Machine with live connectivity using the primary NIC of the Datto SIRIS.

Tip: When bridging a VM’s network adapter to the primary NIC, do not give it the same IP address as the Datto SIRIS as this will result in an IP Conflict.

With bridged networking a device driver is used on the Datto SIRIS 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.

This allows for setting up routing or bridging between the VM and the rest of the network.

Bridged to eth1

Bridging the Virtual Machine to eth1 (Secondary) NIC of the Datto SIRIS provides the Virtual Machine with live connectivity using the secondary NIC of the Datto SIRIS.

With bridged networking a device driver is used on the Datto SIRIS 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.

This allows for setting up routing or bridging between the VM and the rest of the network.

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 Datto SIRIS.

Note: VMs that have Network Adapters set to be firewalled on a private subnet will have the IP Address 10.0.2.15.

Tip: This will allow the VM to have outbound access without conflicting with the production systems.

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.
Tip: 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 & subnet to configure two or more VMs hosted on the Datto SIRIS to communicate with each other.


We hope this post provided a better understanding of Configure Networking Type of Virtual Machine on Datto SIRIS. For further assistance please contact
Invenio IT Support.

Get More out of your Datto SIRIS with these expert best practices.
Invenio it logo

Join 23,000+ readers in the Data Protection Forum

Related Articles