Still, this is a good reason why not to let your DB get that large.  Many 
places can't have their TSM servers down for more then 8 hours.  We have Oracle 
and SAP DB's that use TSM to archive their logs.  If we are down for up to 8 
hours they can survive but if we were down for 24 I'm sure many of their log 
directories would fill and the DB would crash.



Daniel Sparrman <Daniel.Sparrman AT EXIST DOT SE> wrote:
Hi Ian

We've made a unload, audit and then a load on this 160GB database.

Didnt take days to complete. The full process took about 40 hours. If we
had choosen not to do the audit, the process would have taken about 28
hours.

Best Regards

Daniel Sparrman
-----------------------------------
Daniel Sparrman
Chef Utveckling & Drift
Exist i Stockholm AB
Propellervdgen 6B
183 62 TDBY
Vdxel: 08 - 754 98 00
Mobil: 070 - 399 27 51



Ian Hobbs

Sent by: "ADSM: Dist Stor Manager"
2004-10-15 06:51
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Splitting apart a Tivoli DB






On Thu, 14 Oct 2004 10:58:54 -0500, Stapleton, Mark wrote:

The magic # I have seen is about 100GB. Even a 100GB database would take
days depending on the
hardware if a full DBAUDIT had to be done.

I wouldn't want to do that .

>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
>Behalf Of Chris Hund

>30GB is a little small for such consideration. Properly configured
>databases, spread across fast spindles, should perform well at twice the
>size.
> ...
>Mark Stapleton (stapleton AT berbee DOT com)
>Berbee Information Networks
>Office 262.521.5627



Ian Hobbs
little_brutus AT rogers DOT com
=======================================================
"Never argue with an idiot. They drag you down to their level then beat
you with experience."
-Dilbert


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com