ADSM-L

Re: [ADSM-L] Active logs taking 4 days to delete in 6.2

2011-07-25 09:25:01
Subject: Re: [ADSM-L] Active logs taking 4 days to delete in 6.2
From: Paul Fielding <paul AT FIELDING DOT CA>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 25 Jul 2011 07:19:40 -0600
Yeah, I am.  The thing that's wierd is the 4 day delay.  Active logs are
getting deleted, but they're waiting 4 days to do so.  And this is not how
the behavior has always been since going to 6.2.  I just noticed the change
one day.  Very bizarre...


On Mon, Jul 25, 2011 at 6:59 AM, Zoltan Forray/AC/VCU <zforray AT vcu DOT 
edu>wrote:

> Are you doing "backup volhist" as well?  IIRC, there was a discussion that
> you needed to do that as well to purge activity logs.  Plus it is a
> requirement to perform DB restores on 6.x servers.
>
>
> Zoltan Forray
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>
>
>
> From:
> Paul Fielding <paul AT FIELDING DOT CA>
> To:
> ADSM-L AT VM.MARIST DOT EDU
> Date:
> 07/25/2011 08:50 AM
> Subject:
> [ADSM-L] Active logs taking 4 days to delete in 6.2
> Sent by:
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
> So, at one of my client sites I noticed that the Active log filesystem is
> sitting at 82% full.  This is not normal for this TSM server.  Looking in
> the filesystem I saw active logs going back four days.   Checking the
> actlog
> shows that TSM db backups are still running properly every day, but just
> to
> be safe I ran two db backups in succession.  No logs were removed.
>
> I decided to keep an eye on it.  What I see happening is that each morning
> when I look at it, there are still four days worth of logs, but the oldest
> logs are moving forward by a day. ie.  when I looked on July 22, the
> oldest
> log was July 18.  When I looked on July 23, the oldest log was July 19.
>  Today, July 25, I see the oldest log is July 21.
>
> This strikes me as a bit bizarre.  Anyone have any ideas?
>
> regards,
>
> Paul
>