We had an image backup failure over the weekend. The schedule started as
it normally does at 08:30am, but it was stopped a few hours later (he had
expected it to use two drives), so he updated the schedule to start a few
minutes later. it started again, and failed with these messages in the
dsmerror.log

It's the ANS1289W's that I'm interested in.

18-06-2005 10:16:47 sessSendVerb: Error sending Verb, rc: -50
18-06-2005 10:16:47 sessSendVerb: Error sending Verb, rc: -50
18-06-2005 10:16:47 ANS1017E (RC-50)  Session rejected: TCP/IP connection
failure
18-06-2005 10:16:47 ANS1424W Retrying failed image operation for volume
\\tsml902a\f$.
18-06-2005 10:16:59 sessSendVerb: Error sending Verb, rc: -50
18-06-2005 10:16:59 sessSendVerb: Error sending Verb, rc: -50
18-06-2005 10:17:01 ANS1228E Sending of object '\\tsml902a\f$' failed
18-06-2005 10:17:01 ANS1017E Session rejected: TCP/IP connection failure

18-06-2005 10:17:01 ANS1813E Image Backup processing of '\\tsml902a\f$'
finished with failures.

18-06-2005 10:37:28 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0bea8 and 0:8b0c0a7
18-06-2005 10:37:29 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0c0a8 and 0:8b0c2a7
18-06-2005 10:37:30 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0c2a8 and 0:8b0c4a7
18-06-2005 10:37:30 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0c4a8 and 0:8b0c6a7
18-06-2005 10:37:31 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0c6a8 and 0:8b0c8a7
18-06-2005 10:37:31 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0c8a8 and 0:8b0caa7
18-06-2005 10:37:32 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0caa8 and 0:8b0cca7
18-06-2005 10:37:32 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0cca8 and 0:8b0cea7
18-06-2005 10:37:33 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0cea8 and 0:8b0d0a7
18-06-2005 10:37:33 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0d0a8 and 0:8b0d2a7
18-06-2005 10:37:34 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0d2a8 and 0:8b0d4a7
18-06-2005 10:37:34 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0d4a8 and 0:8b0d6a7
18-06-2005 10:37:35 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0d6a8 and 0:8b0d8a7
18-06-2005 10:37:35 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0d8a8 and 0:8b0daa7
18-06-2005 10:37:36 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0daa8 and 0:8b0dca7
18-06-2005 10:37:36 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0dca8 and 0:8b0dea7
18-06-2005 10:37:37 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0dea8 and 0:8b0e0a7
18-06-2005 10:37:38 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0e0a8 and 0:8b0e2a7
18-06-2005 10:37:38 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0e2a8 and 0:8b0e4a7
18-06-2005 10:37:39 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0e4a8 and 0:8b0e6a7
18-06-2005 10:37:39 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0e6a8 and 0:8b0e8a7
18-06-2005 10:37:40 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0e8a8 and 0:8b0eaa7
18-06-2005 10:37:40 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0eaa8 and 0:8b0eca7
18-06-2005 10:37:41 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0eca8 and 0:8b0eea7
18-06-2005 10:37:41 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0eea8 and 0:8b0f0a7
18-06-2005 10:37:42 ANS1289W Bad areas on '\\tsml902a\f$' between sectors
0:8b0f0a8 and 0:8b0f2a7
18-06-2005 10:37:42 ANS2026W Bad sectors were detected on the volume
'\\tsml902a\f$'.
18-06-2005 10:37:42 ANS1425W Retry of failed image operation for volume
\\tsml902a\f$ is not possible due to severe error.
18-06-2005 10:37:44 ANS1228E Sending of object '\\tsml902a\f$' failed
18-06-2005 10:37:44 ANS1069E An error occurred while reading data from the
device

This is a 2TB disk and so far I've been unable to convince the sysadmins
that they should run a some kind of disk check before trying to run the
backup again.
Since this is also a flash-copy of the file system which is mapped to the
node in times of backup, I'm not sure if those details add to the
complexity of the environment - did TSM got those errors directly off the
disk it was reading or did the flash copy copy bad bytes?

When I've got the flash-copy logs I'll be able to eliminate it, until then
has any one been down this path already?

Cheers,
Matthew




Aviva plc
Registered Office: St. Helen's, 1 Undershaft, London EC3P 3DQ
Registered in England Number 02468686
www.aviva.com

This message and any attachments are confidential.
If you are not the intended recipient, please telephone
or e-mail the sender and delete this message and any
attachment from your system. Also, if you are not the
intended recipient you must not copy this message or
attachment or disclose the contents to any other person.