In the event that my Zabbix Server catches fire and the hard drives all melt, what exactly do I need to put on a new machine to restore monitoring?
(Assuming I have machines with capacity, the same OS, the same MySQL, the same httpd, the same php, and a copy of the Zabbix tarball with the source as I installed it on the server.)
Is it completely sufficient to save /etc/my.cnf and either a mysqlhotcopy or mysqldump of the zabbix database? Is it necessary to generate a zabbix_server.xml (and how would I do that from a cron job?)?
How does the requirement change in the face of a distributed setup (instructions for the creation of which are still unwritten, alas)?
(Assuming I have machines with capacity, the same OS, the same MySQL, the same httpd, the same php, and a copy of the Zabbix tarball with the source as I installed it on the server.)
Is it completely sufficient to save /etc/my.cnf and either a mysqlhotcopy or mysqldump of the zabbix database? Is it necessary to generate a zabbix_server.xml (and how would I do that from a cron job?)?
How does the requirement change in the face of a distributed setup (instructions for the creation of which are still unwritten, alas)?
Comment