Dear Zabbix Users,
we are planning a major upgrade from 4.0 to 6.0.
Current system is CentOS7 with PostgreSQL 12, no custom partitioning or any other scripts, 16 proxies, database size is about 350 GB, the pg_dumpall file compressed is 20 GB.
Target system should be RHEL8 with php7, PostgreSQL14 which I have in prepared before the upgrade. I.e. I have installed the RHEL8, php7 and Zabbix6 on a fresh system.
The following procedure is what I think up about after I read through the upgrade documentation:
1) disable all trigger actions
2) disable all hosts that are monitored by proxies
3) stop all proxies
4) stop zabbix-server and frontend
5) do a pg_dumpall (ascii format)
6) copy the dump file over to the new Zabbix server system and import it into the PostgreSQL 14 database
7) At this point I am not sure how to proceed. I would like to take advantage of the improved performance by using primary keys in Zabbix 6.0. So should I continue with the primary key script now? On the other hand there is this blog post (https://blog.zabbix.com/a-guide-to-m...ne-2021/18569/) which does not recommend doing the primary key change „when upgrading an existing instance“.
8) Apply the double.sql script on the database
9) then timescale or better wait with that and do that some time later?
10) start zabbix-server on the new system and watch it converting the database in the log
11) start the frontend
12) check if everything works so far, then take over the ip address and name of the old system, do a reboot
13) upgrade proxies and start them
14) enable hosts
15) enable trigger actions
Thank you for your thoughts and recommendations
Cheers
Timo
we are planning a major upgrade from 4.0 to 6.0.
Current system is CentOS7 with PostgreSQL 12, no custom partitioning or any other scripts, 16 proxies, database size is about 350 GB, the pg_dumpall file compressed is 20 GB.
Target system should be RHEL8 with php7, PostgreSQL14 which I have in prepared before the upgrade. I.e. I have installed the RHEL8, php7 and Zabbix6 on a fresh system.
The following procedure is what I think up about after I read through the upgrade documentation:
1) disable all trigger actions
2) disable all hosts that are monitored by proxies
3) stop all proxies
4) stop zabbix-server and frontend
5) do a pg_dumpall (ascii format)
6) copy the dump file over to the new Zabbix server system and import it into the PostgreSQL 14 database
7) At this point I am not sure how to proceed. I would like to take advantage of the improved performance by using primary keys in Zabbix 6.0. So should I continue with the primary key script now? On the other hand there is this blog post (https://blog.zabbix.com/a-guide-to-m...ne-2021/18569/) which does not recommend doing the primary key change „when upgrading an existing instance“.
8) Apply the double.sql script on the database
9) then timescale or better wait with that and do that some time later?
10) start zabbix-server on the new system and watch it converting the database in the log
11) start the frontend
12) check if everything works so far, then take over the ip address and name of the old system, do a reboot
13) upgrade proxies and start them
14) enable hosts
15) enable trigger actions
Thank you for your thoughts and recommendations
Cheers
Timo
Comment