*** 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
- Follow Best Practice recommendations as outlined in Analytic Metadata Best Practices
- 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 - 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.
- 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
- Recommended WD Red options:
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:
- Stop Server Service
- Go to C: > Program Files > exacqVision > Server > eventpi (there is a Database File and XML Document named “eventpi”; you want Database File)
- Copy eventpi.db to new Volume location
- Modify eventpi.xml ‘DatabaseName’ attribute to new db path (If no “DatabaseName” attribute inside the <Events…> node then add it to the Events node
- Restart Server Service
- Conduct a search to make sure its working,
- Monitor/View new eventpi.db size and make sure it is growing
- The eventpi.db in the original location can now be removed
eventpi.db File
eventpi.xml (Modify Database Name)
Related Articles
- Artificial Intelligence Object Classification Event Triggers Filling OS Drive
- Analytic Metadata Best Practices
AESW-5987