Hello there,
We presently outsource our PRTG implementation but the remote probe for our company is on-premise and under our control. If I stood up a new PRTG core, is there a way to "repoint" our remote probe to that new core server and have it maintain the devices and sensors? We have over 2500 and don't want to have to add them back. We could live with losing the history. Thanks.
Article Comments
My issue is that I have no access to the current core server as it is managed by the service provider and they won't give us the configuration as it's multi-tenant with other customers. So it appears this will be a manual migration.
Dec, 2016 - Permalink
Ok, I see, in this case the service provider also has his own already existing configuration file and the culprit here is that you cannot merge one config into another one (neither fully nor partially). So in this case I'm afraid the only option is to add the devices newly from scratch with their sensors as soon as the remote probe is connected and you get access to that part of the device tree (or the service provider needs to do this then).
Dec, 2016 - Permalink
Hello Kyle,
The thing is that remote probes store no sensor data or further configuration details (besides how to connect to the core server), because that is all stored on the core server.
So if you migrate the core server to a different machine and keep all the settings (e.g. by following this guide), all you need to do is configuring the new hostname/IP of the PRTG server in the Remote Probe's administration tool.
See also: How PRTG Network Monitor Stores its Data
Kind regards,
Erhard
Dec, 2016 - Permalink