Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Status 13 - A read of a file or socket failed.

Updated: 21 May 2010 | 2 comments
Jay Son's picture
0 0 Votes
Login to vote

Environment: NBU 6.5.3
Master Server : UNIX Solaris 10
Media Servers: UNIX Solaris 10
Clients: Unix Solaris 10

I have several UNIX clients backing up to disk. The Full backups fail (both "attempts") over the weekend with a status 13. The "retries" (set to 4 hours later) seem to  work just fine. I've moved the schedule to when the "retries" occur to see if this will resolve the caching issue. It did not. I've asked our Physcial Network Infrastructure group to monitor the Activity during these times and cannot seem to pinpoint the issue. I've asked our UNIX Admins to run SAR over the weekend and processes seem normal. I've called Symantec Tech Support and they seem to have minimal knowledge of all the logs i've given them (from master to client logs). If I bakcup to tape, I am certain that it WILL work. But, it defeats the purpose for DR.  What am I missing here? Has anyone else gone through this and found a permanent solution?

Thank you
Jay Son

Comments

Deepak W's picture
06
Aug
2009
0 Votes 0
Login to vote

I have not faced this issue

I have not faced this issue but below mentioned are some links that might help you in resolving the same...

http://seer.entsupport.symantec.com/docs/278563.htm

http://seer.entsupport.symantec.com/docs/275189.htm

hope this helps you...

-- Deepak W (Kindly close the thread if your query is resolved)

Jay Son's picture
07
Aug
2009
0 Votes 0
Login to vote

Unfortunately, I've went

Unfortunately, I've went through this troubleshooting process and none seem to work. I will try setting my client read timeouts to 1200 and see if that makse a difference.