On 7 apr 2009, at 20:41, Thomas Denier wrote:
I am in the process of planning a TSM configuration for dual data centers. I expect to have one instance of the TSM server code at each data center dedicated to the library manager function for the automatic tape library at that site. Based on reports from other sites that have set up library managers, I expect a database size of about 200 megabytes for each library manager. I expect to be using TSM Version 6. The documentation indicates that the minimum size for the active log is 2 gigabytes. This size will double if I mirror the active log, as I would prefer. Is there any way to avoid the absurdity of an active log 20 times as big as the database it supports?
use TSM v 5.5 ;-) The DB2 active log is made out of 500MB files. You need 2 to be able to perform any log circulation, 4 if you want to be able to support transactions that span two logfiles (I guess, judging from this minimum). Maybe you could perform unsupported tweaks in DB2 te decrease the size of the logfiles, but I would just learn to live with the 2 GB minimum size. -- Met vriendelijke groeten/Kind regards, Remco Post [email protected]
