Hosts, templates, triggers migration from Zabbix 6 to 7

[n3r0]

Hi,

We use Zabbix 6 in our data center.

As You understand, a lot of hosts, templates etc are currently added.

For now we planned migration to new version.

I have configured new separate Zabbix Server and Database.

Is there any suggestions or maybe best practises to export/import hosts, templates, triggers migration from Zabbix 6 to 7?

Thank You in advance!

[NgRox]

Hi!

I recommend performing a dump of the database and uploading it to the new environment... if it's for a different database, check if there's a dump converter.

If that's still not possible, you can use the Zabbix API to export and import...

In any case, I would have to edit the Agent's config files to switch to the new environment, or when going into production, remove the network interface (IP) from the old environment and put it in the new one, thus avoiding this change in the agents...

[n3r0]

Hi!

I recommend performing a dump of the database and uploading it to the new environment... if it's for a different database, check if there's a dump converter.

If that's still not possible, you can use the Zabbix API to export and import...

In any case, I would have to edit the Agent's config files to switch to the new environment, or when going into production, remove the network interface (IP) from the old environment and put it in the new one, thus avoiding this change in the agents...

Thank You very much for your feedback!

Also, I want to clarify.

I want to install new zabbix server with Agent 2.

"In any case, I would have to edit the Agent's config files to switch to the new environment" In my case, if I will run server with Agent 2, that means that the host also should be updated to Agent 2? Or this will not affect?

[cyber]

Version upgrade is done autoamtically, during first startup of server. If you have side-by side new environment prepared, drop that new v7 DB and import your old DB, all the v6 schema, data, everything. After that, when you start your v7 server, it shoudl detect, that there is old version of DB. It starts all the upgrade procedures and depending on the DB size it will be ready quite quickly (depends what DB you use and is there a need to apply some DB patches etc, like reapply timescale config to add some new TS tables and convert old data, that might take more time than initial upgrade)). As this is separate instance, you can test this multiple times, if needed, just wiping DB and trying again, if something fails and you have fixed, what failed... Just follow the upgrade procedure in docs...

Agent version is not anywhere in hosts config in DB... So it does not matter, which one you install. Just make sure your agent config is in place.. You can install classic and agent2 on same host. When you have done your upgrade on server side, shut down classic one, start up agent2. If configuration file is correct, it will connect to your new server and everything just continues from that same place... Then uninstall classic agent...