Make sure to read general information about upgrading first.
Stop Zabbix server to make sure that no new data is inserted into database.
If upgrading the proxy, stop proxy too.
This is a very important step. Make sure that you have a backup of your database. It will help if the upgrade procedure fails (lack of disk space, power off, any unexpected problem).
Make a backup copy of Zabbix binaries, configuration files and the PHP file directory.
PHP files and Zabbix binaries:
To proceed with the upgrade your current repository package has to be updated.
To upgrade Zabbix components you may run something like:
If using PostgreSQL, substitute
pgsql in the command. If upgrading the proxy, substitute
proxy in the command.
The HistoryTextCacheSize parameter has been replaced by a new HistoryIndexCacheSize server/proxy parameter, which must be present for the server/proxy to start.
For other recommended changes and new parameters, see the What's new section.
Start the updated Zabbix components.
After the upgrade you may need to clear web browser cookies and web browser cache for the Zabbix web interface to work properly.
It is possible to upgrade between minor versions of 3.0.x (for example, from 3.0.1 to 3.0.3). Upgrading between minor versions is easy.
To execute Zabbix minor version upgrade it is required to run:
To execute Zabbix server minor version upgrade run:
To execute Zabbix agent minor version upgrade run:
Note that you may also use 'update' instead of 'upgrade' in these commands. While 'upgrade' will delete obsolete packages, 'update' will preserve them.