Re: Auditdb timing - FYI
2003-05-27 14:57:48
At 08:31 AM 5/27/2003 -0500, Stapleton, Mark wrote:
To tell the truth, the problem lies in the size of your TSM database
(and probably also the speed of disk upon which said database resides
and the speed of the processor used by the TSM server). You probably
ought to consider breaking it up into several separate TSM servers. This
gives the added ability to export nodes to alternate serves when a
particular server is giving you fits.
When you grow to enterprise size, you've got to start thinking in
enterprise mode.
The truth is that TSM should have self-repairing capabilities in
it. Requiring outages of any length to run an audit is unreasonable. If
you know anything about Gretchen's environment, you should know that she
already has lots of TSM servers. Saying that the solution is to keep
splitting your servers is not a realistic solution. This is only a
workaround, and evades the real problem.
Let's say Gretchen had 6 servers in place of the one she had to run an
audit on. She would still be down for a day to run the audit. Unacceptable.
My 2 cents.
..Paul
--
Paul Zarnowski Ph: 607-255-4757
719 Rhodes Hall, Cornell University Fx: 607-255-8521
Ithaca, NY 14853-3801 Em: psz1 AT cornell DOT edu
|
|
|