Tag: eventpi.db

Categories
Configuration Knowledge Support Support exacqVision Client exacqVision Server Categories Products

Analytic Metadata Best Practices

With Artificial Intelligence being used more often users may notice a spike in the analytic metadata being processed and stored.  Here are our recommendations to manage this increase.

Update exacqVision Server/Client Software

  • Ensure you are running the latest version of both exacqVision Server and Client software.  
  • Search “updating” in the exacqVision Client User Manual, available Here for information on updating.

Adjust Camera Settings

  • Access Analytics from the camera’s configuration GUI page
  • Only those analytic types required by the customer should be enabled
  • The goal is to keep this setting as minimal as possible, while still achieving the customers goals.

Reduce DB retention period

  • Reduce ‘Maximum Days to Keep Bounding Box Metadata’ available in exacqVision Server/Client 23.09 and higher. See: Maximum Days to Keep Bounding Box Metadata Explained
  • Reduce the ‘Maximum Days to Keep Logged Events’
  • These settings decide when older items should be removed or “Purged” from the Database (eventPI), the lower the value, the less storage needed. 
  • It is recommended to set this value as low as possible and adjust based on available storage when data is processing
  • Customer retention requirements must also be considered.

Disable Analytics

  • Each camera is different, but if the user does not have enough storage for 24 hours of analytics, or if analytics are not needed, currently the best option is to disable the analytics completely. 
  • Within the exacqVision Client software, go to Configuration → Server → Configure System → Add IP Cameras → Camera Recording → Analytics Camera → Analytics tab – Uncheck “Record analytic data”

AESW-5987

Categories
Knowledge Support Support exacqVision Server Categories Uncategorized

Moving Eventpi.DB file to New Drive

*** INTERNAL USE ***

Description 

We have found that event links based on triggers from AI Object Classification events flood the eventPI database resulting in the OS drive being filled in a short amount of time. Periodic unexpected crashes, system reboots and increased memory usage have resulted. This happens when the amount of AI metadata captured in the eventPI database exceeds the available free space on the drive.

Product 

  • exacqVision Server [All versions]

Prerequisites

  1. Follow Best Practice recommendations as outlined in Analytic Metadata Best Practices
  2. If your license allows, update the exacqVision Server and Client instances to 23.09 or higher to take advantage of the Maximum Days to Keep Bounding Box Metadata control. Try this solution prior to moving the eventpi.db.
    Maximum Days to Keep Bounding Box Metadata Explained
  3. Moving the eventpi.db should be considered an extreme final effort reserved for those that insist on long term retention of large amounts of metadata.
  4. When moving eventpi.db, you should only do so onto a newly installed NVMe or SSD drive designed for frequent writes. We strongly advise selecting drives with specs of 2500 TBW (Terabytes Written) or higher. Systems without available NVMe slots, such as the 4U A-Series, will need to rely on Internal NAND SSD.
    • Recommended WD Red options:
      • NVMe – WDS200T1R0C
      • NVMe – WDS400T1R0C
      • SATA SSD – WDS400T1R0A

WARNING: We DO NOT recommend by any means, moving the database onto a video recording drive.

Solution

NOTE: If your license allows, update the exacqVision Server and Client instances to 23.09 or higher to take advantage of the Maximum Days to Keep Bounding Box Metadata control. Try this solution prior to moving the eventpi.db.
Maximum Days to Keep Bounding Box Metadata Explained

Move the eventpi.db database according to the following procedure:

  1. Stop Server Service
  2. Go to C: > Program Files > exacqVision > Server > eventpi (there is a Database File and XML Document named “eventpi”; you want Database File)
  3. Copy eventpi.db to new Volume location
  4. Modify eventpi.xml ‘DatabaseName’ attribute to new db path (If no “DatabaseName” attribute inside the <Events…> node then add it to the Events node
  5. Restart Server Service
  6. Conduct a search to make sure its working,
  7. Monitor/View new eventpi.db size and make sure it is growing
  8. The eventpi.db in the original location can now be removed

eventpi.db File

eventpi.xml (Modify Database Name)

Related Articles

AESW-5987

Categories
Knowledge Support Support exacqVision Server Categories Products

Artificial Intelligence Object Classification Event Triggers Filling OS Drive

Description 

We have found that event links based on triggers from AI Object Classification events flood the eventPI database resulting in the OS drive being filled in a short amount of time. Periodic unexpected crashes, system reboots and increased memory usage have resulted. This happens when the amount of AI metadata captured in the eventPI database in a single day exceeds the available free space on the drive.

The following exacqVision Server log entries confirm when this issue is occurring.

Product 

  • AXIS Object Analytics
  • Hanwha AI-based object detection
  • Illustra AI Object Classification
  • exacqVision Server [All versions]

Solution

Update the exacqVision Server and Client to version 23.09 or higher.

Once updated, utilize the ‘Maximum Days to Keep Bounding Box Metadata’ control. Details on this feature may be found in Maximum Days to Keep Bounding Box Metadata Explained

Related Articles

AES-392