Re: [Veritas-bu] bpbackup and socket read error (23)

This sounds like a problem opening a connection from the client to the NetBackup server.

On client and master/media servers (I assume you use the default "vnetd", port 13724, method and FQDN):

Test forward and reverse DNS for servers and client. If multiple IP addresses, adjust NBU config. I tell people to use lower case DNS names, even if it should work otherwise.
Verify firewall exceptions to allow connections in AND out.

Restart the NetBackup Client Service. Because it's Windows, reboot to ensure 6.5.6 is really installed. But, again, I'm guessing a telnet to the NetBackup server(s) on port 13724 will fail until you resolve the problem.

Properly doing these things has always worked for me, but the next step for me would be to turn on NetBackup logging to see exactly where the problem is, while verifying connections/rejections are seen on each side.

Cheers, Wayne

On Tue, Oct 5, 2010 at 9:05 AM, Andy Braithwaite <netbackup-forum AT backupcentral DOT com> wrote:

Hi, I'm having some problems with a client initiated backup. I hope you can help.
I have a 6.5.6 windows 2003 x64 master server and two Red Hat linux (2.6.18-164.el5) client - there are many more clients, however these two were built at the same time and are supposed to be almost identical.

Server scheduled backups work on both clients. However on one client bpbackup fails:

[root@xxxxx bin]# ./bpbackup -w /etc/group
EXIT STATUS 23: socket read failed

Also, the clients properties in the admin console show v6.5 only. I've definately installed 6.5.6 on this client. I even reinstalled the client from scratch and still get the same result.

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