I would suggest checking your client timeouts. If you're backing up
large amounts of data or there is a network issue, I have noticed it
will fail with this error. Hope this helps.

 

Glen Collins
Storage Engineering Services
Robert Half International, Inc.
________________________________


From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Jenner,
Steven
Sent: Thursday, May 10, 2007 8:41 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Status code 42 - SQL2005 backup using NetBackup
5.1MP6

 

Hi,

 

I have a strange failure that hopefully someone out there knows the
resolution to.

 

I am trying to perform 'hot' SQL backups on several new SQL
installations in my environment but some of the DB's back up ok whilst
others fail with status code 42 (network read failed). For example on
one server the backup of the master and model DBs both fail with status
code 42 whilst the msdb and a custom DBs work. However this is not
always the case as with other backups the model and msdb DB's have
failed and master and custom have worked.

 

The client machines are running NetBackup 5.1MP6, SQL2005 and Windows
2003; whilst the NetBackup servers are running on Solaris 9 with 5.1MP6.

I am able to backup other SQL2005 installations set up as above but the
SQL install on the new servers has been set up by an external resource
and I am not sure whether the issue could be something to do with the
SQL config.

Any suggestions?

Steve.

 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070510/5007dd01/attachment.html