Are you mis-reading/writing that info?    350GB takes 1-hour to expire and
about the same to backup??

My 190GB DB used to take 48+ hours to run expire (350M objects) and
2-hours for a full backups!  With recent cleanup/load balancing by moving
nodes to a new server, the expires are down to 24-hours.



"Conradt, Jeremy" <JConradt AT ASHLEYFURNITURE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/04/2008 11:28 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] Database size, Split to multiple instances or wait for
version 6.1






Expiration takes about 1 hour.  DB Backup takes about 1 hour 15 minutes.

Thanks,
Jeremy

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Wanda Prather
Sent: Wednesday, December 03, 2008 7:01 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Database size, Split to multiple instances or wait
for version 6.1

How long does it take you now to do Expiration and DB backup?



On Wed, Dec 3, 2008 at 4:24 PM, Conradt, Jeremy <
JConradt AT ashleyfurniture DOT com> wrote:

> I have a TSM server currently running version 5.3.5 on Windows 2003
> that we plan to upgrade soon.
> The problem I have is our database has grown to 350 GB.
> The question I have is will version 6.1 of TSM be better capable of
> maintaining a database this size and much larger or should I break it
> apart?
> I would rather keep everything together so we can make better use of
> de-duplication that may be coming out with version 6.
> Thanks,
> Jeremy
>
>
>