Recovery Launchpad: Cloud VLAN Overview

Follow

Topic

This article explains how offsite VLANs are created and goes over some limitations and best practices associated with them.

Environment

  • Datto ALTO
  • Datto SIRIS

Description

VLAN Creation

You can only create VLANs while setting up an offsite virtualization, as they will be created on the server for the VM. This server will then be the "Master Server" for the VLAN and will share the VLAN as needed. Only one VLAN with a given IP scheme can exist on a master server (For example, if a VLAN with the subnet 192.168.2.0/24 already exists and is in use, you will be unable to create it, and must either select a different networking scheme or reach out to Datto Technical Support for assistance).

Offsite VLANs for cloud VMs are limited to /22 or 255.255.252.0 to avoid using large sections of available addresses for a small amount of VMs. The 192.168.122.0/24 subnet cannot be used for offsite VLANs. This subnet is used for internal resources.

VLAN Cleanup

Figure 1: Destroy and unmount VLANS pop-up (click to enlarge)

Remove the old VLANs after your Disaster Recovery or DR test scenario completes. Remove the old VLANs after your Disaster Recovery or DR test scenario completes; doing so helps keep those subnets available when needed. Otherwise, unless your virtualization occurred on a private node, multiple devices from multiple partners will sync and potentially virtualize on the given offsite server. Removal of inactive VLANs ensures that commonly used subnets (such as 192.168.1.0/24 and 10.1.1.0/24) will remain available.

If you remove all VMs from a cloud network, the Recovery Launchpad will delete the VLAN after 72 hours unless you associate it to at least one virtual machine.

Was this article helpful?

0 out of 1 found this helpful

You must sign in before voting on this article.

Want to talk about it? Have a feature request?

Head on over to our Community Forum or get live help.