Open

How To Article | HTA-20220531-LG-25 iProtect Access / Security | How To Articles |

Open

Database

iProtect™ use a Fairom c-tree database. There can be maximum 10.000.000 records being stored in iProtects™ database.

10.000.000 is the amount in the lasted iProtect™ versions, to be sure how many records there can be in your version of iProtect™ you can check it in the following menu:

Use the search (Transaction):

And you see the maximum records is 10000000. This database is filled with 128772 events records. Not yet full so it can grow to its maximum. Then it will use the first in / first out rule. A new record will delete the oldest record. Best is to try not to let it come to this, it will have a big performance impact.

Older versions of iProtect™ also have a file size limit on the database. the files where not allowed to grow beyond 2GB (and a few later versions 4GB). Be sure to update iProtect™ to the latest version if you run into file size issues.

iProtect 8.4.40 >4GB

iProtect 9.10.9 >4GB

Events

Every event in iProtect™ can be given a maximum time in days before it will be deleted.

As example we will look at “subscriber card”

The storage period is 100 days. If you know how many cards are being used and at how many times they will be presenting it to a reader you can calculate the storage.

Example:

200 cards, 50 times used by a reader is 10.000 events in the database.

But that are not all events which occur when going thru a door, also a output active (100 days), output inactive (100 days), door status changed (100 days). So at least with this settings there will be 40.000 events stored.

Video and alarms also generates a lot of events. Even a login and logout from external users can fill up the database quickly.

Events not needed for storage can also be set to 0 days, when the system needs the event for actions or procedures, it will still work.

Event Frequency report

To monitor the event frequency there is a report function:

This will create a PDF with event statistics for the last 11 days. This will give a good insight of the most occurring events so you can lower the storage period of not needed events (Output events can easily lowered to 14 days).

In this screenshot there are some Video events, you may leave it this way or set the Storage period at 1 day. And surely always look at the root cause of the problem.