My site once had a primary tape pool and a copy tape pool used for
some of our larger clients, with both of these pools collocated by
node. Offsite reclamation was a painful experience. TSM did not
seem to make any attempt to order the input tape mounts
intelligently. When a new input tape was mounted it almost always contained
data from a different node than the preceeding input tape.
As a result, an input tape mount almost always triggered an output
tape mount.

We just upgraded to TSM 5.3 and are considering the use of
collocation groups, with both primary and copy storage pools
collocated by group. If we did this, would input tape mounts for
offsite reclamation be handled more intelligently than they werewith
collocation by node?