Backupsets aren't stored in pools so no to the question about pools!

Yes, this is a good idea but only if you have the time at the end of the
month to get it done.  To generate the set TSM will read data from whatever
tapes the client data is stored on.  If there are lots of tapes, this means
lots of mounts.  I have not done this myself but I've done some TSM health
checks on systems where they were trying to.  Notice I said trying to.  They
weren't having luck getting the work done in a timely fashion.  So, that's
one negative.

The other negative is that the backupset tape is tracked in the volhist
table rather than in the volume table.  Therefore it is a little easier to
lose track of the tapes that contain backupsets.  Not a real downer but
something to consider.

Finally, generate backupset creates a tape from the client's active files.

You are right having the client move all the data to the server for an
archive can be problematic.  I like the approach of using a targeted archive
rather than a general archive: only archive the stuff you really need to
archive, not the entire client. That should help to cut down on the amount
of data you need to move.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs, CO 80949
lipp AT storsol DOT com or kelly.lipp AT storserver DOT com
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175