Yes, thats about 600MB.  Expiration doesnt run too badly.  Expspeed says
we are doing about 2M pages per second.  It seems like TSM grabs one
CPU, runs it at 100%, and very little I/O is occurring during all this
time.  The DB is 90.3% of 35000MB, and the DB was reorged about 3 months
ago.

Prather, Wanda wrote:

Wow.
I thought 20 minutes was a long restart time!.
Never heard of anything that bad before.

How big is your DB?  Does your expirarion take a really long time to
run?

You are only applying about 600 MB of updates, yes?

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andy Carlson
Sent: Monday, January 10, 2005 12:20 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM Long Restart Time


Wehave had a problem over the years with LONG TSM restart times if the
recovery log has anything in it.  Here is what we are running:

AIX 5.1 ML4+ Running on a P670, 4 Proc, 16GB Memory
TSM 5.2.1.1

We had an outage on one of our TSM instances Friday.  The log is
currently in normal mode, 12GB in size.  It was 5.1% full.  The restart
took 10 hours!.  I have noticed this with various releases of TSM, so
this is not new.  I talked to TSM about it before, and did not get any
good answers.  Has anyone else seen anything like this?  Would Roll
Forward DB mode help?  Thanks for any info.

--
Andy Carlson - Senior Technical Specialist
BJC Healtcare
------------------------------------------------------------------------
---
Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License:
$8.95/month,
The feeling of seeing the red box with the item you want in
it:Priceless.

--
Andy Carlson - Senior Technical Specialist
BJC Healtcare
---------------------------------------------------------------------------
Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month,
The feeling of seeing the red box with the item you want in it:Priceless.