Hi Team,
I understand this question has been asked before over the past 5 years, however I know that things have significantly changed since then too. We're an MSP who is just about to begin a very large multi-tenanted deployment of PRTG.
Currently we have a production platform that we've been running for a few months and has all of the devices and data deployed already. There is two other installations that other staff members have setup, and are wanting to merge their data.
To my understanding the main issue with merging data is due to the sensor numbering sequence, thus having conflicts if merged. If this is the case is it possible to change the numbering sequence of the data for example to add an additional 1 in front of a sensor. Eg 202 becoming 1202 etc.
If necessary we will start again, it would just be unfortunate to throw away the hundreds of hours of development and deployment time.
If there is any other way around this please let us know.
Cheers,
Dear Nick
Configuration merging is not supported. This would be a complex operation as some objects are unique per core server and cannot be simply merged. Other difficulties are libraries, which pose new complex issues, as well as notifications. It is likely that both installations have some very similar notifications which would lead to redundant notifications on the merged configuration.
The main issue however is the aforementioned unique object handling.
Please create device template from the existing devices and re-create the sensors on one of the servers which you intend to use as new core server.
Nov, 2015 - Permalink