Adding a new backup LAN to the existing VBR setup

[morit]

A customer is using VBR and Veeam Agent based backup for AD, File Server and SQL Servers (all Windows VMs).
The protection groups were created and registered with hostname/FQDN with Production IPs.

In later stage, the new dedicated Backup LAN is ready, and the customer is asking following question;

“Do we need to remove the respective servers from the backup infrastructure and add them back with the appropriate new Backup FQDN/IP?
If so, does this mean we need to recreate the backup jobs as well?
Is there any alternate way/option to update the existing protection groups with new backup FQDN/IP?”

They already opened a support case and Case # 04742624.
Here is the setup details.

VBR SW Version : 10.0.1.4854 P20201202
Hypervisor version : VMware ESXi 7.0.1, 16850804
vCenter version : 7.0.1
Windows OS on VMs : MS Win Server 2019 DC
Veeam Agent Version: Veeam Agent for Windows 4.0.1

They say that it’s challenging for them to change/update the FQDN of the backup IP to the ones with Prod IPs at this moment as those are already reserved for production FQDN.

[Egor Yakovlev]

Hi Mori,

Preferred Networks control should do the trick seamlessly, with no other changes.

/Thanks!

[morit]

Thank you for the input.
In fact, the customer is already using Preferred Networks setting with their new Backup LAN/IPs, but somehow only one protection group can see the new backup IP automatically.
Rest of the Protection Groups are not recognizing the new backup IPs.
The customer is collecting a log from the agent machines (as requested by Veeam support team), but not sure if there is anything missed out...