In our environment, I have seen this when a checkdisk has been performed, a
drive has been swapped, defragmenting a drive can cause the defragmented
data to be sent, moving disks in a SAN. I would have to guess that breaking
a mirror set and bringing up the mirror instead of a primary drive could
produce the same result. To test you can move all the data from one
directory into another and then back to the same directory, I am sure it
will all be backed up at the next backup.

I do not know every technical nuance to TSM but when the file is scanned and
checked against the TSM DB it sees that the file location has changed and
there needs to be backed up. I have not looked into a way to work around
this but I would guess there is not a way.


Duane Ochs
Systems Administration
Quad/Graphics Inc.
414.566.2375