New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


PRTG Cluster: How do I convert a (temporary) Failover Master node to be the Primary Master node?

Votes:

0

Your Vote:

Up

Down

In my PRTG cluster, the server running the master node crashed. One of the failover nodes in the cluster took over the master role.

As my master node server cannot be recovered, how can I make my current failover master node my new primary master node? Can I thus save all settings that I have made to the failover master node in the meantime?

cluster clustering-convert failover-master primary-master prtg

Created on Apr 19, 2012 11:25:02 AM by  Daniel Zobel [Paessler Support]

Last change on May 6, 2019 11:27:49 AM by  Maike Behnsen [Paessler Support]



1 Reply

Accepted Answer

Votes:

0

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 19 or later

If a Primary Master Fails Permanently

If a Primary Master node fails, a failover node becomes Failover Master until the primary master node is back in the cluster again. Sometimes a server crashes and a master node installation cannot be restored.

We recommend that you recover the Master Node from a proper backup.

However, if a master node cannot be recovered, there is a possibility to convert a Failover Master so that it becomes the new Primary Master of a cluster.


Convert a Failover Master Node—Steps to Take

In order to convert a (temporary) Failover Master node to be the new Primary Master node of the cluster, follow the steps below.

Note: This procedure is recommended only in cases where you cannot restore the master node of your cluster. In this article, we assume there are at least two running nodes left in your cluster: The current Failover Master node and another Failover node.

Step 1: Revert Master to Standalone

On the failing Primary Master node (if still accessible):

  • Open the PRTG Administration Tool on the master server.
  • Select the Service Start/Stop tab.
  • Stop the core server service by clicking the Stop Core Server button.
  • Select the Cluster tab.
  • Click the Revert to Standalone... button.
  • Make sure you do not (re-)start the PRTG core server and keep the server stopped permanently. The Standalone setting will prevent the primary master node from re-joining the cluster (and overwriting the new cluster configuration) in case it should "accidentally" be started some time later.

Step 2: Stop Core Servers on Failover Nodes

On all Failover nodes:

  • Open the PRTG Administration Tool on the failover servers.
  • Select the Service Start/Stop tab.
  • Stop the core server service by clicking the Stop Core Server button.

Step 3: Set Failover Master to be the New Master

On the current Failover Master node:

  • Open the PRTG Administration Tool.
  • Select the Cluster tab.
  • Click the Create a PRTG Cluster... button.
  • When asked if you want to "convert this PRTG installation to the master node of a PRTG cluster," confirm with Yes.
  • Follow the procedure to create a new cluster master by confirming cluster port and cluster access key. Leave all settings as they are.
  • Write down the settings for cluster port, cluster access key, and the IP address of the machine that is running the master node, as you will need this information later.
  • Close all windows by clicking the Ok/Save & Close buttons.
  • When asked if you want to (re-)start the core server service, confirm the restart. This node is now your new Primary Master node. If you have made changes to the configuration on the Failover Master node, they will now be saved permanently and deployed to the cluster.

Step 4: Correct the Existing Cluster Configuration

For the new Primary Master node you created in the previous step:

  • Log in to the PRTG web interface and from the main menu, select Setup | System Administration | Cluster.
  • In the Cluster Node Setup, copy the data (the "Node Name") of the Primary Master node to line number 1 and clear the IP if necessary. "Node ID" is updated automatically, please check if it is correct.
  • Delete the entries in all other lines (lines 2-5).

Step 5: Re-Join Failover Nodes

On all Failover nodes:

  • Open the PRTG Administration Tool.
  • Select the Cluster tab.
  • Click on the Join a PRTG Cluster… button.
  • Follow the procedure to create a new Failover node and use the information you wrote down earlier: Insert the IP address of the new Primary Master node, the cluster port, as well as the correct cluster access key.
  • Close all windows by clicking the Ok/Save & Close buttons.
  • When asked if you want to (re-)start the core server service, confirm the restart. This node is now a Failover node. It will connect to the new Primary Master node and receive its configuration. Repeat the procedure in this step for each of your failover nodes.

Step 6: Clean Up on the New Primary Master Node

On your new Primary Master node, hardware device specific sensors on the Local Probe device may not work anymore. For example, the sensor for the network card adapter may show a Network card not found message, because the hardware has changed. In this case, please delete the affected sensors and add them again.

More

I need help with my PRTG cluster configuration. Where do I find step-by-step instructions?

See Also

Created on Apr 19, 2012 11:26:20 AM by  Daniel Zobel [Paessler Support]

Last change on May 13, 2019 5:19:02 AM by  Maike Behnsen [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.