Loading ...
Loading ...
Loading ...
1. A XProtect Smart Client user creates an evidence lock. Information sent to Management Server.
2. Management Server stores information about the evidence lock in the SQL database.
3. Management Server informs Recording Server to store and protect the protected recordings in the
database.
When the operator creates an evidence lock, the protected data remains in the recording storage that it was
recorded to, and is moved to archiving disks together with non-protected data, but the protected data:
l
Follows the retention time configured for the evidence lock. Potentially infinitely
l
Keeps the original quality of the recordings, even if grooming has been configured for non-protected data
When an operator creates locks, the minimum size of a sequence is the period that the database divides
recorded files into, this is by default one-hour sequences. You can change this, but it requires that you
customize the RecorderConfig.xml file on the recording server. If a small sequence spans two one-hour
periods, the system locks the recordings in both periods.
In the audit log in the Management Client, you can see when a user creates, edits, or deletes evidence locks.
When a disk runs out of disk space, it does not impact the protected data. Instead, the oldest non-protected
data will be deleted. If there are no more non-protected data to delete, the system stops recording. You can
create rules and alarms triggered by disk full events, so you are automatically notified.
Except for more data being stored for a longer period and potentially affecting disk storage, the evidence lock
feature as such does not influence system performance.
If you move hardware (see Move hardware on page 324) to another recording server:
Administrator manual | XProtect® VMS 2023 R1
71 | Overview
Loading ...
Loading ...
Loading ...