Hi AnaB,

can you please provide more details about your problem? What is not working properly? We have a similar configuration, which is working.

One thing we had to change was to change the VBA/EBR interface type (https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA17000000010A1). Afterwards everything was OK.

Regards

Michael

Hi Kleinenbroich

Thank you very much for you answer

I think I made a mistake configuring the DNS server for the private/backup network.

I have a question

If the domain in the production network is called domain1.local, for the private domain do you need a different domain name, for example domain2.backup, don´t you?

Now I can´t decommission the VBA/EBR appliance, because I do not have this option in the Networker  version I have installed.

If I correct the DNS configuration, do you think I need to redeploy the VBA/EBR appliance again or I can correct the DNS configuration with yast2 and it will work ?

Thanks in advance

Hi AnaB,

regarding different domain names: I'm not 100% sure whether you need two different domains, but it would make live easier for you as you can use a unique FQDN for each IP (production and backup network) for the configuration.

Regarding decommission: You can redeploy the EBR from the EBR GUI and for the NetWorker (NW) server this should be sufficient. For the vCenter server there is a way how to undeploy the VBA (from vCenter point of view the EBR is called VBA).

There is one thing which is confusing me: The EBR/VBA dual NIC support was added with NW 8.2 SP1 (from the release notes: "Dual network support for proxy backup with NetWorker VMware Protection The NetWorker VMware Protection solution for NetWorker 8.2 SP1 supports dual network configuration so that you can use separate networks for VM backups (for example, proxies deployed to backup VMware environments) and traditional backup data traffic. You can configure dual NIC when you deploy the VMware Backup appliance and the proxy appliance."). With NW 8.2. SP1 you can also decommission the EBR from NW. Are you sure that you're using a NW/EBR environment which is compatible to your architecture? Are you using NW 8.2.1 (aka NW 8.2 SP1)?

Regards

Michael

Yes 8.2.1 sp1, but there is not option to decommission the VBA.

I have seen this option in releases before

Are you using one DNS server for each network following the guide

instructiond?

The missing decommission is quite strange. I've decommissioned an EBR in NW 8.2.1.0. Now we have NW 8.2.1.6 and the feature (which is mentioned in the documentation) is not available any more in the environmant. Screen-shots from the docu57703_NetWorker-8.2-SP1-VMware-Integration-Guide.pdf:

However, we are using one DNS server resolving different domains per LAN (like VLAN1.a.b.c and VLAN2.a.b.c).

You can redeploy / reintegrate the EBR into NW using the EBR GUI:

When you click on "Click to modify vCenter configuration" the EBR is also updated in NW and vCenter.

Regards

Michael

Here the scree shot which was missing in my last reply:

You can no longer perform a decomission of an EBR/VBA from the NMC Gui. You have to either contact EMC support or follow this article on the subject:

https://community.emc.com/blogs/moinmansuri/2016/06/30/how-to-delete-vba-node-in-networker

Cheers,

Erik

You cannot decomission EBR without EMC support, but if the VBA is newly deployed, no risk are if you follow the instructions in the link published by Erik Jansson.

On the other hand, what is exactly the problem with your VBA?, backup interface I suppose is the interface you are using to send data to Data Domain, so, you don't need DNS resolution for the backup-IP of your VBA, you do need DNS resolution for your Data Domain (backup interface).

Resume:

DNS for:

- NW server, Vcenter, VBA, ESX (production interfaces)

- Data Domain (backup Interface)

Not DNS for:

- VBA (backup interface)