SureBackup & Multiple Networks

[remko.de.koning]

I am currently working on automated disaster recovery testing with SureBackup.
All the tests work as expected, I can check if services are running and if ports are listening.
So far so good.

The problem I am facing now is multiple networks.
We have three HyperV hosts with a single virtual network. On this virtual network all my networks are available, tagged with a VLAN

Example:
Servers: 10.0.10.0/24 (VLAN 10)
Workstations: 10.0.100.0/24 (VLAN 100)
Equipment: 10.0.40.0/24 (VLAN 40)
etc
etc
For convinience the third octet is the same as the VLAN ID.

If I do a surebackup and test the servers that are in the same VLAN as my Veeam B&R server, the tests work as expected.
However, when a machine is powered up in a different VLAN, the machine is not accessible.

I have tried two approaches.

Approach 1
Basic Single-host networking
This works perfect for my servers.
The Veeam server is on the same VLAN as my other servers.Ping tests, scripts, all work fine.
Machines on other networks are not accessible for automated tested.
I guess this is expected as this method is not suitable for multiple subnets.

Approach 2
Advanced Single-host
Occording to this article : https://helpcenter.veeam.com/backup/hyp ... .html#vlan
I should be able to map multiple VLANS
When trying to map multiple Production networks with VLAN ID's to Isolated Networks with VLAN ID's the VLAN ID's are changed.
The value was changed from 50 to 100 after adding the second line.


Anyone knows what am I doing wrong here? Why is the VLAN ID on the Isolated network changed?

[PTide]

Hi,

Do the isolated networks have different names?

Thank you

[remko.de.koning]

You got me on the right track. I figured I could have multiple VLAN's on the same isolated network but from what I understand, you need to have a virtual network for each VLAN. (is this correct?)

I have now created multiple Virtual Labs/Networks by typing a new name in the Virtual lab field and mapping it to the right production network.



Do I need to set a VLAN ID by the way on the isolated network?

Anyway, you definitly got me going forward
On my HyperV host, I see the new isolated networks but I am still strugling with the Virtual Proxy appliance. This one does not want to start at the moment and keeps starting over and over. I will troubleshoot on this some more.

[remko.de.koning]

Had a good nights rest.
Created a drawing in Visio how I want the virtual lab to be.
Created a route statement on my router to the Veeam Proxy for the Masquerade IP addresses


Read the documentation again and saw the light
The virtual lab is now up and running

Restored Virtual machines on the different networks can now see each other, can access the internet and can be reached from the production network through their masquerade IP addresses.

Happy...

[PTide]

Sorry for non-replying so long, I had to doble-check something with QA. Glad that you've resolved it, may I ask you what was wrong with the appliance?

Thanks

[remko.de.koning]

I may have cheered to early.
I began with a small setup. Two virtual networks connected to the proxy appliance.
All worked fine after which I started adding one network at a time.
This is were it fails. As soon as I add one more virtual network, the virtual appliance keeps booting over and over again.
I am thinking of opening a support ticket on this. I have been banging my head on this for a while and cannot seem to find the reason why this is happening.

[PTide]

Did you try to connect to the appliance console and check what's happening on the screen while it boots?

[remko.de.koning]

This is what I have done.



The Virtual NIC's


And the crash screen

[tdewin]

Seems like the kernel is panicking because it does not have enough mem. Could you maybe try to manually power on the VM and see if it crashes? If yes, could you shut it down and give it some more memory (the appliance) and then try to power it on again. Make sure the VM get enough memory (maybe use static memory?)

Also I suggest you open a case, because the appliance (default configuration) should be able to manage such amount of networks without any problem imho.

[remko.de.koning]

You are correct. I doubled the amount of memory and it started! 512 --> 1024

Weekend has started in this time zone so I will play around with this some more next Monday. Thanks for the tip!!!

[remko.de.koning]

Just wanted to confirm that my problem has been solved by adding additional memory to the Veeam Virtual Proxy appliance.
Thanks for your tips and advice!

[mma]

I think my question will fit in this thread...

Can I add multplie isolated networks with untagged VLANs?
Looks like you have to add the VLAN ID...

Regards
Marcel

[PTide]

Hi,

You can add as many isolated networks with the default (0) VALN ID as you want. Do you experience any issues? What's your environment: Hyper-V or VMware?

[mma]

Ok, figured out how it works.
No problem at all

Thanks