Curtis, I didn't read this whole thread, but I don't think this is quite
true.  I believe that all files in an aggregate relate to a single common
database entry which indicates where the aggregate is stored (which tape or
disk volume, and location on that volume).  When files in an aggregate are
moved (i.e., migrated from disk to tape), then the one aggregate record is
updated in the database to reflect that the aggregate was moved, but all of
the individual file entries (that make up the aggregate) do not need to be
updated.

So yes, each file it's own database entry, but that database entry doesn't
necessarily indicate *where* the file is stored.  That information is kept
in an aggregate record.

It should still be true that if an aggregate transmission is interrupted,
the entire transaction is rolled back.

The above is my understanding, but I do not know it as fact.

..Paul


At 03:54 PM 1/28/2008, Curtis Preston wrote:

So I'm back to my original understanding then, that all files are
tracked individually in TSM.  It's just that TSM doesn't do a commit
until an aggregate has completed.  This explains why the entire
aggregate must be redone if it fails halfway through due to a
busy/locked file.  If it fails, the entire transaction is rolled back,
so there is no record of any of the previous files in the aggregate.  Am
I still on the right page?

--
Paul Zarnowski                            Ph: 607-255-4757
Manager, Storage Services                 Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801    Em: psz1 AT cornell DOT edu