I have noticed that sometimes when I make changes, 20-30 minutes pass and they are not updated on failover node. How long does it take?
Article Comments
Hello,
Which version of PRTG are you using at the moment? We enhanced the synchronization within the last version, because it could get off sync in some cases.
This depends on multiple factors and cannot be generalized. The Master server will send small configuration changes immediately. Some greater changes to the configuration file will require a synchronization of the complete configuration file. This might for example occur if you change an object with many dependencies, especially in large installations. This mechanism will ensure that the synchronized data will always be consistent.
As the configuration file might become large depending on the number of objects, this might require some additional time - 20 to 30 minutes is indeed a long time here.
Best regards
Jun, 2015 - Permalink
Currently Installed Version 15.2.17.2804
Any way to have updates pushed immediately? Could I copy configuration file or would that screw up my cluster setup?
Jun, 2015 - Permalink
Hi,
Version 15.2.17.2804 already contains the synchronization improvements. I would advice against copying the configuration file manually. The configuration file can easily get corrupted if the Fail Over Node writes down the changes in the meanwhile. I'm afraid that depending on the configuration file size, changes might take some time to synchronize.
Best regards
Jun, 2015 - Permalink
Hello,
Which version of PRTG are you using at the moment? We enhanced the synchronization within the last version, because it could get off sync in some cases.
This depends on multiple factors and cannot be generalized. The Master server will send small configuration changes immediately. Some greater changes to the configuration file will require a synchronization of the complete configuration file. This might for example occur if you change an object with many dependencies, especially in large installations. This mechanism will ensure that the synchronized data will always be consistent.
As the configuration file might become large depending on the number of objects, this might require some additional time - 20 to 30 minutes is indeed a long time here.
Best regards
Jun, 2015 - Permalink