I want to back up my PRTG data and configuration. How can I do it?
This article applies to PRTG Network Monitor 19 or later
Back up PRTG Data
PRTG Network Monitor writes data to several locations:
- The program directory (core installation)
- The data folder (monitoring configuration, monitoring data, logs, etc.)
- The registry (license key, admin login, IP settings, etc.)
For more information on where PRTG stores its data, see How and where does PRTG store its data?
Quick Backup of Configuration Files
For a quick backup of only the monitoring configuration (for example, groups, devices, sensors, users, maps, reports), back up the file PRTG Configuration.dat in the data folder.
It is also a good idea to back up older configurations in the folder \Configuration Auto-Backups.
These files are not kept open while the PRTG core server is running and can be backed up at any time.
Backing Up All Data Stored in the File System
For documentation on the various other files and folders where PRTG stores its data, see How and where does PRTG store its data?. Then select the data that you want to back up.
To get a complete and consistent backup of the databases (for example, log database, monitoring database, Toplist database, Ticket database), stop the PRTG core server while running the actual backup process.
Note: Probes will continue to monitor their sensors for a few minutes and deliver monitoring results to the PRTG core server as soon as it is back online, but alerting will not be available during this period.
Our tip: Most important are the folder Monitoring Database and the file PRTG Configuration.dat, other files and folders can usually be left out of your backup process.
I would like to share a tip in regards to backing up configuration:
We use an application called Karen's Replicator which syncs directories.
There is a (virtual host) server which is a cold backup for the active prtg server. The relevant directories are scheduled to sync from the active server to the cold backup one every 1 hour.
This way the cold server is ready to be activated at any time, with minimum data loss.
@IB: Thanks for sharing! Edited your post to add the link to the software.
I got a question regarding the backup of the PRTG Data.
Once the configurations have been saved (groups, devices, sensors...), can they be copied to a second device with another installation of PRTG so that they can be imported from the second PRTG Core? (I am not interested in Clustering)
Yes, that is possible. This would basically require the same steps as migrating an installation. Please refer to How can I move (migrate) my PRTG installation to another computer?
C:\ProgramData\Paessler\PRTG Network Monitor\Monitoring Database contains GBs of data.
Do we need to take full backup dump of this huge folder as well ?
Raviray, this folder contains the historic sensor data. If you want to create reports, you need this and its contents. So I would recommend to include it in a backup.
As Raviraj says, the Monitoring Database contains GBs of data (in my case, we have a 2-node PRTG-Cluster with about 5600 sensors - after about 4 Weeks it is nearly 19GB), but I backuped that folder by copying it to another location and after that compressed it with 7-Zip (7z, Ultra, LZMA, 64MB, 64, 4GB, 2 CPU-Threads) - it took about 90 mins, but gave me a backup-file with just 976 MB.
Hello, I recently installed a few remote probe servers. Do I need to take a backup of this servers, too? Or is everything important on the local probe server?
Thank you! Michael
Remote Probes actually do not carry any configuration data (apart from the connection settings to the core server) or data files. So usually it is not necessary to include them in backups.
"Please note that the probes will continue to monitor their sensors for a few minutes and will deliver monitoring results to the core as soon as it is back online"
Could you be more specific on "few minutes" please?
A Remote Probe stores a maximum of 500,000 sensor results in RAM memory. See also section "How Probes work" here.
Hello all, I'm working on a concept for a active / passive cluter for a PRTG environment with >7000 sensors. I'm copying all Data from the Database folder (excluding Report PDFs, Logs and Autobackup configurations) and everything important from PRTG DIR (webroot, snmplibs, lookups, notifications, devicetemplates and Custom Sensors). For an automated failover I need to move the license to the 2nd Standby Core Server and tell the remote probes to connect to another Core Server. Is there a way to do this via script?
That is a nice idea, however PRTG only supports an active/active cluster solution. I myself already thought a script based solution for the cluster but after talking to our developers I figured out that this is not possible, I'm afraid.
If you want to built up a PRTG cluster, please stick to our manual guide.
Everything else is not supported, sorry to say.
Hi Sebastian, thanks for your reply. Unfortunatelly the cluster is not favored by the customer and we estimate a sensor count of >8000. So there is no way to update the core-server entry via API on the remote probes?
No, because the relevant information are stored in the Windows Registry of the host system as well, I'm sorry.
what files are needed to migrate to another pc when only want monitoring data only? and can it be when migrating the file the core server is still running?
About PRTG Configuration.dat in the data folder \Configuration Auto-Backups. If i use cluster mode with two nodes every node has it's own PRTG Configuration.dat file? Or Master Node has backup for both nodes? If i need to restore this config to cluster if it's fail, first i need to restore both nodes cfg and then make a cluster, or this backup has cluster info inside?
The master node is the primary cluster node. Every setting will be changed within the configuration file of the master node and the configuration will be automatically synchronized with the failover nodes.
To restore a failover node please set-up a new client that should be the future failover node and proceed the regular step by step guide to whoop this machine into the PRTG cluster. The configuration file will be automatically pushed to it.
If you still own the /Monitoring Database directory of the old failover node, you can also restore it on the new failover node to restore the historic data.
"please stop the PRTG core server while running the actual backup process." - this must be done from Windows Services MMC? Or from inside PRTG web-interface? Maybe script is the best way?
It does not really matter where you stop the services. You can either stop the services from the Service Start/Stop tab within the PRTG Administration Tool on the PRTG Core Server or you can stop them via Windows Services MMC.
The second option would allow you to stop the services using a script, but this is not mandatory.
Good, but what if i use "Veritas Backup exec" and make Full Backup of all Master Node Server include System State and all other server content, need i stop this service? As far as i understand Veritas can backup all content without service interruption. Can be some trouble with server restore after this?
I'm not familiar with Veritas Backup, so this question can't be answered.
I assume it's possible, but I'd recommend to test a Veritas Backup before relying on it.