Knowledge Base

Method A: If you know the postgres user password you can use the pgAdmin utility: 1. Open pgAdmin by opening the Windows Start Menu to EventSentry pgAdmin4. If you have set a password for the PgAdmin application in the past it may prompt you for that password. 2. Double click on EventSentry Database under the Servers category ...

KB-ID 227
Category: Database
Applies to: 2.93 and newer

EventSentry Database Rotation: Creating a New Database ampamp Archiving the Old As an EventSentry database grows managing longterm data retention while maintaining performance becomes critical. While you can purge old records some environments require a Database Rotation. This process involves initializing a fresh Primary database for ...

KB-ID 549
Category: Database

To move an existing MSSQL database to a different server simply detach the database from the existing server copy it to the new system and reattach it. After the DB is online simply initialize the database again and update all connection strings: 1. Stop all EventSentry services. If you are not using the collector then all remote agents sho...

KB-ID 200
Category: Database
Applies to: 2.93 and later

This guide shows how to restore an EventSentry .backup file created with pgdump see KB235https://www.eventsentry.com/kb/235howdoibackupthebuiltineventsentrydatabase onto a separate dedicated PostgreSQL server for example to access archived/historical data without risking disk space or performance issues on your producti...

KB-ID 558
Category: Database

This article describes how to relocate a PostgreSQL database to a different drive while preserving the ability to access it through the Web Reports for historical reporting. In this example an old archive database is moved to the E: drive using a PostgreSQL tablespace. Prerequisites 1 The database being moved must be disconnected from all...

KB-ID 556
Category: Database

First we recommend you make a backup of the database in case you have any issues and need to reinstall: How do I back up the built in EventSentry database Once you39ve got a backup then you can proceed with moving the database by following these steps: Stop the EventSentry Database v14 Service Control Panel Administrative Tools ...

KB-ID 247
Category: Database
Applies to: 2.93 and newer

The Archive feature in EventSentry enables continuous parallel synchronization between a primary and secondary database. Once activated both databases remain active: one handles live data while the other serves as a realtime archive. Archiving is not retroactive the archive database will only store data collected from the moment the featur...

KB-ID 550
Category: Database

If you39re troubleshooting database issues with EventSentry and initially installed EventSentry with v6.0.1.32 or earlier then you may need to enable PostgreSQL file logging so that detailed log files are generated. Follow the steps below to configure file logging. File Location By default the postgresqleventsentry.conf file for EventSen...

KB-ID 551
Category: Database
Applies to: 6.0.1.32 and older

Starting in EventSentry 5.1 a new way to purge your database is available in Web Reports. This purge job runs more efficiently on large databases and is recommended over the database purge package in the console. If you first installed EventSentry on version 5.1 or later then the Web Reports purge should have been set up by default but if yo...

KB-ID 523
Category: Database
Applies to: 5.1 and later

Overview Customers frequently report that after deleting large amounts of data from their EventSentry database the database file size remains unchanged or the free disk space doesn39t increase as expected. This behavior is normal and by design for both PostgreSQL and Microsoft SQL Server databases. Why This Happens Databases are optimiz...

KB-ID 540
Category: Database
Applies to: All Versions

NOTE: Starting in EventSentry 5.1 the default way to purge your database is from Web Reports. Please see KB 523https://www.eventsentry.com/kb/523 for information on how to set up this new purge and change the number of days in your retention period. Beginning with EventSentry 3.0 during the installation you39re presented with an o...

KB-ID 325
Category: Database
Applies to: All versions

If after purging data from your EventSentry database you still have enough disk space approximately 1.5x the database size is needed available on the drive you can open the PgADMIN software doubleclick EventSentry localhost:5432 to bring up the logon window and log on with the Postgres password and then follow these steps to shrink...

KB-ID 241
Category: Database
Applies to: 2.93 and newer

You can remove data from the EventSentry database in two ways: Through the web reports with the maintenance wizard or through the commandline utility esdbpurge.exe using the 39sa39 39root39 or 39postgres39 account and password. 1. Database Maintenance Wizard The database maintenance wizard is available through the web reports and can be access...

