Hello community,
i would to know if there's a more elegant solution to my concept and am open to any suggestions:
Currently i have 2 Zabbix Servers running on 2 ESXI, one active and one cold standby due to limitations on the monitored devices.
To synchronize between these 2 Servers, i would SQL dump the active server DB, transfer it on a regular base to the other server and reimport it to the system.
And vice versa, in case that the passive system is taking over. I know that the DB size can be quite big and will certainly take time to be dumped and transfered through
the internal Network.
So i would to ask again, is there any better solution available except high availability? On high availability i would have to make sure that the DB has to be somewhat on
a HA system as well and i only have 2 phyical servers. OR am i missing the concept of High availability? In case if I use High availability, do those 2 Servers still have their own respective DB or are these 2 servers pointing to that single DB?
Thanks !
i would to know if there's a more elegant solution to my concept and am open to any suggestions:
Currently i have 2 Zabbix Servers running on 2 ESXI, one active and one cold standby due to limitations on the monitored devices.
To synchronize between these 2 Servers, i would SQL dump the active server DB, transfer it on a regular base to the other server and reimport it to the system.
And vice versa, in case that the passive system is taking over. I know that the DB size can be quite big and will certainly take time to be dumped and transfered through
the internal Network.
So i would to ask again, is there any better solution available except high availability? On high availability i would have to make sure that the DB has to be somewhat on
a HA system as well and i only have 2 phyical servers. OR am i missing the concept of High availability? In case if I use High availability, do those 2 Servers still have their own respective DB or are these 2 servers pointing to that single DB?
Thanks !