Migrate 2.4.8 to 3.2 on new server

[Clifra Jones]

OK, I currently have:

Zabbix 2.4.8 on CentOS 6, zabbix 3.2 apparently is not compatible with CentOS 6.

I have built a CentOS 7 server and want to install Zabbix 3.2 and migrate my data and configuration to it.

Can I:
1. Export the database (MySQL) from 2.4.8.
2. Install 3.2 on new server (do not create database).
3. Modify config files in accordance with old server.
4. Import the 2.4.8 database into MySQL.
5. Start zabbix server 3.2 and have it upgrade the database as if it was an in place upgrade

Is this the best approach for this?

[nick0909]

I am testing a similar upgrade myself. This weekend I create a Zabbix 3.2 VM and imported my 2.4 database. The server upgraded the database on the first run, however it looks like there are some deprecated things that it did not convert. So far I know I have to convert service_state[] items to service.info[], and discovery rules might have to be rewritten.

It is fairly disappointing that the database upgrade could not do more of this automatically, or provide some sort of tool to do it. At the very least have a tool the points out the old data that needs to be manually updated, I am worried I will miss something and it won't alert when I need it to.

[Clifra Jones]

I am testing a similar upgrade myself. This weekend I create a Zabbix 3.2 VM and imported my 2.4 database. The server upgraded the database on the first run, however it looks like there are some deprecated things that it did not convert. So far I know I have to convert service_state[] items to service.info[], and discovery rules might have to be rewritten.

It is fairly disappointing that the database upgrade could not do more of this automatically, or provide some sort of tool to do it. At the very least have a tool the points out the old data that needs to be manually updated, I am worried I will miss something and it won't alert when I need it to.

Yes, I do see that in another post. Disappointing but understandable if a schema change was made.

Makes me wonder if an upgrade is the way to go or just build the new server and migrate over to it gradually. That is what I did when I went from 1.8 to 2.4.

[nick0909]

I don't want to lose my history and all the custom things I have built so I am doing the database upgrade on my new server. I have been looking over my VM with the imported database, so far it looks like the upgrade handles most situations I knew to look for, SNMP OID discovery rules do get translated to the new format and escalations are changed automatically from the old condition to the new checkbox. service_state items are NOT converted, but it seems they still work in the old format for now, so you just have to change them before they kill the old way. I just wish it was clearer in the documentation, my fear is missing something, but I will just have to fix it after testing in production.

[Clifra Jones]

I don't want to lose my history and all the custom things I have built so I am doing the database upgrade on my new server. I have been looking over my VM with the imported database, so far it looks like the upgrade handles most situations I knew to look for, SNMP OID discovery rules do get translated to the new format and escalations are changed automatically from the old condition to the new checkbox. service_state items are NOT converted, but it seems they still work in the old format for now, so you just have to change them before they kill the old way. I just wish it was clearer in the documentation, my fear is missing something, but I will just have to fix it after testing in production.

Well, that is good to know.

I will give it a shot and post my results.

[burn1024]

I did 2.x >3.x upgrade. First migrate to the new server keeping the Zabbix version (2.x), then switch repos and upgrade normally with yum.
Backups, of course.

[Clifra Jones]

I did 2.x >3.x upgrade. First migrate to the new server keeping the Zabbix version (2.x), then switch repos and upgrade normally with yum.
Backups, of course.

Does this do anything different than installing 3.2, importing the 2.x database and allowing 3.x to update the database?

[burn1024]

Yes, it ensures you didn't screw up server migration