I could write a book. I have personally opened 4-apars and have tripped
upon numerous other issues.

As for the DB backups required to clear the transaction archive logs:

http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.doc/c_archive_log_space.html

This one caught me off guard. I was testing 6.1 by ex/importing a large
node (which I am going to eventually move, in reality).  With 40M objects
to move, it blew out 350GB of my 450GB disk, in transaction archive logs.
I was unaware (yeah, yeah.....RTFM..) of the requirement for 3-FULL DB
backups (I now schedule 3-FULL DB backups every day) per the document
linked to, above.

Speaking of the DB backups, currently, the majority of them end up with a
timestamp of 2047/11/30, thus making a standard "del volhist" worthless
(keep having to use FORCE to delete them).  See IC61173.



From:
"Allen S. Rout" <asr AT UFL DOT EDU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
06/03/2009 12:05 PM
Subject:
Re: [ADSM-L] TSM 6.1 Installation Problems
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



>> On Wed, 3 Jun 2009 09:58:50 -0400, Zoltan Forray/AC/VCU
<zforray AT VCU DOT EDU> said:


> I agree - way too unstable for production.  Watch out for the hidden
> storage/disk requirements plus the need for 3-FULL DB backups before it
> purges archived transaction logs!


More details, Zoltan?


- Allen S. Rout