Maintenance & Data Retention

Routine maintenance of a node is small but regular: keep the license valid, keep retention honest, keep watchlists clean, and keep images updated deliberately. Most of it can be scheduled quarterly; retention runs itself once configured correctly.

Data retention and GDPR

The retention job deletes expired event records and images automatically at the configured TTLs — verify it actually runs (record counts should plateau, not grow) and that the TTLs still match your data-protection commitments. Deployments that must not store biometric event data at rest run STORAGE_ENABLED=false; everything still works live, only history queries return nothing. Full model in Event Storage & Retention.

Watchlist hygiene

Watchlists degrade silently: subjects leave, duplicates accumulate, enrollment photos age. Schedule a periodic review — remove stale subjects, re-enroll low-quality references, and confirm the allowed/denied wiring still reflects operational policy. Cleaner watchlists are faster and more accurate; see Tuning Identification.

License and credentials

The iengine.lic license file is tied to host hardware — plan its renewal and re-issue it via the Customer Portal before any hardware replacement, not after. Registry robot-account tokens do not expire but should rotate with your secret policy.

Backups

With storage disabled there is little state to lose: configuration files and the VPP database (watchlists, subjects) are the assets to back up. With storage enabled, add the PostgreSQL event store to your backup scope only if your audit requirements demand it — by design it is a short rolling window, and letting it expire is often the correct behavior.