ADSM-L

Re: Expiration not working

2000-04-20 07:39:18
Subject: Re: Expiration not working
From: Richard Sims <rbs AT BU DOT EDU>
Date: Thu, 20 Apr 2000 07:39:18 -0400
>In the readme for ADSM 3.1.2.55
>IY06778 MULTITHREADED EXPIRATION RUNS VERY SLOWLY, BITFILES EXAMINED
>INCREMENT VERY SLOWLY
>
>Seems like for every archived directory, it has to examine every other
>archived directory with that same path or beneath it to verify if it can
>be expired or not.  To avoid this use a skipdirs=yes option.

I have to say that I'm getting awfully concerned about the quality of the *SM
software coming out of Tivoli.  We're encountering one crippling problem after
another, and administration is being cluttered by a raft of special commands
and operands to circumvent problems - and sometimes the circumventions
conflict.  The Tivoli Storage Manager product is going to degenerate into a
shambles if this continues.  Tivoli *has* to get serious about this and, as
we've said before:
  - Do careful design
  - Conduct code reviews
  - Do comprehensive testing

TSM is supposed to be the rock-solid vehicle that customers are to depend upon
to protect their data.  I no longer feel that confident in what is going on
inside TSM: it's more probabilistic than certain what's going to happen when
you go to do something with it.  The product as it stands now is an
embarassment to a company that prides itself on enterprise management and
certain results.  The architectural problems introduced in v3 (for example, No
Query Restore) have yet to be resolved, after almost two years.  We've been
suffering for a year with the archived directories fiasco.  Database recovery
remains horrendous.  This is a very sad situation.

       Richard Sims,  Boston University OIT
<Prev in Thread] Current Thread [Next in Thread>