I have seen that. It was a little complicated... ; ) We were using data domain dd460's as sequential pools. These boxes are replicated. We lost the primary dd460 only to find that replication had not been working for a period of time. When we switched the replica with the primary, tsm thought it had many files in this pool that were not there. We got the errors anytime we tried to access a missing file (usually during a reclaim). The only way to correct it was to run restore volumes for any lost files.
Cory Heikel Tivoli Systems Administrator Hershey Medical Center (717) 531-7972 >>> "Gill, Geoffrey L." <[EMAIL PROTECTED]> 1/23/2007 2:35 PM >>> This is the first time I have seen anything like this and I thought I'd throw it out there to see if anyone else has. There is nothing in the AIX logs to indicate anything odd going on there. It looks like there was a migration running, which reports SUCCESS, when this happened and I see no tape error messages and no tapes in an odd state. TSM Server is AIX 5.3 TSM is 5.3.3.0 1/23/2007 6:45:43 AM ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 5A4D4E50 hdr version 0000 hdr length 0005 sequence number 00000009 data length 00329C3F server id 00262096 segment id 0000000000000000 crc 00000000. 1/23/2007 6:45:43 AM ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 00000980 server id 00000000 segment id 0000000188983073. Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: [EMAIL PROTECTED]