KB-ID 183
Category: Database
Applies to: All Versions

If our support department has requested that you run a script or query using PgAdmin here are the steps: 1 Rightclick PgAdmin and run as an administrator Start Programs EventSentry pgAdmin4 or Start Programs EventSentry Database if you are on an older version. If you have a pgAdmin master password set you wi...

KB-ID 313
Category: Database
Applies to: 2.93 and newer

If you experience data corruption data loss or accidentally delete files from the internal Postgres database this guide will walk you through the steps to regenerate the internal Postgres database structure and recreate a fresh empty EventSentry database. Before proceeding with this guide ensure that you back up the data14 directory. T...

KB-ID 519
Category: Database
Applies to: 5.0 and later

The builtin EventSentry database ships with a basic configuration which is tuned for wide compatibility instead of speed. If you are collecting a lot of data it is likely that the default parameters are undersized for your system resulting in poor collector performance high outbound queue size or resulting in poor performance when searching...

KB-ID 232
Category: Database
Applies to: 2.93 and newer

If you are using the built in EventSentry database you can back it up using the pgdump.exe utility. This is located by default in the EventSentry\postgresql14\bin folder. You can create a batch file with the following contents: batch ECHO OFF SET PGPASSWORD=yourpostgresaccountpassword C:\Program Files\EventSentry\postgresql14\bin\p...

KB-ID 235
Category: Database
Applies to: 2.93+

Since the Server Admin account created when you setup a database in Azure has only limited permissions running the EventSentry Configuration Assistant to automatically create the database and users is not an option for Azurebased PaaS databases. However in a few easy steps you can manually create a database with the users in Azure to use...

KB-ID 350
Category: Database
Applies to: EventSentry 3.3

Some events contain binary data which is almost never read or analyzed by anyone and therefore can be safely ignored. The Ignore Binary Data setting controls whether or not the EventSentry agent writes binary data to the database when an event contains binary data. Binary data has poor insert performance since it cannot be indexed so it i...

KB-ID 347
Category: Database
Applies to: All

Yes We first recommend creating two domain accounts eventsentrysvc and eventsentryweb and then on the machine with EventSentry give these accounts Local Administrator rights. These are the accounts that your EventSentry related services will be running as Agent Heartbeat Collector etc. which typically run as the Local S...

KB-ID 391
Category: Database
Applies to: 4.0.3

This is a common question that is asked frequently but unfortunately also somewhat difficult to answer since there are many factors that impact the disk usage of EventSentry. Every line item below can significantly impact the disk usage of the EventSentry database. Number of monitored Windows hosts Audit Settings of Servers OS Type Doma...

KB-ID 385
Category: Database
Applies to: 3.5 and later

When trying to backup the EventSentry Database in pgAdmin v9.6 you receive an error message containing: server version: 9.6. pgdumpall version: 9.5.1 aborting because of server version mismatch You can fix this error by going to File Options Binary path and changing PG Bin Path to: C:\Program Files x86\EventSentry\postgresql96...

KB-ID 383
Category: Database
Applies to: EventSentry 3.4 or newer

If you are not utilizing the builtin PostgreSQL database then you can ignore this article. EventSentry v3.3 includes a new version 9.6 of the builtin PostgreSQLbased database since the previously included v9.1 no longer receives security updates from the PostgreSQL team. Since PostgreSQL database generally don39t offer an option to simply ...

KB-ID 332
Category: Database
Applies to: 3.3 and higher

Option A: If you have not completed the Configuration Assistant when installing EventSentry for the first time: 1A Use the Microsoft documentation to locate the nonLatin text language you need to record and then copy that language39s Location column value from the documentation: https://msdn.microsoft.com/enus/library/cc233982.aspx 2A Execut...

KB-ID 333
Category: Database
Applies to: 3.0 and newer

If you are running the builtin PostgreSQL database you can perform maintenance using the pgAdmin administration and management tool which is included with EventSentry. Running the REINDEX maintenance command in PostgreSQL will rebuild all indexes using current data and replace the old copy of the index. There are several scenarios in which t...

KB-ID 320
Category: Database
Applies to: v2.93.1 or later