EventSentry v5 introduces two major changes with a more complex upgrade process compared to previous upgrades, especially for users utilizing the built-in PostgreSQL database.
Running the latest EventSentry installer will update an existing installation to the latest 5.0..x build. Prior to running the installer, you should back up your settings (Home > Export in the console) and optionally back up your database.
|
All server-side components of EventSentry, including the installer, built-in database and all utilities are now 64-bit. Agents are still available for 32-bit systems, but EventSentry can only be installed on 64-bit systems. |
|
EventSentry now ships with the 64-bit version of PostgreSQL v14. This latest version of PostgreSQL includes a number of improvements that will make the built-in database faster and more reliable. Upgrading to v14 is not required but highly encouraged. |
|
Clear text connections to the collector will be phased out in the next release of EventSentry. Users utilizing clear text connections with the collector need to migrate to TLS connections. |
64-Bit Upgrade
Main Files
As part of the installation process, all user data (e.g. MIBs, configuration backups) will be moved from the existing installation directory (e.g. C:\Program Files (x86)\EventSentry) to the new 64-bit installation directory (e.g. C:\Program Files\EventSentry). Any custom directories and files located in the 32-bit installation folder should be backed up and manually moved to the new installation directory.
After removing binary and temporary files (e.g. installers, crash dumps), the 32-bit installation directory will be compressed into the backup_eventsentry_x86.zip zip archive (in the 64-bit installation folder).
ADMonitor
Since ADMonitor binaries from version 4.2 and earlier are 32-bit and have also been migrated to the 64-bit platform, all data associated with ADMonitor will also be migrated to the 64-bit installation folder. All 32-bit ADMonitor data will be moved to the 64-bit installation directory and compressed (stored in the ADMonitor\backup sub directory) for backup purposes.
PostgreSQL Upgrade
When an existing PostgreSQL 9.6 database is detected, then the installer will prompt the user on whether to install the newer v14 PostgreSQL database.
|
Upgrading from EventSentry version 3.2 or earlier, which uses PostgreSQL 9.1 is not supported. Users wishing to upgrade to version 5.0 should either first upgrade to EventSentry 4.2 or contact support for additional options. |
The following two options are available when installing PostgreSQL v14:
Option 1: Archive existing data in PostgreSQL v9.6, store new data in PostgreSQL v14
Existing data is preserved in PostgreSQL v9.6, but all new data is stored in the updated v14 database. The existing v9.6 database will continue to run and will be accessible via an "Archive" profile in the web reports. New data will be accessed the same way as before. This is the most simple approach with the shortest downtime, and is recommended for large v9.6 databases.
Option 2: Migrate existing data to PostgreSQL v14, retire v9.6
Runs a script that copies data from the existing v9.6 database to the updated v14 database utilizing the PostgreSQL pg_dumpall utility. EventSentry services will be unavailable during the migration, and this process is potentially time consuming (depending on hardware and the size of the database). Since this process copies data from one database to the other, it requires free disk space equivalent to the size of the existing 9.6 database. This option does eliminate the need to keep the existing v9.6 database but is generally only recommended for smaller databases.
See the diagram below for an overview of the pros and cons of each option:
Option 1 (no data migration) |
Option 2 (data migrate) |
|
Keep PostgreSQL v9.6 database to access old data |
YES |
NO |
Ability to run searches & reports against old & new data in web reports |
NO |
YES |
Potentially extended EventSentry downtime |
NO |
YES |
Potential for errors during data migration |
NO |
YES |
Requires free disk space based on existing database size |
NO |
YES |
Updating from v4.x
No specific instructions, run installer.
Updating from v3.5
Upgrade to v4.0 first, and then follow upgrade instructions for v4.0.
Updating from v3.4
Version 3.5 and later ship with a 64-bit version of the EventSentry Heartbeat Monitor, the configuration assistant will automatically upgrade an existing 32-bit heartbeat service during the post-setup process.
Updating from v3.3
Version 3.4 and later ship with a 64-bit version of the Web Reports, the installer will automatically upgrade an existing 32-bit web reports installation by uninstalling the old and re-installing the new 64-bit version during setup. It is recommended to backup all configuration files and some settings may need to be edited manually after the upgrade, see KB 370 for more details.
Updating from v3.2
A direct upgrade path from v3.2 is not supported, In order to upgrade to version 5.0 users will need to upgrade to version 4.2 first and then upgrade to version 5.0.
