can't connect to client

[oracle999]

log file entry:

bash-3.2# more  8993.0.1419732293
Backup started Sun Dec 28 02:18:49 2014

02:21:57 Initiating backup
02:24:23 INF - Waiting in NetBackup scheduler work queue on server bucyclone
02:26:57 INF - Waiting in NetBackup scheduler work queue on server bucyclone
02:30:17 INF - Waiting in NetBackup scheduler work queue on server bucyclone
02:32:14 INF - Waiting in NetBackup scheduler work queue on server bucyclone
02:35:07 INF - Starting bpbrm
02:35:23 INF - Server status = 58
02:35:35 INF - Backup by oracle on client bugrs using policy bucyclone_ORACLE_gr
strain, sched Weekly_Full_Archive:can't connect to client
bash-3.2#

any help appreciated (i am new to netbackup)

Paul

[inn_kam]

add host file name 

check firewall

[inn_kam]

Oracle RMAN backups failing with error Server Status: Cannot connect on Socket

Article:TECH147617

|

Created: 2011-01-06

|

Updated: 2013-10-26

|

Article URL http://www.symantec.com/docs/TECH147617

[inn_kam]

Oracle backup fails with status 58

Article:TECH183639

|

Created: 2012-03-13

|

Updated: 2013-10-25

|

Article URL http://www.symantec.com/docs/TECH183639

STATUS CODE 58: Can't connect to client. Troubleshooting procedures for Status 58 errors.

Article:TECH68832

|

Created: 2009-01-17

|

Updated: 2014-09-03

|

Article URL http://www.symantec.com/docs/TECH68832

[Marianne · Accepted solution]

In addition to above TNs, you can follow the same troubleshooting steps that I have posted over here:

https://www-secure.symantec.com/connect/forums/cant-connect-socket#comment-10778961 

If you have separate media server(s), repeat all steps in above post between media server(s) and client.

[oracle999]

I now believe the issue to be an oracle one; can't connect to the RMAN catalog to do the backup

and unable to TNSPING either. Thanks for your help.

[inn_kam]

mark the solution which helps you thanks

[Marianne]

The error in your opening post is NBU comms error.

PLEASE follow steps to test hostname lookup as well as port connectivity.

OS firewall will also prevent TNS comms.

[oracle999]

ok, thanks

[suhas_kakade]

Hi, this error is due to the hostname and IP address resolution.

Make the entries of Hostname and IP address of master, media and client in /etc/hosts and /usr/openv/netbackup/bin files.

Run the following commands

1)bptestbpcd -client <clientname>-----to test connection to client

2)bptestbpcd  -client <clientname> -debug-----to test through the connection process.

bptestbpcd command tries to establish a connection from NB server to bpcd daemon.

[oracle999]

this is cuurently being investigated by oracle networking ... thanks

[Marianne]

 See https://www-secure.symantec.com/connect/forums/cant-connect-socket#comment-10857781 

this issue was reolved by a restart of the solaris zone