11-15-2017 07:08 AM
Nov 12, 2017 2:21:13 AM - Info bpbrm (pid=4656) connect failed STATUS (18) CONNECT_FAILED
Nov 12, 2017 2:21:13 AM - Info bpbrm (pid=4656) status: FAILED, (43) CONNECT_RESET; system: (104) Connection reset by peer; FROM 0.0.0.0 TO {client} {IP} bpcd VIA pbx
Nov 12, 2017 2:21:13 AM - Info bpbrm (pid=4656) status: FAILED, (42) CONNECT_REFUSED; system: (111) Connection refused; FROM 0.0.0.0 TO {client} {IP} bpcd VIA vnetd
Nov 12, 2017 2:21:13 AM - Info bpbrm (pid=4656) status: FAILED, (42) CONNECT_REFUSED; system: (111) Connection refused; FROM 0.0.0.0 TO s{client} {IP} bpcd
Nov 12, 2017 2:21:13 AM - Error bpbrm (pid=4656) cannot connect to {client}, Operation now in progress (115)
Nov 12, 2017 2:21:13 AM - Info bpbkar (pid=0) done. status: 58: can't connect to client
Nov 12, 2017 2:21:13 AM - end writing
can't connect to client (58)
The master is version 8.0; the client is 7.7.2.
The Netbackup Client Service is set for automatic but keeps ending. We restart the service and the backup completes. Why is the service keep stopping?
Solved! Go to Solution.
08-21-2019 10:54 AM
The solution was on our network side. They replaced the daughter cards.
11-15-2017 08:28 AM
maybe the event log might have some info?
11-15-2017 08:35 AM
Good suggestion. I'll check.
11-16-2017 12:02 AM
Also look at Security/AntiVirus software.
We have seen in the past that certain AV software stopped NBU software. Especially services that are 'listening' for external connection request.
11-16-2017 12:18 AM
Can also be caused by the firewall profile not being loaded on the client, have seen it when the network as not been identified as the domain network.
Think there was a technote about the 0.0.0.0 ip address, which might help you.
08-21-2019 10:54 AM
The solution was on our network side. They replaced the daughter cards.