ADSM-L

Re: Log prune on non-standard log names?

2006-09-14 11:32:52
Subject: Re: Log prune on non-standard log names?
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 14 Sep 2006 11:30:38 -0400
Another thing that can cause pruning to fail, is not having enough free
space on the disk to make a copy of the log file (100MB) before the
pruning is done.  But in the dsmsched.log file, you will see the pruning
failure when that happens. 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Gee, Norman
Sent: Tuesday, September 12, 2006 11:40 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Log prune on non-standard log names?

This has happen to us every so often that the sched log does not get
prune.  Usually if I restart the Schedule process in the control panel
services panel, the log file will trim it self correctly.



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David McClelland
Sent: Tuesday, September 12, 2006 2:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: 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
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

<Prev in Thread] Current Thread [Next in Thread>