ADSM-L

Re: How big of a TSM DB is too big?

2005-10-26 14:03:01
Subject: Re: How big of a TSM DB is too big?
From: Paul Zarnowski <psz1 AT CORNELL DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 26 Oct 2005 14:02:24 -0400
Karel,

We have been waiting for online audits and defrags for a long
time.  Yes, they will be nice if and when they are available.  I
agree with your other points about what "should be".  However, my
recommendation is based on hard-won experience.  When expiration
starts taking longer and longer, you can get into a negative-feedback
loop and your database size can balloon, restore performance can
suffer, and all the other implications of running a large
database.  If you're going to go large, keep a sharp eye on your
expiration performance.  If you see it starting to take longer and
longer, be prepared to act.  When we saw this, it fell off quickly,
and we weren't watching for it, and consequently went through a
challenging period.

..Paul

At 01:42 PM 10/26/2005, Bos, Karel wrote:
Somewhere in the near future, ITSM will be able to do audits and defrags
online. And, 150 GB of ITSM database size shouldn't be considered big
these days. Hardware, IO, Mem and CPU power, all of which can handle the
load. Why isn't ITSM build to work on that.

Still, I hold on to the first part and hope these functions will be
available if and when I need them.

Regards,

Karel


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

<Prev in Thread] Current Thread [Next in Thread>