[2.0.10] How to break the distributed architecture model safely?

[paszczak000]

Hi, guys,

Right now I'm running Zabbix 2.0.10 in distributed monitoring (2 nodes).

Details:
Number of hosts: 177
Number of items: 12239
Number of triggers: 5109
Number of users (online): 45
Required server performance, new values per second: 392.14

I'm thinking about change distributed architecture to proxy and upgrade Zabbix to 2.2.x

How to do this safely to ensure that no data/configuration is lost or gets corrupted?

Thanks in advance

[johansen]

very interested in this as well!

[Linwood]

I am VERY new to zabbix and have been experimenting with distributed monitoring in this area, so this may be completely off base, but...

If you have kept your templates and related items in synch between the nodes, who about exporting all hosts on the secondary node to XML, editing the XML to add the proxy monitoring section (simple search/replace), and import on the main node (pushing it to the proxy which I am guessing is active).

If you need whole different configurations (e.g. templates) it's harder of course, but it still may be easiest to do by changing the xml files.

Of course buried somewhere yet unseen there may be some automated migration tool.... ?

[paszczak000]

Hi guys,

I was thinking about stoping slave node and changing IDs of hosts in master server database. But I'm afraid about constraints.

I don't want to lose hosts history from slave nodes.

[paszczak000]

I have remove all hosts from SLAVE node and add once again into MASTER.

So right now Zabbix is wroking in DM but with one node.

When you # NodeID in conifg file and restart zabbix_server it won't work.

[LenR]

I think you can run fine with a nodeid, one master and multiple proxies. Your master will show it's in DM, but it really won't be doing anything other than using the nodeid.

I don't think there is a way provided to get back to nodeid = 0