Our current infrastructure is pretty simple, just a single Zabbix server monitoring a bunch of servers.
We are moving to a distributed setup, with the Zabbix server in AWS, and a proxy in our data center.
The old zabbix server is running 3.4.1, the new server is running 4.0
The database on all systems is Postgres
There is a pg_dump of the database every night around 11PM.
All the clients have been configured to talk to all the zabbix servers & proxies
I've set the proxy to hold the data for 24 hours. What I want to do is to be able to load the backup into the new server, let the zabbix-server update the database and then manually change all the servers to use the proxy.
I figured I'd do this 2 times, so that the proxy would know about all the servers and store their data. I've gone through this cycle 2x, and so far, haven't been able to have the new zabbix server be able to pull in all the data from the proxy for the time period between when the backup was done and the new Zabbix server being started.
Any suggestions?
We are moving to a distributed setup, with the Zabbix server in AWS, and a proxy in our data center.
The old zabbix server is running 3.4.1, the new server is running 4.0
The database on all systems is Postgres
There is a pg_dump of the database every night around 11PM.
All the clients have been configured to talk to all the zabbix servers & proxies
I've set the proxy to hold the data for 24 hours. What I want to do is to be able to load the backup into the new server, let the zabbix-server update the database and then manually change all the servers to use the proxy.
I figured I'd do this 2 times, so that the proxy would know about all the servers and store their data. I've gone through this cycle 2x, and so far, haven't been able to have the new zabbix server be able to pull in all the data from the proxy for the time period between when the backup was done and the new Zabbix server being started.
Any suggestions?