As an alternative to backing up all events, you can prune and archive old events.
· Pruned events are removed from the live database table and placed in a separate database table, allowing you to reduce the size of the main database while keeping them accessible on the ICPAM system. Pruned events are not visible in Events & Alarms, but are included in reports. Pruned events are also included in system backups.
· Archived events are removed from all ICPAM database tables and copied to a compressed file. The file includes a password-protected SQL script, and can be run on an offline database to view the purged events. Archived events are not visible in the Events & Alarms listings or Reports, and are not included in system backups.
Archiving historic events improves system performance and simplifies monitoring since only the latest, most relevant, events and alarms are displayed. System backup file sizes are also reduced. In addition, the historical event records are self-contained. Referenced objects, such as a person's name and card number, are retained even if the original record is deleted. Reports on historical events can also span a much longer time range than is normally possible for live events.
Archived event files can be restored to the ICPAM database, if necessary, or used by other applications to view old events or run reports. See the Creating Reports from Pruned Events.
See the Archiving Historical Events for more information.
See also:
Backing Up and Archiving Events