Convert a Zabbix Node to a Zabbix proxy

[aink999]

Is there an easy way to convert a Zabbix node into Zabbix proxy ?

I find Zabbix proxy more easy to manage.

[trikke76]

i dont think u can convert it back

but u could install a proxy and then just move your hosts to the proxy from your node as nodes and proxies can work in the same environment together

[Alberto]

replace a child node whith a proxy

Hi Aink999,

I want to replace a child node for a proxy. Have you try it?

I have hundreds of host/configurations, maps, etc.. on child node. Is easy to export/migrate them to the master node?

I will be gratefult for your recomendations.

Thanks.
Alberto.

[andrea.consadori]

hi, i try it before but i notice that in node the object has a starting id depending on the node so if you make an export and reimport you have object with wrong id in your proxy.

i see that in upcoming zabbix 2.4 node will be removed so i think that there will be some mysql operation to revert node to standalone, so once in standalone maybe you could export hosts in your main server, remove zabbix server, cleanup mysql and install zabbix proxy.

[Wolfgang]

Hello,

It is not possible to convert a node into a proxy.

It is of cause possible to simply add a proxy and reconfigure the hosts on the node in question to be monitored through that proxy.

On top of it, you could also try changing the node based setup into a standalone server setup - however doing so would keep the entire node based id scheme.

It is also possible to convert a node based setup into a standalone server. This would result in a very clean and consistant zabbix database, but requires a good amount of develpoment work and a _very_ detailed understanding of the zabbix database architecture and how all works together.

I have done this a couple of times for smaller and bigger installations. (Upto 6000+ Hosts with 370.000+ Items, 90.000+ Trigger with 6+ nodes).
Basically you need to touch all tables from the node based database and create a new standalone database with _complete_ new ids for any zabbix objects (so not only hosts and items but also graphs. graphs items, screens, trigger, trigger definitions, history data, events, alerts, user etc.). So you will have to convert ids from the src database to your new destination database.

For some of our customers it paid off to go that route because the node based database also had inconsistancies that we repaired when doing that transition and they wanted to keep the _entire_ configuration, user, historical data, trends, escalations etc.

Regards

Wolfgang