This is not unusual at all. The log size is related to the amount of activity, not to the DB size. Some people have a log size bigger than their DB, some do not. It is not uncommon to have TSM logs > 5 GB!
The simple thing, just make the log bigger. Here's another idea you could try: Create a devclass with TYPE=FILE (goes to disk). Schedule an admin command on the weekends that does a DB backup with type=incr, using the TYPE=FILE devclass. That can run with no operator intervention, and will clear your log. Then on Monday you can go back to your DB backups on DLT. So : on Friday DB BACKUP TYPE=FULL to DLT devclass on Sat DB BACKUP TYPE=INCR to file devclass on Sun DB BACKUP TYPE=INCR to file devclass on Mon DB BACKUP TYPE=FULL to DLT devclass -----Original Message----- From: Andrea GRIGOLO [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 11:29 AM To: [EMAIL PROTECTED] Subject: Recovery log problem Hello ! I have a little problem with the recovery log of a TSM server 4.2.1.7 (with a Compaq TL891DLX). There are about 50 client workstations, 5 client servers (mostly file servers) and 5 TDP for MSSQL. This grows very fast and I have no idea if it is normal or not. I have 500 megs for dbvolumes and 900 for the log, but I still get the "insufficent recovery log" message after the weekend (when the dbbackup is not done, as we do it on an external stand-alone DLT and no operator is there during the weekend to swap the tape). So, is it normal to have a recovery log twice bigger than the dB ? How could I reduce dB size (I already force expiration and I delete old volhistory entries)? Thank you Andrea ************************************************************************** This message may contain confidential information and is intended solely for the use of the addressee. If you are not the intended recipient of this message, please notify the sender immediately and do not disclose, use, disseminate or copy this message. The information contained in this message is subject to Systemat's General Terms and Conditions. Any personal opinion expressed in this message reflects the opinion of the sender and not Systemat's opinion. **************************************************************************
