Question : Another server migration error

The error log created from my data copy to the destination server contains and error as follows"

'NWSMTS error: The sequence number is invalid.' (Source Server: MAIN Path: 'DATA:WORDS/Archives/Rbt-closed/Brown, S/' Error: 'fffdffd8' Function: 'NWSMTSOpenDataSetForBackup'
Migerror.log message: 0xfffdffd8      NWSMTSOpenDataSetForBackup      MAIN      NEWMAIN      DATA:WORDS/Archives/Rbt-closed/Brown, S/)

'NWSMTS error: The sequence number is invalid.' (Source Server: MAIN Path: '' Error: 'fffdffd8' Function: 'NWSMTSScanNextDataSet'
Migerror.log message: 0xfffdffd8      NWSMTSScanNextDataSet      MAIN      null)

It stopped copying files at this point. I found only one reference (TID 10087482) to this in the Novell KB and it appears to be an error generated by TSAFS.NLM, but should have happened when trying to use the Open Files Option in Backup Exec. Since this happened during the use of Novell's SCMT, their closing comment...

"In reality all older models (TSA500/600) support such an operation, hence this is not a BackupExec issue. But, Veritas may need to reconsider their model to fit with TSAFS design.  "

seems kind of ironic. Any ideas why I get this error and the data copy stops?

Answer : Another server migration error

It depends on 1) how much data there is, 2) how much time I have and 3) how much confidence I have in a) the copy and b) the backups I made before the migration.

A binary-level comparison will compare every file bit-by-bit.  I don't recall but I'm guessing the other option is a checksum verification, where the checksums are recalculated for both sides and compared, and if there's a checksum mismatch it throws a flag.  That's much faster than bitwise.