On Apr 26, 2009, at 9:03 AM, Remco Post wrote:

On Apr 26, 2009, at 12:10 , Peter Buschman wrote:

Apologies if this is a well-known question but I am scratching my
head trying to answer it.

Basically, what I want to know is if a migration job in TSM job will
also migrate expired data on the volumes it is migrating.  In a
sense, I am wondering if part of the effect of reclamation can be
achieved through initiating migration to another storage pool.

If data is migrated from one storage pool to another, do the volumes
in the new storage pool still contain expired files that were in the
first storage pool after the migration?

Expired data is not in the TSM database any more, so it can't be
migrated.

Without contradicting Remco's point, I'll add that the MOVE DATA
command includes an optional parameter, RECONSTRUCT, that would
influence the recovery of space used by files expired from an
aggregate of data. This option may occasionally trigger some confusion
about when space used by expired files is recovered during copy
procedures.