Hi David, We're using the TSM scheduler so it should be managed properly. I'll put them in a different order on this machine and see if it makes a difference.
Thanks for the suggestion. Regards, Matthew -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David McClelland Sent: 12 September 2006 10:53 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Log prune on non-standard log names? Hi Matthew, Is your customer's TSM client scheduled using the TSM Central Scheduler (I guess so if it's growing to over 100MBs) for backup operations? This kind of log pruning only happens during a TSM scheduled backup operation (not when the backup operation is scheduled via TWS/cron/Windows Scheduler etc). There's certainly nothing in the docs that I've found to suggest that changing the schedlogname will prevent pruning (it would be a travesty if it did). As an off-the-wall suggestion, have you tried switching the order in which the two options appear in the dsm.opt? Rgds, David McClelland Data Protection Specialist IBM Tivoli Storage Manager Certified Consultant Shared Infrastructure Architecture and Design -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Large, M (Matthew) Sent: 12 September 2006 08:27 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Log prune on non-standard log names? Hi All, One of my customers recently came to me to say that they had a 100MB log file from TSM sitting in their file system, which confused me since the setting clearly stated in the options file (Win2K) says SCHEDLOGRETENTION 7 schedlogname dsmsched_1yr.log Does anyone know if I should expect these settings to prune the dsmsched_1yr.log or must I manually trim this file when necessary? Clients - 5.2.4.4 Server - 5.2.7.1 Many Thanks, Matthew TSM Consultant ADMIN ITI Rabobank International 1 Queenhithe, London EC4V 3RL 0044 207 809 3665 _____________________________________________________________ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _____________________________________________________________ To find out more about Reuters visit www.about.reuters.com Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
