<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: System Administration—Administrative Tools

Create Configuration Snapshot

Create a snapshot of your PRTG configuration. This action can take up to 100 seconds. Once finished, you will find a ZIP file that contains a *.dat file in the Configuration Auto-Backups subfolder of your PRTG data directory. If you run a PRTG cluster, this action is executed on the cluster node you are currently logged in to. The ZIP file follows the name pattern PRTG Configuration (Snapshot YYYY-MM-DD HH-MM-SS).zip.

This option is not available in PRTG on demand.

Write Core Status File

Create status files of your PRTG core server. You will find the two text files in the Logs (System) sub folder of your PRTG data directory. If you run a PRTG cluster, this action is executed on the cluster node you are currently logged in to. The files are named Core Status.txt and Core Memory.txt. They are overwritten each time you click this button.

This option is not available in PRTG on demand.

Clear Caches

PRTG caches tiles for Geo Maps and user data for Active Directory Integration. Use this button to delete the cache if you encounter broken Geo Maps tiles, or if you changed a user's password in the Active Directory.

This option is not available in PRTG on demand.

Load Lookups

(Re)load the lookup files from the \lookups\custom folder. In this folder your customized lookup files are stored. If you have created a new lookup file or changed something in an existing lookup file, it might be necessary to load or to reload these files.

This option is not available in PRTG on demand.

Recalculate PRTG Graph Data Cache

PRTG constantly writes monitoring data to disk and keeps the graphs for your graph tabs in memory. If PRTG is ended unexpectedly, the graph cache may get corrupted. In this case, graphs may be shown empty or show wrong data.

If you experience graph display problems, a graph recalculation will fix the problem. Click Go! to delete the data cache file and recalculate it automatically.

If you apply recalculation, PRTG needs to restart the core server. Because of this, all users of the PRTG web interface, of the Enterprise Console, or of Smartphone Apps will be disconnected. After clicking the Go! button, a dialog window will appear which asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen.

Directly after this action your graphs will be empty. They will be re-filled successively while recalculation in the background progresses. Until recalculation is finished, performance of the PRTG web interface may be affected due to high disk I/O activity.

Restart Core Server

Restart the PRTG core server service manually. Click the Go! button for this purpose.

If you restart the core server, all users of the PRTG web interface, of the Enterprise Console, or of Smartphone Apps will be disconnected. After clicking the Go! button, a dialog window will appear which asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen.

If you want to schedule an automatic restart of Windows services for both core server and probe service, you can do this in the corresponding Probe Settings.

This option is not available in PRTG on demand.

Write Probe Status Files

Create status files of your PRTG probes. PRTG writes status files for the local probe running on the PRTG core server (if you run a PRTG cluster, on the cluster node you are currently logged in to) as well as for all remote probes configured (if any).

On the respective systems, you will find four text files in the Logs (System) sub folder of the PRTG data directories. The files follow the name pattern Probe Memory XX.txt, ProbeState XX.txt, ProbeState AXX.txt, and ProbeState BXX.txt. They are overwritten each time you click this button.

Restart All Probes

Restart all PRTG probes as well as the local probe Windows service. If there are any remote probes configured, the probe Windows services on the respective remote systems will be restarted as well. To restart single probes only, please see below.

Disconnected probes cannot be restarted here. Please use the PRTG Administration Tool on the probe system to start a disconnected probe.

If you run a PRTG cluster, this action is executed on the cluster node you are currently logged in to. In this case, remote probes are only restarted if you are logged in to the primary master node. The cluster probe Windows service of failover nodes is not restarted if you execute this action on the master node. If you want to restart the cluster probe Windows service of a failover node, please log in to this failover node's web interface and click the Go! button there.

Probe [#Number] "[Name]"

This section shows information about the connection status. If the probe is currently connected, the field shows the source IP address and port number used by the probe. For the Local Probe, the IP will always be 127.0.0.1. You will also see information about the date when the last data packet was received from the probe.

If you want to restart a single probe, click the corresponding Restart Probe button. Entries for every single probe are following.

Disconnected probes cannot be restarted here. Please use the PRTG Administration Tool on the probe system to start a disconnected probe.

This option is not available for local probes in PRTG on demand.