I did some further digging in client logs, once I enabled them and
re-ran, and found that it was caused by MS VSP being disabled.
Resetting to manual fixed the issue.
Thanks,
jason
> -----Original Message-----
> From: WEAVER, Simon [mailto:simon.weaver at astrium.eads.net]
> Sent: Friday, July 21, 2006 3:58 AM
> To: Brooks, Jason; veritas-bu at mailman.eng.auburn.edu
> Subject: RE: [Veritas-bu] Troubleshooting Guide Question
>
>
> Jason
> If it was me in this position (and it isnt!) I would enable
> BPBKAR and BPBRM logging and where possible find out what the
> client is doing when performing the backup!
>
> I do not know your network environment or your OS, but if I
> assume the client is Windows, turn off any VSP/VSS open file
> agents, disk I/O or any AV and retry again.
>
> In activity monitor, note the date / time the backup failed
> and compare this with the BPBKAR logs to determine where the
> cause / process is causing the problem.
>
> Check disk space too. Finally - ensure Network connections
> and speeds are correct and set for the maximum throughput.
> This is common for issues like connection reset by host or client.
>
> Hope its of some help
>
> Regards
>
> Simon Weaver
> 3rd Line Technical Support
> Windows Domain Administrator
>
> EADS Astrium Limited, B32AA IM (DCS)
> Anchorage Road, Portsmouth, PO3 5PU
>
> Email: Simon.Weaver at Astrium-eads.net
>
>
>
> -----Original Message-----
> From: Brooks, Jason [mailto:brooksje at longwood.edu]
> Sent: 20 July 2006 14:29
> To: veritas-bu at mailman.eng.auburn.edu
> Subject: [Veritas-bu] Troubleshooting Guide Question
>
>
> I've been running down all the onesy and twosey issues with
> backups today.
> This line in the Troubleshooting guide gives me a fit,
> however. It states:
>
> For detailed troubleshooting information, create a debug log
> directory for
> the process that returned this status code, retry the
> operation, and check
> the resulting debug log.
>
> Here's what I'm dealing with now:
>
> 7/19/2006 11:11:11 PM media client Error 35692 Backup
> socket read failed, An existing connection was forcibly
> closed by the remote
> host. (10054)
>
> The end result is a status 13. How do I determine the
> process that returned
> this? Dig further through the logs? Or is there a cleaner way?
>
> Thanks,
> Jason
>
>
> ------------
> Jason Brooks
> Computer Systems Engineer
> IITS - Longwood University
> voice - (434) 395-2916
> fax - (434) 395-2035
> mailto:<brooksje at longwood.edu>
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
> This email is for the intended addressee only.
> If you have received it in error then you must not use,
> retain, disseminate or otherwise deal with it.
> Please notify the sender by return email.
> The views of the author may not necessarily constitute the
> views of EADS Astrium Limited.
> Nothing in this email shall bind EADS Astrium Limited in any
> contract or obligation.
>
> EADS Astrium Limited, Registered in England and Wales No. 2449259
> Registered Office: Gunnels Wood Road, Stevenage,
> Hertfordshire, SG1 2AS, England
>
|
