Our Hyperic 4.4 community version was broken for a few days due to disk space full issue. After fixing the disk space, now when we restarted the Hyperic server, all the agents are showing as "unavailable" and server seems to be busy in catching up. There are following messages in the server.log. It seems it may take a long long time to catch up. is there a way to tell hyperic to not to catch up but start collecting metrics from the current time?
2011-03-29 11:18:45,948 WARN [Thread-18510] [org.hyperic.hq.measurement.server.session.AvailabilityManagerEJBImpl@899] Avail measurement came in 10 days late, dropping: timestamp=1300545600000 measId=66585 value=1
2011-03-29 11:18:45,949 WARN [Thread-18510] [org.hyperic.hq.measurement.server.session.AvailabilityManagerEJBImpl@899] Avail measurement came in 10 days late, dropping: timestamp=1300545000000 measId=66585 value=1
2011-03-29 11:18:45,950 WARN [Thread-18510] [org.hyperic.hq.measurement.server.session.AvailabilityManagerEJBImpl@899] Avail measurement came in 10 days late, dropping: timestamp=1300544400000 measId=66585 value=1
2011-03-29 11:18:45,948 WARN [Thread-18510] [org.hyperic.hq.measurement.server.session.AvailabilityManagerEJBImpl@899] Avail measurement came in 10 days late, dropping: timestamp=1300545600000 measId=66585 value=1
2011-03-29 11:18:45,949 WARN [Thread-18510] [org.hyperic.hq.measurement.server.session.AvailabilityManagerEJBImpl@899] Avail measurement came in 10 days late, dropping: timestamp=1300545000000 measId=66585 value=1
2011-03-29 11:18:45,950 WARN [Thread-18510] [org.hyperic.hq.measurement.server.session.AvailabilityManagerEJBImpl@899] Avail measurement came in 10 days late, dropping: timestamp=1300544400000 measId=66585 value=1