I suggest you call support.
This can either be a very bad thing resulting from a hardware error
(i.e., what is actually on your disk pool doesn't match what is in your
TSM data base), or a minor thing resulting from a code bug.
I saw some similar things in early 5.3 versions (also Windows) when the
files being moved were very large and spanned volumes. And I beleve
more than 1 patch was required to fix all cases.
SO depending on your tolerance level, you can upgrade your code to TSM
5.3.3.3 (that's the last patch level we put on to address a similar
problem), or call support.
But if you call support, DON"T let level 1 get away with just telling
you to delete the file (that happened to the last customer I advised to
call them). That will appear to make the problem go away, but it will
just come back to bite you later. You want to run ANOTHER backup of the
file so that you have one available, but keep the bad one around so you
can run a trace if necessary when you get to level 2 support.
Wanda Prather
"I/O, I/O, It's all about I/O" -(me)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Kurt Buff
Sent: Wednesday, November 15, 2006 9:31 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Errors moving file from disk to tape
All,
Running TSM 5.3.x on our Win2k machine, which is backing up data from
our
Win2k3 file serer.
I've recently started dumping a database to the file server that's
around
61gb in size, and the Win2k box seems to be choking while moving the
file
from disk to tape internally. The disk array for the Win2k box is not
quite
2tb, on a 3ware array of 8 PATA drives.
The database file is a full dump each night, given the same name each
time.
I'm not seeing errors in the event log that look interesting or relevant
to
this problem.
Any thoughts? More info available if needed.
Here are the error messages we're seeing:
----------Begin Log Snippet----------
ANR1330E The server has detected possible corruption in an object being
restored or moved. The actual values for the incorrect frame are: magic
8F0DA670 hdr version 37816 hdr length 62476 sequence number 101823309
data
length 370C5960 server id 1536713424 segment id 5320757052904444595 crc
C6B42145.
ANR1331E Invalid frame detected. Expected magic 53454652 sequence
number
00148128 server id 00000000 segment id 0000000053513180.
ANR1330E The server has detected possible corruption in an object being
restored or moved. The actual values for the incorrect frame are: magic
66371DED hdr version 31706 hdr length 48550 sequence number -1501832601
data length 7BDA67BD server id -630735450 segment id
13665746297275917947
crc A67BDA67.
ANR1331E Invalid frame detected. Expected magic 53454652 sequence
number
00000077 server id 00000000 segment id 0000000053517615.
ANR1330E The server has detected possible corruption in an object being
restored or moved. The actual values for the incorrect frame are: magic
A4ECEAA6 hdr version 29637 hdr length 22108 sequence number 2145482599
data
length D29CEB93 server id 426614096 segment id 15022471743897101349 crc
96D9D54C.
ANR1331E Invalid frame detected. Expected magic 53454652 sequence
number
00000112 server id 00000000 segment id 0000000053600878.
ANR1001I Migration process 27 ended for storage pool DISKPOOL.
ANR0986I Process 27 for MIGRATION running in the BACKGROUND processed
124562
items for a total of 22,930,460,672 bytes with a completion state of
FAILURE
at 13:04:18.
----------End Log Snippet----------
Thanks,
Kurt Buff
Lead Network Administrator
Zetron, Inc.
425.820.6363 x463
kbuff AT zetron DOT com
PO Box 97004
Redmond, WA 98073
|
