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       | 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=