Situation: We replaced our PRTG-core (hardware to virtual mashine) knowing, that our probes would cache their data during the time, we need for the change. After the replacement the probes began to unload their data to the core. During that period, the probes began to update themselves, cancelled sending data to the core and threw the cached data.

What was our mistake? What's best practice for this project?

Article Comments

Hey ages,

did you use the same version on old and new core-server? If not, this is a normal case. probe-server has to be on the same patch level as there core. So if the versions are not the same, they will update next to the server change.

I don't know the best practise from Paessler, but i would look for the following points.

  • Patch-Level: should be the same on all server
  • Network: connection to all probes should be possible
    • Maybe I should use the same subnet
  • Time: this work shouldn't do 10 min till "beer o'clock ;)
  • Reboots: miss reboots till the data is send to the new core

This are my own points of interest by merging the data to a new core server.

Maybe this is an answer to you. If not, request again, maybe a support from Paessler answers then with there best practise.

Best

Sascha


Nov, 2014 - Permalink

Hello,

the "mistake" was the difference in versions here. That caused the Probes to run the automatic probe update, which means the cached data is flushed.
In such a scenario you want to avoid a restart of the Probes (services). That also means the new Core Server should run under the IP/Hostname of the old Core. Otherwise you will need to change the connection settings on the Remote Probes, which flushes the cached data on the Probes.

best regards.


Nov, 2014 - Permalink