Documentation
7 升级步骤
概述
本章节提供了关于升级至 Zabbix 6.4 的信息：
- 使用二进制包安装：
- 使用源码包 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:
| Upgrade from | Read full upgrade notes | Most important changes between versions |
|---|---|---|
| 6.2.x | For: Zabbix 6.4 |
|
| 6.0.x LTS | For: Zabbix 6.2 Zabbix 6.4 |
Minimum required PHP version upped from 7.2.5 to 7.4.0. Deterministic triggers need to be created during the upgrade. If binary logging is enabled for MySQL/MariaDB, this requires superuser privileges or setting the variable/configuration parameter log_bin_trust_function_creators = 1. See Database creation scripts for instructions how to set the variable. |
| 5.4.x | For: Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Minimum required database versions upped. Server/proxy will not start if outdated database. Audit log records lost because of database structure change. |
| 5.2.x | For: Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Minimum required database versions upped. Aggregate items removed as a separate type. |
| 5.0.x LTS | For: Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Minimum required PHP version upped from 7.2.0 to 7.2.5. Password hashing algorithm changed from MD5 to bcrypt. |
| 4.4.x | For: Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Support of IBM DB2 dropped. Minimum required PHP version upped from 5.4.0 to 7.2.0. Minimum required database versions upped. Changed Zabbix PHP file directory. |
| 4.2.x | For: Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Jabber, Ez Texting media types removed. |
| 4.0.x LTS | For: Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Older proxies no longer can report data to an upgraded server. Newer agents no longer will be able to work with an older Zabbix server. |
| 3.4.x | For: Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
'libpthread' and 'zlib' libraries now mandatory. Support for plain text protocol dropped and header is mandatory. Pre-1.4 version Zabbix agents are no longer supported. The Server parameter in passive proxy configuration now mandatory. |
| 3.2.x | For: Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
SQLite support as backend database dropped for Zabbix server/frontend. Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended. 'libpcre' and 'libevent' libraries mandatory for Zabbix server. Exit code checks added for user parameters, remote commands and system.run[] items without the 'nowait' flag as well as Zabbix server executed scripts. Zabbix Java gateway has to be upgraded to support new functionality. |
| 3.0.x LTS | For: Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Database upgrade may be slow, depending on the history table size. |
| 2.4.x | For: Zabbix 3.0 Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Minimum required PHP version upped from 5.3.0 to 5.4.0. LogFile agent parameter must be specified. |
| 2.2.x LTS | For: Zabbix 2.4 Zabbix 3.0 Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Node-based distributed monitoring removed. |
| 2.0.x | For: Zabbix 2.2 Zabbix 2.4 Zabbix 3.0 Zabbix 3.2 Zabbix 3.4 Zabbix 4.0 Zabbix 4.2 Zabbix 4.4 Zabbix 5.0 Zabbix 5.2 Zabbix 5.4 Zabbix 6.0 Zabbix 6.2 Zabbix 6.4 |
Minimum required PHP version upped from 5.1.6 to 5.3.0. Case-sensitive MySQL database required for proper server work; character set utf8 and utf8_bin collation is required for Zabbix server to work properly with MySQL database. See database creation scripts. 'mysqli' PHP extension required instead of 'mysql'. |