We just encountered an issue where our monitoring graphs encountered an 4hr loss of data following a reboot for monthly security patching. Prior to the reboot the data was displaying just fine.

Is there a temporary sensor data cache that we can manually trigger to commit to the database before we reboot? One of 10GigE Bandwidth Sensors had graph data displaying just fine until we rebooted. Post reboot the last 4 hours were missing.

Article Comments

Hello,

this might be just a caching issue, PRTG does save historic much more often (about every 5-15 minutes). Please try the following:

  • Stop both PRTG services (core and probe).
  • Head to your data folder (can be discerned from the Server Administrator tool, under the "Core Server" tab)
  • Delete the "PRTG Graph Data Cache.dat" file
  • Restart the PRTG services
  • Log in to the Web GUI
  • Go to "Setup -> PRTG Status-> System Status" and check the background tasks. It should state that it is calculating historic data

Then,

  • Refresh the page from time to time (is the number being reduced?)
  • Let it run until it is done and then take a look at the historic data of your sensors - it should now be available

It is very important, that the PRTG Core Service has enough time to properly shut down, and finish writing it's Graph Cache File. So it might be better in some cases to shut down the PRTG Services 10-15 minutes before actually rebooting the host server. A few users do this with a batch-script and the net stop and shutdown /r-commands.

best regards


Aug, 2011 - Permalink