[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

1628.0. "keep age question" by JETSAM::WOODCOCK () Wed Oct 09 1991 18:28

Hi there,

I have just noticed that my historical files are at +250,000 blocks. My
recordings have the default 45 day keep age. But I just pulled out some
counters from two months ago. Am I misunderstanding this keep age feature
or is it not working??

any info appreciated,
brad...
T.RTitleUserPersonal
Name
DateLines
1628.1TOOK::SHMUYLOVICHThu Oct 10 1991 11:0346
    re: .0:

>I have just noticed that my historical files are at +250,000 blocks. My
>recordings have the default 45 day keep age. But I just pulled out some
>counters from two months ago. Am I misunderstanding this keep age feature
>or is it not working??

	Some details how "keep age" works:

   Let's assume that you specified record command as follow:

	RECORD NODE4 SAM PARTITION = COUNTERS,-
			 POLLING PERIOD = 00:01:00,-
			 KEEP AGE = 1 00:00:00,-
			 in domain FOO

   Every one minute this recording request writes counters into
   historical repository and deletes historical counters that are older 
   that one day. 
   If this recording request is suspended or deleted the process of
   data collecting and data purging are stopped. Collected historical
   data will be kept in the historical repository until the new recording
   request for the same entity and partition is specified. 
   If you wish to delete historical data whose recording requests are 
   suspended or deleted you can use the PURGE command.

   Purge command does not remove a record from historical file. It means that
   using Purge ("keep age" argument in the Record directive) you can not
   compress the file size. To do this you have to follow recommendations 
   described in the Historian release notes:

            To reclaim the purged space in the repository files after
            the repositories must be compressed using the following DCL
	    command procedure that takes the file name of the repository 
	    and produces a compressed version of the file:

                $ ANALYZE/RMS/FDL/OUTPUT=PURGE.FDL 'p1'
                $ EDIT/FDL/NOINTERACT/ANALYZE=PURGE.FDL PURGE.FDL
                $ CONVERT/FDL=HAR.FDL 'p1' *

            Note that all recordings for the domain historical
            repository being compressed must be suspended.


	Sam
 
1628.2thanks for infoJETSAM::WOODCOCKThu Oct 10 1991 16:0112
Sam,

Thanks for the rundown. I now realize I need to do the extra steps to get
the space back (it's been quite some time since I reviewed the Release
Notes). Also I reissued a command for counters past 45 days, what I got
was the counters from 45 days ago, although I would have thought it would
return "no counters for specified time". This is probably what I got the
first time but I didn't pay close enough attention to the date on the
Counter Creation Time.

best regards,
brad...