05-07-2013 06:20 AM
I have been troubleshooting a connection issue to a Media Server for a day or two... The environment is:
NBU 7.1.0.3 Master Server on Win 2k3 Ent x64
NBU 7.1.0.4 Media Server on Win 2k3 Ent x64
Firewalls are disabled on both, and basic network connectivity exists(ping, nslookup, bptestbpcd(with no options), and I have checked the host files on both and the entries are corect.
I noticed that backups to the media server are rerouting through a different MS. I tried to go get to host properties on the MS and after a few seconds get:
"Ping failed on host [HN](IPx.x.x.x)"
I was able to get pretty far through troubleshooting and found no visable issues. Finally I came across a command that does not work:
bptestbpcd -client [server] -connect_options 0 1 1 -verbose
From the Media Server to the master, everything looks fine:
Solved! Go to Solution.
05-07-2013 08:38 AM
After troubleshooting with support the issue was the Timeout settings on the Master. Apparently these settings:
Client connect timeout - 300
Client read timeout - 300
Media server connect timeout - 30
Needed to be:
Client connect timeout - 1800
Client read timeout - 3600
Media server connect timeout - 150
Not quite sure why I need 30 mins and an hour... but I can't argue with what works. I will go back and tune those down a bit later but for now everything is working.
Thanks for the suggestions!
05-07-2013 06:45 AM
Do you have bpcd log on the media server?
If so, please copy to bpcd.txt and post as File attachment.
05-07-2013 07:08 AM
Here is the most recent bpcd. Sorry about the size. They have been quite large because of the redirection of jobs.
Thanks,
05-07-2013 07:37 AM
Way too big!
Could you try and change its file name and then connect to it from the Master again so that we get a short period of connection to analyse
The 0.0.0.0 is interesting - does the Media server have its loop back address in its hosts file? (127.0.0.0 against itself?)
Do you have short and FQDN names specified
Have you disabled domain, public and private firewalls?
05-07-2013 08:01 AM
Actually the log's were not even verbose 5. I will work on narrowing the logs down with more detail! :)
05-07-2013 08:38 AM
After troubleshooting with support the issue was the Timeout settings on the Master. Apparently these settings:
Client connect timeout - 300
Client read timeout - 300
Media server connect timeout - 30
Needed to be:
Client connect timeout - 1800
Client read timeout - 3600
Media server connect timeout - 150
Not quite sure why I need 30 mins and an hour... but I can't argue with what works. I will go back and tune those down a bit later but for now everything is working.
Thanks for the suggestions!