How Do I Perform a Local Disaster Test with a Local VLAN and No Internet Access



How do I perform a local disaster test with local VLAN and no internet access?


  • Datto SIRIS


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

Datto does not support requests from partners who want to intentionally power down their live environment to test the local or offsite virtualization as a production environment. Engaging in a 'fire-drill' scenario can create the potential for data loss and the possibility of crippling the live environment.


  1. Sign into the Datto's remote or local user interface (UI).
  2. Go to the Restore tab.
  3. Select a protected machine, then Local Virtualization, then a recovery point.
  4. Select resources to allocate to the VM. Make sure the RAM is a multiple of 1024 (eg 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.
  5. Change the networking set to Firewalled on a private subnet without internet access.
  6. Start the VM.
  7. Repeat the above for all VMs you wish to use.
  8. Sign into each VM as it reaches the login screen.
  9. Allow several minutes or more for the VMs to fully boot once logged in. The VMs will need to install some drivers for the new virtual hardware they are using. You may need to reboot.
  10. On the command line of the protected machine, find and document the Automatic Private IP Address (APIPA) of each VM. On windows, run the command ipconfig /all. On Linux, run ifconfig -all.
  11. From the command line of the protected machine, ping the other VMs' APIPAs from each VM to make sure connectivity is good. Do not use the APIPA of any VirtualBox Host-Only adapters, only the APIPAs assigned to the LAN interfaces.
  12. If no ping reply, make sure the firewall on the VM that is not sending a reply is set to allow ICMP responses on all kinds of networks (public, private, domain):
  13. Test any proprietary software you have.

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!