Veritas-bu

Re: [Veritas-bu] NBU Error- Socket Read Fail

2008-11-19 10:47:51
Subject: Re: [Veritas-bu] NBU Error- Socket Read Fail
From: <judy_hinchcliffe AT administaff DOT com>
To: <VERITAS-BU AT mailman.eng.auburn DOT edu>
Date: Wed, 19 Nov 2008 09:37:50 -0600
13's can be tricky, does the drive have a lot of files?
You might have to work on your timeout settings to give the server more
time to build the list.
Do you have more then one job running on the server at a time?
You might need to limit the number of jobs so the server does not have
to work so hard to build multi list at the same time.

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


-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of ee01akk
Sent: Wednesday, November 19, 2008 9:02 AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] NBU Error- Socket Read Fail


I have tried to backup certain drives and am getting an error : socket
read fail, connection forcibly closed by remote host. Any ideas on what
these errors mean and how I can fix them??

Thanks,

Veritas Net Backup version 5.1MP6 
Net Backup error - 18:02 to 1:10 
----------------- 
18/11/2008 18:02:30 - started process bpbrm (4896) 
18/11/2008 18:02:30 - connecting 
18/11/2008 18:02:31 - mounting E10591 
18/11/2008 18:02:31 - positioning E10591 to file 31 
18/11/2008 18:02:31 - positioned E10591; position time: 00:00:00 
18/11/2008 18:02:31 - begin writing 
18/11/2008 18:02:36 - Error bpbrm(pid=5724) socket read failed, An
existing connection was forcibly closed by the remote host.  (10054)
18/11/2008 18:02:45 - end writing; write time: 00:00:14 
file read failed(13) 
18/11/2008 18:02:45 - Error bpsched(pid=5976) suspending further backup
attempts for client slgwbp1003m, policy LGWB_E, schedule LGWB2003_Daily
because it has exceeded the configured number of tries
18/11/2008 18:02:45 - Error bpsched(pid=5976) backup of client
slgwbp1003m exited with status 13 (file read failed) 
18/11/2008 21:10:18 - Error bpsched(pid=5248) Cancel incomplete job
<55682>. Job exceeded maximum incomplete time. 
file read failed(13) 
Net Backup error - from 03:08 to 05:20 
----------------- 
9/11/2008 02:11:27 - positioned E10583; position time: 00:00:00 
19/11/2008 02:11:27 - begin writing 
19/11/2008 02:11:33 - Error bpbrm(pid=5916) socket read failed, An
existing connection was forcibly closed by the remote host.  (10054)
19/11/2008 02:11:42 - end writing; write time: 00:00:15 
file read failed(13) 
19/11/2008 02:11:43 - Error bpsched(pid=2012) suspending further backup
attempts for client slgwbp1003m, policy LGWB_E, schedule LGWB2003_Daily
because it has exceeded the configured number of tries
19/11/2008 02:11:43 - Error bpsched(pid=2012) backup of client
slgwbp1003m exited with status 13 (file read failed) 
19/11/2008 05:20:18 - Error bpsched(pid=3880) Cancel incomplete job
<55709>. Job exceeded maximum incomplete time. 
file read failed(13) 

Error on Event Viewer 
--------------------- 
18:00 The shadow copy of volume E: could not be created due to a failure
in creating the necessary on disk structures. 
18:01 The shadow copy of volume E: could not be created due to a failure
in creating the necessary on disk structures. 
18:02 The shadow copy of volume E: could not be created due to a failure
in creating the necessary on disk structures. 
18:03 The shadow copy of volume E: could not be created due to a failure
in creating the necessary on disk structures. 
18:15 The Volume Shadow Copy service entered the stopped state. 
18:18 The Microsoft Software Shadow Copy Provider service entered the
stopped state. 
19:38 The Volume Shadow Copy service was successfully sent a start
control. 
19:38 The Volume Shadow Copy service entered the running state. 
19:50 The Volume Shadow Copy service entered the stopped state. 
02:10 The Volume Shadow Copy service was successfully sent a start
control. 
02:10 The Volume Shadow Copy service entered the running state. 
02:10 The Microsoft Software Shadow Copy Provider service was
successfully sent a start control. 
02:10 The Microsoft Software Shadow Copy Provider service entered the
running state. 
02:10 The shadow copy of volume E: could not be created due to a failure
in creating the necessary on disk structures. 
02:10 The shadow copy of volume E: could not be created due to a failure
in creating the necessary on disk structures. 
02:11 The shadow copy of volume E: could not be created due to a failure
in creating the necessary on disk structures. 
02:11 The shadow copy of volume E: could not be created due to a failure
in creating the necessary on disk structures. 
02:25 The Volume Shadow Copy service entered the stopped state. 
02:28 The Microsoft Software Shadow Copy Provider service entered the
stopped state. 
06:49 The Volume Shadow Copy service was successfully sent a start
control. 
06:49 The Volume Shadow Copy service entered the running state. 
07:01 The Volume Shadow Copy service entered the stopped state. 
08:00 The Volume Shadow Copy service was successfully sent a start
control. 
08:00 The Volume Shadow Copy service entered the running state. 
08:12 The Volume Shadow Copy service entered the stopped state.

+----------------------------------------------------------------------
|This was sent by ee01akk AT hotmail 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

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

<Prev in Thread] Current Thread [Next in Thread>