New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Avoid data loss in case of update or replacement

Votes:

0

Your Vote:

Up

Down

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?

data-loss prtg remote-probe

Created on Nov 27, 2014 8:05:35 AM by  ages (1,007) 5 1



2 Replies

Votes:

0

Your Vote:

Up

Down

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

Created on Nov 27, 2014 12:49:27 PM by  Sascha Lewandowski (2,291) 3 4



Votes:

0

Your Vote:

Up

Down

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.

Created on Nov 27, 2014 1:20:02 PM by  Torsten Lindner [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.