Sachin,

Interesting that the bpcd test fails, I assume sometimes and sometimes not.

Do you have a firewall between the master and client server?
Are there multiple paths between the master and client?
When netbackup fails the bpcd test can you make any other connections between 
the two servers (ftp, sftp, telnet etc)?
Are there any hung netbackup processes on the client?
Have you turned on the debug logs on the client and master? Verbose=5?
If so do you see anything interesting in the logs.
Are the errors on full backups only or incremental backups only or both.

len

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of SACHIN ARORA
Sent: Monday, February 08, 2010 11:17 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Fwd: error 21

Another server with exactly same story , but bptestbpcd show :

<16>bptestbpcd main: Function ConnectToBPCD(Server B) failed: 23
socket read failed
I cant understand why are thse failing :(

Thanks
Sachin
---------- Forwarded message ----------
From: SACHIN ARORA <sachin...@gmail.com<mailto:sachin...@gmail.com>>
Date: Tue, Feb 9, 2010 at 9:40 AM
Subject: error 21
To: VERITAS-BU@mailman.eng.auburn.edu<mailto:VERITAS-BU@mailman.eng.auburn.edu>

Hi All,

I have an issue here.

Master : Netbackup 6.5.4 , Solaris10
CLient : netbackup :6.5.4 , Solaris10

Backup works fine for some days and then it starts failing with error 21.

-------> Host entry are ok
-------> Server is pingable
-------> Telnet to bpcd hungs up
-------> bpgetconfig provides the output :
Solaris, Solaris10
6.5.4
NetBackup
6.5
650000
/usr/openv/netbackup/bin
SunOS 5.10
--------> bpclntcmd works fine.
--------> bptestpcd shows following result :

<16>bptestbpcd main: Function ConectToBPCD(server A) failed: 21
socket open failed
Can somebody suggest what's happening here?

Thnks
Sachin


_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to