Differences between LPR Manager 5.x and 5.7 - Security Center 5.7 SR1

Security Center Installation and Upgrade Guide 5.7 SR1

series
Security Center 5.7 SR1
revised_modified
2018-01-23

Beginning in Security Center 5.6, the LPR Manager must work in tandem with an Archiver. After upgrading an LPR Manager from 5.5 or earlier to 5.7, the role might be in the warning state (yellow). To make the LPR Manager operational, you must assign an Archiver role to it.

Data management: Before and After

The following diagram shows how data are stored before and after Security Center 5.6.

Feature differences

Characteristics LPR Manager 5.5 and earlier LPR Manager 5.6 and later
Data management The LPR Manager stores both the LPR images (captured by context cameras, LPR cameras, and wheel imaging cameras), and the LPR metadata (reads, hits, timestamps, Patroller positions, and so on) in a database. The LPR Manager stores the LPR metadata (reads, hits, timestamps, Patroller positions, and so on) in a database. The Archiver stores the LPR images (captured by context cameras, LPR cameras, and wheel imaging cameras) on disk in G64 files.
Data retention periods Data retention periods configured in LPR Manager properties. Data retention periods configured in LPR Manager properties. The Archiver follows the LPR Manager's data retention settings.
Automatic cleanup Once per day. Every 15 minutes for LPR metadata.

Every 5 minutes for LPR images.

SQL Express capacity Limited to 10 GB per database (roughly 160,000 reads with images). Limited to 10 GB per database, but stores up to 6 million reads because the image data are no longer stored in the database.
Performance - Updated data structure to improve query performance.
Configuration LPR Manager configuration tabs. LPR Manager configuration tabs.

Archiver Resources tab.

Media Router Properties tab.

Role failover In Config Tool, assign a secondary server to the LPR Manager role, and make sure the LPR Manager database is accessible over the network from both servers. No changes to the LPR Manager failover configuration.

The Archiver failover is configured separately and independently of the LPR Manager. Each server assigned to the Archiver role must have its own archive database. This means that when the Archiver role fails over to the secondary server, the data managed by the primary server is not available.

Best Practice: To simplify the failover configuration, we recommend assigning the same primary and secondary servers to both the LPR Manager and the Archiver roles, provided that these servers meet the combined load requirements.
Backup and restore The LPR Manager database is backed up and restored like any role database. The LPR Manager database is backed up and restored like any role database.
The Archiver database is only used to store the catalog of the G64 files stored on disk. To protect your LPR data, you must back up both the Archiver database and the G64 files.
NOTE: The Archive transfer task does not yet support G64 files containing LPR images. If you restore the G64 files to a different disk, you must re-index these files in the Archiver database using the VideoFileAnalyzer.exe tool.