Updating Eocortex software🔗

Note

Starting with version 2.2, the interaction scheme between servers in a multiserver configuration has changed in Eocortex. Therefore, when updating Eocortex servers running version 2.1 or earlier, if they are already joined into a multiserver system, one of the servers will need to be assigned as the Main server.

When updating the Eocortex server application from an old version to the latest one, follow the recommendations below.

Depending on the version of the installed Eocortex server application:

  • If the version of the currently installed server application differs from the recent one only by the release number, then you can update directly to the latest version.

  • If the version of the currently installed server application differs from the recent one by the number of the version, then you need to successively update the server application.

Warning

Successive updating requires you to start the server at least once after upgrading to each subsequent version.

Warning

Successive update presumes keeping the system settings and the archive of cameras. However, there is a small chance of losing the settings or the archive.

Warning

Similarly, there is an upgrade from an older to a newer version that is not up-to-date.

Warning

Each Eocortex server hosts one or more internal databases. These databases contain event information, including data generated by analytics modules, as well as other system data. This information is used for viewing event logs, generating reports, and displaying video analytics data.

Prior to version 3.4, the Firebird DBMS was used for all internal Eocortex databases.

In Eocortex version 3.4, the database for the Object Search video analytics module was migrated from Firebird to PostgreSQL. This reduced the time required to generate search results.

In Eocortex version 4.0, all internal databases were migrated to PostgreSQL. As a result, report generation time decreased and the speed of retrieving event log data increased.

Consequently, before installing version 3.4 or higher (or when updating from version 3.3 and lower to version 3.4 and higher), please review the information regarding PostgreSQL installation information.

Note

After completion of the installation, it is required to connect to the server using the Eocortex Configurator application launched on the Windows computer, and activate the license on the server.

The Eocortex Configurator application is installed on the Windows computer in the process of installing any of the following applications on the same computer: Eocortex Client, Eocortex Server or Eocortex Standalone.

Note

If there is a need to change the license without having to change the version or bit depth of the server application, no update is required. Just update the license.

Updating🔗

Updating a multi-server system is performed as follows: first, stop all Eocortex server applications within the system; then, update the servers one by one to the next version. The system's Main server must be updated first. The update for each subsequent server can only be started after the previously updated server has launched and loaded its configuration.

When updating a multiserver system sequentially, it is necessary to repeat the procedure of stopping and updating the servers for each subsequent version. For example, if a system consisting of three servers needs to be updated from version 4.2.104 to version 4.4.61, it is required to:

  1. Stop all servers in the system.

  2. Update each server to version 4.2.104 one after another.

  3. Stop all servers in the system.

  4. Update each server to version 4.4.61 one after another.

Supported Linux distributions🔗

The process for updating the Eocortex server applications for various Linux distributions is described in the documentation: