Backup Exec 2014 can not connect to secondary backup network

I have a Hyper-V HA cluster that is running about 15 server between the nodes.   I have Backup Exec 2014 Central Administration Server that runs the jobs.   I took two network cards from each node and put them into a LAG, I then added a virtual nic to each of the VM’s and gave each Vnic in each VM a 172.30.0.0 Address the production network is 192 network the backup server can ping all the back Vnic’s on each VM and I selected the 172.30.0.0 network in the global settings in the BE central administration server but when I try to run a job it fails saying it could not connect to the remote computer.  Any ideas?
cameljoe121Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rodney BarnhardtServer AdministratorCommented:
I am assuming you installed the remote agent on each system. Have you validated which network the remote agents are using that you placed the 172 network NIC's on? I would start here and see if the remote agent is configured for the backup network buy running the remote agent utility. The other thing you can try is placing an entry for the media server in the host table with only the backup network IP address for the server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cameljoe121Author Commented:
I tried to verify the agents where using the the one 172 net on each I went to to the agent and added the publishing server 172 address but I am still getting the same error.  In regards to the host file do you mean the windows hosts file under system32?
0
Rodney BarnhardtServer AdministratorCommented:
Yes. While I have not tried this on BE 2014, I have had to use them on other Symantec products such as NetBackup.
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

cameljoe121Author Commented:
Symantec has an article about this this is the info they want to be added.  Now I added the 172 address of the machines that make up my DAG no luck I get the same message.  Below is Symantec's example and an example what I added.

127.0.0.1 hostname_of_the_computer
127.0.0.1 hostname.FQDN (Fully Qualified Domain Name)
Local_IPv4_address hostname_of_the_computer
Local_IPv4_address hostname.domain.FQDN
Remote_IPv4_address hostname_of_the_remote server
Remote_IPv4_address FQDN_of_the_remote server

127.0.0.1 Node01
127.0.0.1 Node01.company.local
192.168.100.100 ex1
192.168.100.100 ex1.company.local
172.30.1.1 ex1
172.30.1.1 ex1.company.local
0
Rodney BarnhardtServer AdministratorCommented:
Have you tried breaking the LAG and testing with just a single NIC? That would eliminate or narrow down the problem and ensure there isn't something going on with the aggregation\balance.
0
cameljoe121Author Commented:
Your solution of adding the entries into the host file seems to work.  Although to get it to connect to a cluster I had to add a generic role and give the role a 172 IP address and add the entry to the host file on the BE server after that it could connect to the cluster via the 172 address.  But unfortunately it is not that easy for the exchange DAG every time you try to change the setting in the cluster network management it changes back to default 1 second later
0
Rodney BarnhardtServer AdministratorCommented:
So you do have Exchange. In the first part of your question you were talking about LAG, which the way it was worded I figured you were referring to Link Aggregates. However, in another post, you mentioned your DAG network with no mention of Exchange. Therefore, I just assumed "DAG" was a typo and you meant "LAG".

Glad you have it working.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.