7 升级步骤

概述

本章节提供了关于升级至 Zabbix 6.4 的信息：

• 使用二进制包安装：

  • 对于 Red Hat Enterprise Linux/CentOS
  • 为了 Debian/Ubuntu

• 使用源码包 sources

可以从 Zabbix 6.2.x 直接升级到 Zabbix 6.4.x， 6.0.x、5.4.x、5.2.x、5.0.x、4.4.x、4.2.x、4.0.x、3.4.x、 3.2.x、3.0.x、2.4.x、2.2.x 和 2.0.x。 要从早期版本升级，请参阅 2.0 及更早版本的 Zabbix 文档。

While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the same major version. Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running during server upgrade no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server.

It is no longer possible to start the upgraded server and have older, yet unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled, as the server will ignore data from unupgraded proxies.

Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.

Depending on database size the database upgrade to version 6.2 may take a long time.

Proxies that are older than Zabbix server previous LTS release version or newer than Zabbix server major version are not supported. Zabbix server will ignore data from unsupported proxies and all communication with Zabbix server will fail with a warning. For more information, see Version compatibility.

To minimize downtime and data loss during the upgrade, it is recommended to stop, upgrade, and start Zabbix server and then stop, upgrade, and start Zabbix proxies one after another. During server downtime, running proxies will continue data collection. Once the server is up and running, outdated proxies will send the data to the newer server (proxy configuration will not be updated though) and will remain partly functional. Any notifications for problems during Zabbix server downtime will be generated only after the upgraded server is started.

If Zabbix proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically. Note that starting with Zabbix 6.4.0, if Zabbix proxy uses SQLite3 and on startup detects that existing database file version is older than required, it will delete the database file automatically and create a new one. Therefore, history data stored in the SQLite database file will be lost. If Zabbix proxy’s version is older than the database file version, Zabbix will log an error and exit.

Depending on the database size, the database upgrade to version 6.4 may take a long time.

Direct upgrade to Zabbix 6.4.x is possible from Zabbix 6.2.x, 6.0.x, 5.4.x, 5.2.x, 5.0.x, 4.4.x, 4.2.x, 4.0.x, 3.4.x, 3.2.x, 3.0.x, 2.4.x, 2.2.x and 2.0.x. For upgrading from earlier versions consult Zabbix documentation for 2.0 and earlier.

The following upgrade notes are available: