Zabbix mirroning

[hiad]

Good morning

About Zabbix, im new working with that. I have a client who want Zabbix installing in two servers. We have AWS and now i have Zabbix installed and working in a server in Carolina and Oregon. But, i going to share what client said: "He mentioned he would like to have a mirrored environment of Zabbix - on a separate server on west coast or central".

Can you help me please, mirroning the server? I can't find that in the Documentation.

[kloczek]

If this client wants to have DR all what you need is set up slave zabbix DB in second location with possibility to promote this slave as new master and add on top of this zabbix server and proxies connected to the same set of agents. All this swapping must be done with hostnames or IPs preservations/migrations.
In other scenario where each agent is connected to duplicated set of proxies and second server it will mean that any monitoring change done in one monitoring stack must be manually replayed in second one as well.
In other words what is this client is asking to do is very hard to maintain or impossible to implement to have really 100% mirrored zabbix monitoring.
Base technique used on adding HA to zabbix is active/standby clustering and your client must understand that he is asking to do/implement very stupid/unwise things .. as consequence lack of understanding how zabbix is working.

[hiad]

Sorry about that, but i'm new config Zabbix services. Can you explain me how to do :

"what you need is set up slave zabbix DB in second location with possibility to promote this slave as new master and add on top of this zabbix server and proxies connected to the same set of agents. All this swapping must be done with hostnames or IPs preservations/migrations."

[hiad]

Hello, Can you explain me how to do

If this client wants to have DR all what you need is set up slave zabbix DB in second location with possibility to promote this slave as new master and add on top of this zabbix server and proxies connected to the same set of agents. All this swapping must be done with hostnames or IPs preservations/migrations.

[peatb]

Zabbix itself has no concept of mirroring or master-master/master-slave setup. So what you could do is setup a mirror of the database underneath zabbix. Then install zabbix server on both locations, but only have it running in one.

When you need to failover to the other location you have to stop zabbix on one side and start it on the other. You need to make sure that all zabbix proxies and zabbix agents start connecting to the new location as well, so that may mean reconfiguring them all. Or, the IP of the zabbix server must be moved to the new location as well.

[guzzijason]

Zabbix itself has no concept of mirroring or master-master/master-slave setup. So what you could do is setup a mirror of the database underneath zabbix. Then install zabbix server on both locations, but only have it running in one.

When you need to failover to the other location you have to stop zabbix on one side and start it on the other. You need to make sure that all zabbix proxies and zabbix agents start connecting to the new location as well, so that may mean reconfiguring them all. Or, the IP of the zabbix server must be moved to the new location as well.

This is basically what I did, using a MariaDB/galera cluster. I set my proxies to be passive, so they're not trying to connect back to the server - they simply accept connections from whichever server happens to be active. So far, seems to work fine.

It is important in this setup that you *only* have one active server at a time. As others have said, zabbix doesn't have server clustering logic built-in, so you need to be careful - it's not supported, and easy to run into problems.

__Jason