Updating Eocortex software🔗
Note
The most up-to-date version of Eocortex can be downloaded from the eocortex.com website at the Support / Software Installation Packages Supported page.
Updating Eocortex applications can be done by installing the latest version of the application over the older one (see Installing Eocortex software from a common installer). During installation, the program files of the previous version are deleted, but all settings as well as the archive and the license binding are retained. Thus, no additional settings are required after installing the new software version.
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.
Warning
Since Eocortex version 4.0, support for Windows 7 and Windows Server 2008 operating systems, as well as 32-bit versions of other operating systems, is no longer available. This should be considered when installing or upgrading Eocortex to version 4.0 or higher.
Starting with version 2.2, the server interaction scheme in multi-server configurations of Eocortex has changed. Therefore, when updating Eocortex servers from version 2.1 or lower that are already part of a multi-server system, one of the servers must be designated as the Main server.
Note
It is recommended to enable Eocortex Client automatic update in the server settings to preserve compatibility between the server after the upgrade and the existing client computers. In addition, Eocortex Client can be installed from its own distribution package.
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.
Versions of Eocortex🔗
The version number of Eocortex applications consists of three parts: M.N.R, where M means a major version, N is for a minor version, and R is a release number.
Note
The most up-to-date version of Eocortex can be downloaded from the eocortex.com website at the Support / Software Installation Packages Supported page.
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 major or minor version, then you need to successively update the server application.
Note
To update the server version can use Centralized server update.
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.
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 performing a sequential update of a multi-server system, the procedure for stopping and updating servers must be repeated for each subsequent version. For example, to update a three-server system from version 2.3.404 to version 3.6.85, you must:
Stop all servers in the system.
Update each server, one after another, to version 2.4.350.
Stop all servers in the system.
Update each server, one after another, to version 3.6.85.
Note
In multi-server systems, you can use the centralized server update mechanism to update Eocortex server applications to the latest release within a single version (for example, when the installed and latest versions differ only by release number). This mechanism is only available in the latest versions of Eocortex, starting from version 2.3.
Sequential updating🔗
Version |
Software |
Note |
|---|---|---|
3.6.84 |
||
4.0.94 |
Starting with Eocortex 4.0, support for Windows 7 and Windows Server 2008 operating systems and 32-bit versions of supported operating systems is no longer supported. You should take this into account when installing or updating Eocortex to version 4.0 or higher. |
|
4.1.83 |
||
4.2.104 |
||
4.3.111 |
||
4.4.61 |
Starting with Eocortex 4.4, support for Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2 has been discontinued. You should take this into account when installing or updating Eocortex to version 4.4 or higher. |
|
4.5.102 |