Hi TSM-ers!
Here is a small follow up on my PMR about the recovery log utilization.
I'm at TSM level 2, still trying to convince them that there is
something broken in the TSM server code. To convince them, I have
changed the logmode to normal on one of my servers. I created a graph
(through TSMManager) which shows the recovery log utilization during
last night's client backup window and is doesn't differ much from the
night before, with logmode rollforward. When running in normal mode, TSM
should only use the recovery log for uncommitted transactions, so
utilization should be very low. My log is 12 Gb and the backuptrigger
value (75%) was still hit twice!
This clearly shows that there is something wrong with TSM, let's hope I
can convince Level 2 too, so my case gets forwarded to the lab.
I'll keep you guys posted!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************