Well well, so we actually dont have a criteria for unloading dbīs? I agree more or less (not necessarily buy new HW) with all responses so far. But I was trying to define a criteria in my first unclear answer. You dont have to unload your db, your TSM server will still run continuously. Iīve only done it twice in our production system and it went ok. It was installed summer -98 with a 30Gb db and an average of 150Gb daily backuped. Unload/load DB didnt look like rocket science to me. If I can manage to do an unload, everyone can. And if you make up a checklist and include Rogerīs arguments. You will be fine.:-] 1 all TSM stuff - ok 2 sanity - not sure 3 high blood presure - ok 4 marriage - ok, I bought her a Cucci bag with the extra money i got..
//Henrik
Mark
Stapleton To: [EMAIL PROTECTED]
<stapleto@BER cc: (bcc: Henrik Wahlstedt)
BEE.COM> Subject: Re: database reorganisation
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
2003-01-20
21:21
Please
respond to
"ADSM: Dist
Stor Manager"
On Fri, 2003-01-17 at 04:30, Francois Chevallier wrote:
> What are the best criteria to know if it's time to reorganize the tsm
> database (by unloaddb /loaddbb)
It's almost *never* time to unload and load your TSM db. Most of those
who have done so to "fix" a fragmented db discover that the system will
go back to its original state in a matter of days or weeks.
The real way to improve db performance is to place your db volumes on
fast-access disk (SSA, etc.)
--
Mark Stapleton ([EMAIL PROTECTED])
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.
