This article applies to PRTG Network Monitor 13 or later

Converting a PRTG Cluster to Standalone Installations

Please follow the steps below in order to split a PRTG cluster with one master node and one failover node to get two standalone PRTG servers. Afterwards, historical monitoring data will still be visible on both nodes.

For this purpose, you have to convert the failover node to a current master node (with a new license) and move groups and devices to the local probe on both systems to keep monitoring data.

Step 1: Stop Core Server on Current Master Node

1. On the server that runs the master node, open the PRTG Administration Tool.
2. Select the Service Start/Stop tab.
3. Stop Core Server by clicking the corresponding button.
4. The failover node will become the current master then.
5. Make a backup copy of the PRTG configuration file additionally.

Step 2: Stop Core Server on Failover Node

1. On the server that runs the failover node, check if PRTG’s web interface denotes that this server is the current master node now.
2. Open the PRTG Administration Tool.
3. Select the Service Start/Stop tab.
4. Stop Core Server by clicking the corresponding button.
5. Make a backup of the PRTG configuration file additionally.

Step 3: Set Failover Node to Master Node

1. Still on the server with the failover node, select the Cluster tab in the PRTG Administration Tool.
2. Click on the Create a PRTG Cluster… button.
3. In the appearing dialog box you get a notice that you are going to convert this PRTG installation to the master node of a PRTG cluster. Confirm with Yes to proceed.
4. The Create a PRTG Cluster Master window appears. Leave Cluster Port and Cluster Access Key unchanged and click on OK. This is necessary to keep the data from the cluster node visible when restarting PRTG on this node.
5. Close the PRTG Administration Tool.
6. Confirm the question Restart now? with Yes.

This PRTG node is now a new master node.

Step 4: Move Devices on the New Master Node to Local Probe

1. Open the PRTG web interface on the new master node.
2. Move all groups and devices from the Cluster Probe to the Local Probe.
   • For example, open the Management tab on Root group and Drag&Drop the cluster probe objects to the local probe.

Step 5: Revert the New Master Node to a Standalone Installation and Replace License

1. Still on the new master node server, open again the PRTG Administration Tool.
2. Select the Service Start/Stop tab.
3. Stop Core Server by clicking the corresponding button.
4. Select the Cluster tab.
5. Click on Revert to Standalone…
6. In the appearing dialog box, you get a notice that you are going to revert this PRTG cluster node to a standalone installation. Confirm with Yes to proceed.
7. Select the License tab.
8. Enter your new license key.
9. Keep the PRTG Administration Tool open and the PRTG core server stopped.

Step 6: Move Devices on the Old Master Node to Local Probe

1. On the previous master node server, open the PRTG Administration Tool.
2. Select the Service Start/Stop tab.
3. Start Core Server by clicking the corresponding button.
4. Open the PRTG web interface on this server.
5. Move all groups and devices from the Cluster Probe to the Local Probe.
   • For example, open the Management tab on Root group and Drag&Drop the cluster probe objects to the local probe.

Step 7: Revert the Old Master Node to a Standalone Installation

1. Again in the PRTG Administration Tool on the previous (old) master node server, select the Service Start/Stop tab.
2. Stop Core Server by clicking the corresponding button.
3. Select the Cluster tab.
4. Click on Revert to Standalone…
5. In the appearing dialog box, you get a notice that you are going to revert this PRTG cluster node to a standalone installation. Confirm with Yes to proceed.

Step 8: Restart Both PRTG Servers

1. On both servers, click on Ok in the respective PRTG Administration Tool.
2. When asked if you want to start the core server service, confirm with Yes.

Done

Both PRTG servers will now run independently in standalone mode. The historic data will still be accessible on both servers.