[Feature Req] Dedicated management & data transport networks

[ian0x0r]

Hi there,

As the subject, can I submit a feature request to have the option to chose dedicated management network for VBR as well as dedicated data networks. This is on the back of case 02008794 which has the details for why and also this forum post veeam-backup-replication-f2/slow-job-in ... 39741.html

In a nutshell, if choosing a preferred network in Veeam, it would seem that it tries to use this network for management and data transfer. The issue is if the data network connected to Veeam proxies is not routable to the Veeam management server, job initialisation takes a long time to start as the proxy servers try to communicate with the management server over the preferred network before failing over to other available subnets connected to the proxy servers. Windows network binding order does not resolve this issue and is not an available option in server 2016.

Thanks,

Ian

[jpiscaer]

+1
We have a use case around multi-tenant environments, where we need to backup VM's that are hosted on specific nodes (which are sometimes required to be in their own subnet). This results in some networks that are isolated per tenant, but that we want to include in the centralized backup infra.

[gsroute]

+1

We run a central Veeam management server that runs the jobs for multiple and non connected Hyper-V and VMware environments. We have a management network over a few subnets and a dedicated Backup network running across multiple datacentres. This was working well until v9.5 was installed. If we could set the management networks in the same way as Data Mover networks then this would solve a big problem just now.

Thanks.
Graeme