| > Data is first stored on console$logfiles. It's transferred to
> console$archive in two situations:
>
> 1) Planned archiving, data before "keep" time is archived
> 2) Auto archive, when File Space critical threshold as defined
> in the configuration (show filespace) is reachedfor the logdisk,
> then the oldest hours (as defined in show archive) are moved to
> archive disk.
So far so good...
> But next step is a bit unclear. There is an action routine called
> console$actions:CONSOLE$ARCHIVE_CLEANUP.COM, which by default
> deletes archive files that were created more than two days ago.
> But when is this started, it seems an event CMgr Archive Area Full
> triggers it, but when does this event occur?
Here's the missing piece Hans. The CMgr Archive Area Full triggers the
action routine when the disk that contains the *archive* area is %100
full. The event triggers when the Archive interface detects the archive
disk is full.
> It seems to me that this routine runs regularly without the disk being
> full. I have set up the archive cleanup time to be 10 days, and all my
> archive files disappear after that time, and my archive disk always seem
> to be around 40% full. Is there something setup that I'm not aware of
> that starts archive cleanup at 40% full? Is there any logfile kept for
> the archive cleanup?
Someone could have modified the Archive Area Cleanup filter to trigger
on somehting other than the Cmgr Archive Area Full event. Someone could
have also added the action to another filter by mistake. The point here
is that somone would have had to have modified something.
There is no logfile kept as it's an action routine. You can customize
that action routine in any way you wish. You don't even have to use
it if you do not want to. You will need to setup a job to monitor and
clean the archive area on a regular basis if you have a requirement
to keep X days/weeks/etc. of on-line console data.
Regs,
Dan
Rgds,
Hans
|