SureBackup with separated VLAN ?

[Soolfly]

Hello @all,

In advance, sorry for my Google Trad english...

I'm looking for a way to implement restoration lab without my VEEAM server may need to be linked to the same VLAN as the production network. Is it possible with VEEAM Backup & Replication v7 ?

Currently, the network server is configured my VEEAM so that each VLAN is tagged on the ethernet interface.
I set this up with a tool that call Broadcom Advanced Control Suite 3 (BACS) for Windows Server 2008 R2.

The IP address of my VEEAM server is 10.66.34.16.
Examples of VLAN tagged on my server:

10.66.34.16
10.66.186.14
10.66.139.13
Etc ...

Managed servers in the part -> VMWare vSphere -> vCenter servers, I have several Vcenter, one with the IP 10.66.34.60.

I have several SureBackup already in place and functional, you set up one of these SureBackup:
8 <------------------------------------------------ ----------------------------------------------
Configuration vLab
• Lab name: Virtual Lab VLAN38
• ESX name: esx-bar-02
• Datastore: Local: esx-bar-02

Appliance
• Name: Virtual_Lab_VLAN38
• Pool name: Virtual Lab VLAN38
• Folder name: Virtual Lab VLAN38

Production network name: VLAN_38
• IP: 10.66.34.35
• Subnet mask: 255.255.255.0
• Default gateway: 10.66.34.1

DNS
• Preferred: 10.64.1.1
• Alternate: 10.64.1.2

Network standard configuration
• advanced single-host

Network options
• Isolated network: Virtual Lab VLAN38_isolated
• IP Masquerade: 10.255.34.0
• Appliance IP: 10.66.34.1
• DHCP: disabled

Virtual NIC
• IP adress: 10.66.34.1
• Mak: 255.255.255.0
• Masquerade: 10.255.34.X

Network mapping
• VLAN_38 -> Virtual Lab VLAN38_isolated
8 <------------------------------------------------ ----------------------------------------------

This way of working generates too much traffic on our network and our switches. So, o you know one (or more?) solution would be to make routing or ports forwarding between my VEEAM server and different VLANs?

Regards.