I have a Microsoft server 2008 client.  SAN storage is presented to the client. 
 I added the client to our existing Windows OS backup policy which backs up 
ALL_LOCAL_DRIVES.  All other clients backup up successfully through the policy. 
 The  Microsoft server 2008 client with SAN LUN's and SQL databases gives 
errors  with a netbackup error code of 42.  Below is the information from the 
failed job. 
 
7/28/2010 7:36:07 AM - connecting
7/28/2010 7:36:08 AM - connected; connect time: 00:00:01
7/28/2010 7:36:11 AM - Warning bptm(pid=3552) could not set TCP_NODELAY on 
socket 1724, h_errno = 10038  
7/28/2010 7:36:11 AM - Warning bptm(pid=6892) could not set non-blocking on 
socket 1724, An operation was attempted on something that is not a socket.
7/28/2010 7:36:11 AM - Error bptm(pid=6892) socket operation failed - 10038 (at 
child.c.1294)     
7/28/2010 7:36:11 AM - Error bptm(pid=6892) unable to perform read from client 
socket, connection may have been broken
7/28/2010 7:36:11 AM - begin writing
7/28/2010 7:36:17 AM - end writing; write time: 00:00:06
network read failed(42)
 
 
I have a Windows 2003 Master/Media Server running NBU 6.5.4.  We are backing up 
to a Data Domain DD630 disk based storage unit.
 
If I restart this client backups go through, but after a week or so the problem 
comes back until another reboot. Is there a permanent solution to this coz we 
can't keep restarting the client. Please assist.

+----------------------------------------------------------------------
|This was sent by mulauzid AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


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