05-29-2014 03:30 AM
we have 1 master+media and 1media server, they have both prod & bak interface on them.
However clients have only prod NIC.
In order to route backups from clients prod NIC to master/media bak NIC.
what should be the server entries in NBU client configuration.
I used only master/media server names with bak interfaces as server entires and connection is failing from cient to master/media & viceversa from NBU gui under host proerpties.
If i use both prod & bak server names as server entries an coneection established, confirmed from NBU gui under host proerpties.
why i'm unble connect using bak interface as server entries.
Solved! Go to Solution.
05-30-2014 06:15 AM
Prod network still seems to be the logical choice.
Test comms at OS level from the client to servers, e.g.
ping master-prod
ping master-bak
traceroute master-prod
traceroute master-bak
(tracert on Windows clients)
ping media1-prod
ping media1-bak
traceroute media1-prod
traceroute media1-bak
Also test with traceroute from master and media server(s) to clients.
05-29-2014 03:40 AM
Sorry, but what is the point of having a backup network on your master server and not on the clients?
If you're using the bak interface on the master and media's you'll have to configure the required interface in their host properties. When you're connecting to a client from the master server GUI the request goes out via the primary interface of the master, say 192.168.1.10. When the request gets to the client its see this and resolves the name to MASTER, but MASTER is not in its server list, only MASTER-BAK is. So it doesn't allow the connection.
That why when you add all the entries it work.
05-29-2014 04:45 AM
I am with Riaan on this one.
The purpose of a backup network is to route backup traffic between client(s) and media server(s) using backup network.
Do yourself a favour an draw a network diagram of your backup environment.
Include hostnames and IP addresses for public and private/backup network.
When you look at this diagram, you will see what to put in SERVER entries. And why you cannot route client comms or data to the backup network.
Something like this:
---------------Public Network-------------------------------- | | | | | | | | master media1 client1 client2 192.168.1.1 192.168.1.2 192.168.1.3 192.168.1.4 --------- ---------- --------- ---------- | | | | | | | | | | | | | | | | | | | | | | | | --------- ---------- --------- ---------- master-bck media1-bck 10.10.1.1 10.10.1.2 | | | | -----------Backup Network-------
So, backup data and comms between servers and clients can only be on public network.
Use names on the public network.
05-30-2014 03:30 AM
Hello Marriane,
In our environment, we configured netwrok such that prod and bak vlan allow route in both direction.
Even then we are facing issue.
05-30-2014 06:15 AM
Prod network still seems to be the logical choice.
Test comms at OS level from the client to servers, e.g.
ping master-prod
ping master-bak
traceroute master-prod
traceroute master-bak
(tracert on Windows clients)
ping media1-prod
ping media1-bak
traceroute media1-prod
traceroute media1-bak
Also test with traceroute from master and media server(s) to clients.
05-30-2014 01:38 PM
Also don't forget the bptestbpcd command
bptestbpcd -client (client name or ip)
Telneting from the client to the master or media on port 1553 is make a connection if the ports are open and routeable.
Also you can use prefered network settings to limit which nics are used.
http://www.symantec.com/docs/HOWTO60779
06-04-2014 04:58 AM
Please excuse -
there was some misconfiguration in routing from network team.