some customers of ours are currently segmenting their server networks much more intensive than in the past.
We see compliance and security requirements due to the NIS2 framework in the EU as the cause for this.
In the same spirit these customers want to embrace sure backup jobs much more than in the past (finally!)
to get restore compliance as far as it can get.
currently the number of isolated networks in a vLAB is limited to 9 networks. We see up to 30 networks
in customer installations and since the customers will want to use linked backup job validation they
would have to reorganize the backup jobs (grouping the VMs) toward the limitation of 9 networks
each vLAB. This is not a good solution since they have migrated the backup configuration towards TAGs
just 2 years ago.
the recommendation of just making more vlabs will just not work because the backup jobs will
contain always more than 9 networks for the VMs backed up.
we have submitted a feature extension request already: with case 07201190
i am preaching for years the customer should do more sure backup jobs and finally this is getting
tracktion - just to hit the limitation
From my point of view the limitation has no real reason to be there - except for the ease of the network
overview in the vlab configuration and maybe the amount of networks on the vswitch....
ressource wise this shouldn't be a problem for the vlab VM ....
I'd love to get the view on this by the forum and maybe some Veeam guys?
[side remark: since with a lot of isolated networks comes some work which went into the vlab configuration,
maybe we could get a 'duplicate vlab' feature to push it to other hosts?]