Thanks for the pioneer work with 6.1! Myself and other free riders are
in deep gratitude to those contributing to making version 6 stable and
useful. When the dust settles in a year or so I too may choose to
upgrade knowing that others have taken the risk of losing their data and
personal sanity in making version 6 a success.

Frankly, I am a bit worried. I look at the bloat at Passport
Advantage(4GB download for reporting? Seriuos?) and it seems that every
piece of s**t software that IBM has produced now is forced upon us.
Already TSM in itself has a steep learning curve with a lot of different
"strange" concepts, but IBM obviously doesn't seem to think this is
enough in their ongoing effort to scare off potential customers. An
installation of 6.1 with reporting and administration on a small site
with for example a 2 drive, 40 slot library will require how many
servers? 3? One for TSM, one for admin and one for reporting?

Hope TSM don't end up as DB2, a database in use by IBM only shops.

I apologize in advance for the negativity expressed above.


Hans Chr.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Wednesday, June 03, 2009 7:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM 6.1 Installation Problems

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.s
rv.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

This email originates from Steria AS, Biskop Gunnerus' gate 14a, N-0051 OSLO, 
http://www.steria.no. This email and any attachments may contain 
confidential/intellectual property/copyright information and is only for the 
use of the addressee(s). You are prohibited from copying, forwarding, 
disclosing, saving or otherwise using it in any way if you are not the 
addressee(s) or responsible for delivery. If you receive this email by mistake, 
please advise the sender and cancel it immediately. Steria may monitor the 
content of emails within its network to ensure compliance with its policies and 
procedures. Any email is susceptible to alteration and its integrity cannot be 
assured. Steria shall not be liable if the message is altered, modified, 
falsified, or even edited.