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.

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

Best setup/practise for clustering remote probes



Your Vote:



We are looking to set up a new instance of PRTG .

What I would like to know, is best practice for failover.

So we envisage setting up the server on vmWare in the data center (i know you recommend physical, but we have some super powerful, top of the range new servers, so that wont be a problem) but where should we put the failover? we have similar kit in the site offices, so it could sit on a server there, but what are the thoughts on putting a server up in azure?

Is using azure any better/worse? We were thinking that the azure server will always be up and ready, should something like the internet connection to the office fail, for example?

azure cluster failover

Created on Jul 13, 2016 3:50:33 PM by  Tech Services (0) 1

1 Reply



Your Vote:



It basically doesn't matter where the failover is located. Four things are important:

  1. Keep the sensor count below 5,000 on the cluster node. Performance will be worse otherwise.
  2. The core and probe must be able to connect to each other
  3. The failover should be as powerful as the core server, since they're monitoring the same things.
  4. Additionally, we recommend VMWare, since PRTG doesn't play as nice with HyperV.

If you keep these things in mind, your PRTG installation should be overall healthy :)

Created on Jul 14, 2016 11:34:07 AM by  Stephan Linke [Paessler Support]

Last change on Jul 14, 2016 11:34:45 AM by  Stephan Linke [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.