Hi,

Also think about about what and why.

If you need to archive 50TB of data to create space, to archive just
once and move the data to TSM, just do it, it isn't such a problem.

But if you do the archive as an other way of doing for instance
monthly backups, don't use archives, use backupsets instead.

And if you do a lot of archives in a way as it ment to be, and there
is no other way, you can also think about an other instance, only for
archives.
Normaly archives has long retentions, so expire inventory doesn't need
to run daily, but can also run once a month. And if all archives in a
stgpool has the same retention, you don't need to run space reclaim
too.

Good luck,
Maurice van 't Loo

> Need to archive 50tb of data with millions of files, here is the caveat, tsm 
> db at 220gb, planning on upgrading from 5.5 to 6.2 in the near future, but 
> currently waiting for newer hardware, how would one accomplish this without 
> causing too much db bloat? Any ideas would be greatly appreciated.