.Backup File size???

[AAMFlyer]

This fall I was having problems with my EBOX 4300 locking up every 8-10 days and Boris couldn't find anything and neither could I.....so I went ahead and saved my .backup data and rebuilt a new CF Card - but since it appeared to happen after I started updating software in the fall to the 4.6 versions - I went back to an older version of the software - reloaded and started at 4.2 then updated back up to 4.5i - then I loaded my data.....I am now running 4.5i and it has been very stable .....when I created the new CF card I reloaded my data with the .backup file after getting to 4.5i and it all loaded just fine back to day 1....it's all there.

BUT.....here is what's weird and I'm wondering if something like this could have been the problem........ With Version 4.6r my backup file size was 82 mb in size (about a year and half of data).....after loading back into 4.5i with a new CF card....my .backup files is now half the size at only 38 mb........??????

Ideas why the huge difference??? I also run 2 EBOX 4300's.....one is still running 4.6t and the file size there is almost 88 mb with several more years of data.....but I"m not having problems with that one...

Gregg

[AAMFlyer]

Boris - any thoughts on this....it seems strange that file size would double by a version increase....? Is there simply more data being collected? Thanks

[skyewright]

Boris - any thoughts on this....it seems strange that file size would double by a version increase....? Is there simply more data being collected? Thanks

Is it possible that some temporary file(s) that have since been reduced in size by a re-boot were being included in the backup?

I thought of this as recently one of my Meteohubs ground to a halt unexpectedly. On investiagtion i found that its 'disk' was 100% full, which was odd as I knew it to contain less actual data that another Meteohub that is recording from all the same sensors plus some others and that other Meteohub has loads of spare capacity.

The 'problem' seems to have been that over an uptime of >200 days it had accumulated a large volume of temporaries. After a reboot the tempories had gone and normal working resumed.

Just a thought...