Hi,

I have successfully upgraded a customer TSM 5.5.2 to TSM 6.1 with just 18 GB of 
TSM database. We took backups of about 30nodes and later found the TSM server 
is stopped because of filesystem full on Linux. I found that both tsm log and 
archive log file systems were full. In about 5 hours TSM filled the 55 GB 
space. After moving the logs to a different filesystem, TSM started. Next day 
same thing happens but this time after moving the logs, tsm database did not 
come up.

TSM 6.1 is now also become a lousy product like other Tivoli Management 
software. Another pain is the reporting tool.

Could anybody explain why TSM generate so many transaction logs?

Regards,

Sajjad

+----------------------------------------------------------------------
|This was sent by it-tiger AT hotmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------