�����IJ�

6 Upgrade procedure using sources

Overview

This section provides the steps required for a successful upgrade to �����IJ� 3.2.

Direct upgrade to �����IJ� 3.2 is possible from �����IJ� 3.0.x, 2.4.x, 2.2.x and 2.0.x. For upgrading from earlier versions consult �����IJ� documentation for 2.0 and earlier.

While upgrading �����IJ� agents is not mandatory (but recommended), �����IJ� server and proxies must be of the same major version. Therefore, in a server-proxy setup, �����IJ� server and all proxies have to be stopped and upgraded.

To minimize downtime and data loss during the upgrade, it is recommended to stop and upgrade �����IJ� server and then stop, upgrade and start �����IJ� proxies one after another. When all proxies are upgraded, start �����IJ� server. During the �����IJ� server downtime, running proxies will keep collecting and storing data and will pass the data to �����IJ� server when the server is up and running. Any notifications for problems during �����IJ� server downtime will be generated only after the upgraded server is started.

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.

Note that database upgrade to version 3.2 may take up to several hours depending on the database size.

Before the upgrade from 3.0.x to 3.2:

• read the upgrade notes for 3.2
• check requirements for 3.2

If upgrading from earlier versions, read also the upgrade notes for 2.0 → 2.2, 2.2 → 2.4 and 2.4 → 3.0.

Server upgrade process

1 Stop �����IJ� server

Stop �����IJ� server to make sure that no new data is inserted into database.

2 Back up the existing �����IJ� database

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).

3 Back up configuration files, PHP files and �����IJ� binaries

Make a backup copy of �����IJ� binaries, configuration files and the PHP file directory.

4 Install new server binaries

Use these instructions to compile �����IJ� server from sources.

5 Review server configuration parameters

There are no mandatory changes in this version to server parameters.

6 Start new �����IJ� binaries

Start the server. Check log files to see if the server has started successfully.

�����IJ� server will automatically upgrade the database. When starting up, �����IJ� server reports the current (mandatory and optional) and required database versions. If the current mandatory version is older than the required version, �����IJ� server automatically executes the required database upgrade patches. The start and progress level (percentage) of the database upgrade is written to the �����IJ� server log file. When the upgrade is completed, a "database upgrade fully completed" message is written to the log file. If any of the upgrade patches fail, �����IJ� server will not start. �����IJ� server will also not start if the current mandatory database version is newer than the required one. �����IJ� server will only start if the current mandatory database version corresponds to the required mandatory version.

8673:20161117:104750.259 current database version (mandatory/optional): 03020000/03020000
       8673:20161117:104750.259 required mandatory version: 03020000

Before you start the server:

• Make sure the database user has enough permissions (create table, drop table, create index, drop index)
• Make sure you have enough free disk space.

7 Install new �����IJ� web interface

The minimum required PHP version is 5.4.0. Update if needed and follow installation instructions.

Proxy upgrade process

1 Stop �����IJ� proxy

Stop �����IJ� proxy.

2 Back up configuration files and �����IJ� proxy binaries

Make a backup copy of the �����IJ� proxy binary and configuration file.

3 Install new proxy binaries

Use these instructions to compile �����IJ� proxy from sources.

4 Review proxy configuration parameters

There are no mandatory changes in this version to proxy parameters.

5 Start new �����IJ� proxy

Start the new �����IJ� proxy. Check log files to see if the proxy has started successfully.

�����IJ� proxy will automatically upgrade the database. Database upgrade takes place similarly as when starting �����IJ� server.

Agent upgrade process

1 Stop �����IJ� agent

Stop �����IJ� agent.

2 Back up configuration files and �����IJ� agent binaries

Make a backup copy of the �����IJ� agent binary and configuration file.

3 Install new agent binaries

Use these instructions to compile �����IJ� agent from sources.

Alternatively, you may download pre-compiled �����IJ� agents from the .

4 Review agent configuration parameters

There are no mandatory changes in this version to agent parameters. For new optional parameters, see the What's new section.

5 Start new �����IJ� agent

Start the new �����IJ� agent. Check log files to see if the agent has started successfully.

Minor upgrade procedure

Minor upgrade procedure using sources is almost the same as major upgrade procedure. It means for example upgrading from �����IJ� 3.2.0 to 3.2.x. It is required to execute the same actions as during the major upgrade. The only difference is that during minor upgrade no changes to the database are made.