09-03-2013 02:05 PM
Solved! Go to Solution.
09-03-2013 05:55 PM
... status: FAILED, (44) CONNECT_TIMEOUT; system: (10036) A blocking operation is currently executing....
I have already created bpcd log in the client. But nothing is creating in log folder.
Is there a firewall between the server and client?
NBU 7.5 server will try to connect using port 1556. Client then needs to connect back on port 1556.
Check if Windows firewall is running on the client. Disable it.
09-03-2013 03:32 PM
58's normally happen when the client is not able to resolve the master server or media server ip to name correctly. This can happen when there isn't the required entries in the server list (for master and media), or when the communication is coming in to a client on a different IP than expected.
A good way to troubleshoot this is to look at the bpcd log on the client (\netbackup\logs\bpcd - create this directory if it doesn't exist already) and look at the ip address that is coming in.
Look at how that IP address resolves (taking note of long vs short name discrepencies) using bpclntcmd (http://www.symantec.com/docs/TECH50198)
Check this against the clients server list. You made need to fix resolution, either through DNS or the host file. Once you've done that, clear the 'hosts cache' using the command bpclntcmd -clear_host_cache and you should be good to go.
Good luck!
09-03-2013 03:43 PM
Hi Voller,
Thanks for your reply.. I have already created bpcd log in the client. But nothing is creating in log folder.
Kindly help..
09-03-2013 05:55 PM
... status: FAILED, (44) CONNECT_TIMEOUT; system: (10036) A blocking operation is currently executing....
I have already created bpcd log in the client. But nothing is creating in log folder.
Is there a firewall between the server and client?
NBU 7.5 server will try to connect using port 1556. Client then needs to connect back on port 1556.
Check if Windows firewall is running on the client. Disable it.
09-03-2013 06:19 PM
Thanks for your reply.. Yes the windows firewall is in ON. Now i turned off it and checked backup. Now backup is completing without any issues..