Hi Paul,

Many thanks for your answer, it confirms my thoughts, but unfortunately
doesn't solve my problem : once again my server crashed tonight, with a
log of 7 GB and dbbackup trigger defined at 65 % ! The tape was mounted
in a minute but dump of the db on it has been hanging till the server
crashed, approx half an hour later ...
I have now defined an administrative schedule that initiates a db backup
in the middle of the night, but don't find it to be an "elegant"
solution :-(
If someone reading this has another idea, I'm taker !
Cheers.

Arnaud

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       | 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-----Original Message-----
From: Seay, Paul [mailto:seay_pd AT NAPTHEON DOT COM] 
Sent: Tuesday, 21 January, 2003 20:30
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Triggered dbbackup doesn't start immediately


Apparently, the BACKUP DB command does some pre processing now.  Not
sure what.  My system can take 3 to 5 minutes.  I think what is
happening is some log commit logic is running for a while to try to
unpin as much of the log as possible, but that is just a guess.  Then,
my backup starts.  Mine are not triggered backups, they are scheduled to
occur before any significant processing starts.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: PAC Brion Arnaud [mailto:Arnaud.Brion AT PANALPINA DOT COM]
Sent: Monday, January 20, 2003 10:32 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Triggered dbbackup doesn't start immediately


Hi *SM'ers

I noticed an embarasting problem on our TSM server (4.2.3.1) : I defined
a Dbbackup trigger that should start a db backup as soon as our log
reaches 70 % . What happens is that I see the backup triggerered, but
that the effective copy on tape only starts approximativeley 20 -25
minutes later, sometimes leading to a server crash, due to log
saturation (actual log size
: 12 GB). As far as I know a DB backup has the highest priority, so how
can it be that it "waits" so long before proceeding ? More confusing,
Dbbackups initiated manually or per schedule do not behave the same way
: copy on tape starts immediately ...

01/20/03 15:09:18 ANR4552I Full database backup triggered; started as
process 340. 01/20/03 15:46:23 ANR4554I Backed up 48128 of 4159601
database pages. 01/20/03 15:46:53 ANR4554I Backed up 127536 of 4159601
database pages. 01/20/03 15:47:23 ANR4554I Backed up 206320 of 4159601
database pages. Did anybody allready noticed such a behaviour, or have
an explanation on what could be happening there ? Thanks in advance !
Cheers. Arnaud

 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=