Dear Benjamin,
this is actually a bit tricky. You can install a new master on a new PC/Server and then move the configuration from the old master node, but this will unfortunately create a "GID-Conflict", because the new master has a different GID (the GID is created during the setup-process) as the old one (which is stored in the configuration file). So once the new master is running, you need to take the following actions:
- Stop the PRTG Server Service with the PRTG Administration Tool
- Once the Service is stopped, please close the Server Admin Tool
- Open the PRTG Configuration File, and search for <optionnode id="810">
(in previous versions: "<optionnode id="805">")
- Copy the GID that comes in the tag <cell row="0" col="1"> under this node
- Open the registry and go to:
(64bit) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor\Server\Core
(32bit) HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor\Server\Core
- There open the value "ClusterGid" and paste in the value copied from the config file. It has a format like this: {AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE}
- Save this, and restart the PRTG Server Service
That should take care of the GID conflict. To convert the old master then to failover is simple, just switch the cluster mode to failover and "join the new cluster".
best regards.
Add comment