Tend to agree with Simon , im my experience the 10054 error always
sways me in investigating the speed/duplex settings on the NIC , saying
that 9/10 something to do with the network.
Regards
Dave
-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of WEAVER,
Simon
Sent: 21 July 2006 08:58
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
_______________________________________________
Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Notice to recipient:
The information in this internet e-mail and any attachments is confidential and
may be privileged. It is intended solely for the addressee. If you are not the
intended addressee please notify the sender immediately by telephone. If you
are not the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited and may be
unlawful.
When addressed to external clients any opinions or advice contained in this
internet e-mail are subject to the terms and conditions expressed in any
applicable governing terms of business or client engagement letter issued by
the pertinent Bank of America group entity.
If this email originates from the U.K. please note that Bank of America, N.A.,
London Branch and Banc of America Securities Limited are authorised and
regulated by the Financial Services Authority.
|
