Modifying the Windows registry, you can disable the automatic conversion to the new database format which is performed on first startup of PRTG 8.2. Using this option, historic data will not be available.
However, you can disable data conversion in order to avoid downtime during first startup, or to avoid background conversion of Toplists after startup. Can I Revert to Old Method?ĭue to the great advantages the new storage method brings, we will not support the old storage method in future. PRTG will automatically back up the data files in the old format and delete them after 70 days. In our labs conversion takes about 1 minute per 50 MB of the Toplist Database folder's total size. While converting on slow systems, you might notice that some of your current Toplists are missing, as conversion is given priority in case your server running PRTG cannot provide sufficient performance. The conversion process for existing Toplist databases is different: After startup, PRTG will start converting your Toplist databases in the background, so after a while all historic Toplist databases will be visible in the sensors' Toplists tab. However, this is only needed once, at first startup after updating. To give you a number, according to measurements in our labs, the import process takes about 1 minute per 10-50 MB of file size of Log Database.db (similar for ToDo Database.db). Depending on the size of the Log and ToDo database, this may take some time for the import. Automatic Converting May Take a WhileĪfter upgrading to version 8.2 or higher, during first core server service start up, PRTG will convert your existing data into the new database format. This is a major breakthrough! You will be amazed at how fast log data is displayed in the web interface when browsing through the logs of the system (main menu item Logs) or when viewing logs of a single monitoring object. Furthermore, the writing speed is not affected by the size of the database at all you can now store a whole year of log data without affecting the performance-regardless of the size of your installation! The new engine is up to 300 times faster when writing data and up to 100 times faster when reading data. This leads to a massive performance boost, especially for large installations that make massive use of Toplists, or where log files are viewed frequently in the web interface. As of PRTG version 8.2, the data format for log entries, Toplists, and ToDos is further improved. The old system (based on SQLite) was sufficient for small to medium installations, but for installations with thousands of sensors it could cause performance bottlenecks. PRTG uses its own database format to store monitoring data and other data, to ensure data access is as performant as possible. This article applies to PRTG Network Monitor 8.2 or later Introducing a New Database Format with PRTG 8.2
0 kommentar(er)
