Large PRTG Database

Dear zuperzuze,

you can move the entire data folder (including the historic data, logs, and PRTG configuration file). It is not possible to move only the last x days.

In principle you could migrate the data to a PRTG freeware. While limited to 100 active sensors, it is still possible to create reports for paused sensors. However managing this solution is not trivial.

But PRTG is usually fine with a local harddisk, an SSD should not be necessary. So you can move the complete data folder to a large and cheap disk.

Arne, thanks for the answer.

So, if I keep the Database folder on regular disks and the rest of the installation paths on SSD I would still have good performance? I mean, what are the "hottest" part of the software? Which folders should I keep on SSDs?

Dear zuperzuze,

you can have the installation on one drive and the whole data/log/configuration on another. But you cannot put only some of the data-patch-folders elsewhere.

In many cases, PRTG does not benefit a lot from using an SSD, neither for the installation folder, nor of the data folder. This is because PRTG was conceived at a time where there were no SSDs. Because harddisks are still much more affordable, we also try to maintain the PRTG architecture that an SSD does not become necessary.

It is however important in order to get good performance, to use a drive locally in the server (no network-attached solution.)

An SSD of course does not hurt, but with a typical PRTG setup in mind, our tests show that performance gains are usually not very big. In some cases, reports are generated faster, but unless you create a lot of large reports very often, the practical gain is not that big. Most of the times, reports run in the background as a scheduled task in PRTG, so the performance does not play a very large roll.