[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

5228.0. "HISTORIAN FM and disk consumption" by TAV02::KALAI () Sun Jun 20 1993 06:27


	I looked throw all documentation and notesfiles for some details
on HISTORIAN FM and disk consumption without success.

I have tow major question:
	1.Do we still need to go throw compress in order to reclaim the
	  purged space in the repository files?
	  If yes ,does recording must be suspended during this operation?

	2. Why the repository file continue to grow and doesn't keep
	   the same length between two compress.?

I have a tremendous problem with this subject on one site that need and use 
a lot of history.
Up to now we worked with decmcc 1.2,last week we upgrade to v1.3 .Are we going
to get some good surprises ??


Regards
Kalai Yael

T.R	Title	User	Date	Lines
5228.1		TOOK::SHMUYLOVICH	`Wed Jun 23 1993 11:41`	24
	> 1.Do we still need to go throw compress in order to reclaim the > purged space in the repository files? Yes. > If yes ,does recording must be suspended during this operation? Yes. > 2. Why the repository file continue to grow and doesn't keep > the same length between two compress.? Sorry, I do not understand this question. When the repository is compressed it contains only "alive" records. After this active recordings add more recoprds to the repository file and it grows. >Up to now we worked with decmcc 1.2,last week we upgrade to v1.3 .Are we going >to get some good surprises ?? No, there is no changes in V1.3 Sam
5228.2		TAV02::KALAI	`Thu Jun 24 1993 11:27`	28
	> > 2. Why the repository file continue to grow and doesn't keep > > the same length between two compress.? >>> > Sorry, I do not understand this question. When the repository is > compressed it contains only "alive" records. After this active > recordings add more records to the repository file and it grows. I believe I didn't explain my problem clearly. When I began using History I assumed that the size of the history file will change between 2 values . one value the size of the repository file after compressed with only "alive" records and the second value that it will reach in the delta time between 2 compress. I assumed that this 2 values will be the same all the time .The real life prove different the file keep growing and even worth a moment arrive with size of 500000 blocs that the Historian stop recording so we have to start a new repository file. All this bring us to a very big problem with disk space.The customer is the army he is very strict about keeping information ,for him all this it's DEC problems so we have to give him disks for free. Is it more clear now? Regards Kalai Yael.