Performing a Local Disaster Test with a Local VLAN and No Internet Access

Follow

Topic 

This article provides the steps to perform a local disaster recovery test (DR test) which allows the virtual machines (VMs) involved to interact with each other when they don't have internet access.

Environment

  • Datto SIRIS

Description

NOTE: Datto does not support partner requests to power down their live environment to test virtualization as a production environment. Engaging in a 'fire-drill' scenario can cause data loss and the possibility of crippling the live environment.

Procedure

Building the Virtualization

Repeat this procedure for each VM you wish to create.

1. Sign into the Datto device GUI and click the Restore tab.

Figure 1: The Datto Device UI (click to enlarge)

2. Select a protected machine, then Local Virtualization, then a recovery point.

Figure 2: The Restore screen (click to enlarge)

3. Select resources to allocate to the VM.

  • Make sure the RAM is a multiple of 1024 (e.g. 1G is entered as 1024, 4G is 4096, etc).
  • Leave at least 1 core and 1G of free RAM unallocated for the Datto to operate.
  • Leave as much free resources as possible.

Figure 3: Local virtualization resource allocation (click to enlarge)

4. Change Network Options to Firewalled on a private subnet without internet access.

Figure 4: Select network options (click to enlarge)

5. Click Start VM to start the virtualization. A Screenshot of the VM will appear. Click Open in browser to go to the login screen. 

Figure 5: The running virtualization (click to enlarge)

Running the test

1. Sign into each VM as it reaches the login screen. Allow several minutes or more for the VM to fully boot once logged in. The VM will install new virtual hardware drivers; you may need to reboot it as part of the install process.

Figure 6: The virtualization login screen (click to enlarge)

2. On the protected machine's command line, Find the automatic private IP address (APIPA) of each VM using the following command:

  • Windows: ipconfig /all
  • Linux: ifconfig -all

Make a note of each automatic private IP address.

3. From the command line of the protected machine, ping the IP address assigned to each VM's LAN interface to verify connectivity. If the machine does not get ping replies, make sure the firewall on the VM failing to reply is set to allow ICMP responses on all kinds of networks (public, private, domain): http://www.howtogeek.com/77132/how-to-enable-ping-echo-replies-in-windows-8/ (external link).

5. Test any proprietary software you are using.


Was this article helpful?

1 out of 1 found this helpful

You must sign in before voting on this article.

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