UNSOLVED

sukhigrwl

updated

8 years ago

S

sukhigrwl

4 Posts

0

6294

April 26th, 2018 14:00

dedicated backup vlan

Hello All,

a little background on the situation right now we using the same VLAN for backup as production. All the storage nodes, DD,  networker server all located on production VLAN. all the client added in Networker using Production DNS name.

Now I try to change this setup by putting second NIC  (for dedicated backup) in Networker server, storage node and one client ( which I am using for test). dedicated backup VLAN does not have any DNS server on so I am putting all entries manually on all nodes in the host files.   ping worked all way

but some reason backup still flowing through the production NIC.

so just wondering if someone points me in the right direction to solve this problem...

some points on new setup:-

Networker Server based on Linux and networker version is 9.1.1.3

Storage node and client are both window based client and have the same version as the networker.

already updated the aliases (Globals (1 of 2)) for networker server and a storage node in networker.

the client I added into networker using clients production DNS name.

client have DNS name for networker server in Server network interface ((Globals (1 of 2)) (from dedicated VLAN)

devices(data domain) are still in a production network. 

Dedicated VLAN have no communication with production VLAN.

hosts files are updated on all three nodes with backup VLAN IP address and hostnames.

server files also updated on the client

Thanks in advance,

Sukhdeep