Description
Individual Expiration Configuration Rules will not delete existing video files which can result in Oldest Content to exceed configured At Most Rules.
Product
- exacqVision Server
Steps to Reproduce
- Add a camera
- Configure individual expiration configuration rule for At Most X days
Expected Results
- PS and PSI files are removed if they are older than X days
Actual Results
- Some PS and PSI files exist which are older than X days
Solution
The above has been found to be true if the following conditions are met
- Storage Used Space never reaches 100% of Video Space
- Cameras are configured to use individual At Most Expiration rules.
When a camera is first added there is always a period of time between when the camera initially connects and a Expiration Configuration rule can be configured. This can be very brief, think seconds or very long, days, weeks or even years. If motion is detected during this time a PS and PSI file are created without the expiration flag i.e. “80” instead of “00”. Combined with the other prerequisites listed above, the Oldest Content will continue to increment and eventually exceed the At Most days configured.
Example
- 4/13/2022 2:03:37 PM Camera added to the system
- 4/13/2022 2:04:09 PM Expiration configuration rules configured
A check of the storage drive shows the following:
Since motion was detected at some point in the 32 seconds it took between adding the camera and the expiration configuration rule being setup there is now both a ps and psi file on the storage drive without an expiration flag. These files will never be removed as part of the newest in oldest out file processing since the storage drive never completely fills. Eventually this will cause the oldest content to exceed the number of At Most days configured.
Workaround
- Manually identify and remove the files with the missing expiration flag
- Use System Wide Expiration Configuration rules
Related trac ticket #23441
