Winlog rollover recovery: verify live intake and EVTX backlog separately
New live events do not establish recovery of unread archive records.
The gap behind new events
Verify live resubscription separately from archive-backlog recovery. New arrivals do not establish that unread record ids in the previous file landed. That is why the source side of a Truthound reconciliation must include archive generation; restored live throughput leaves the verified historical gap unresolved. [1, 2, 3]
A jump is not a verified record inventory
Winlog #53655 reports unread events remaining in EVTX archives after archive-on-full, while live-channel resubscription cannot read them. The jump of 12,331 and 15 individually verified events are different evidence and must not be presented as one confirmed loss count. Read the archive evidence and resubscription behavior at their stated scope. [1]
Change the recovery source location
Reconcile the unread range using the pre-rollover bookmark and the archive boundary. Preserve the archive, test documented EVTX file input on a bounded scope, and distinguish already landed record ids during backfill. Identify records by channel, generation and record id so numbers reused in another file are not mistaken for recovery. [1, 3]
An independent basis for five records
In the illustrative archive, records 101105 are directly verified after accepted bookmark 100. The expected backlog is 105−100=5, independent of new live counts. A recovered count of 5 meets only the count condition; each of 101105 must occur once. New live data with backlog count 0 fails. This defines a recovery contract rather than measuring an actual loss total. [1, 3]
Validate the verified backlog
Truthound Core Python SDK 3.3.2 can compare verified_archive_backlog_records and recovered_backlog_records using ColumnPairValidator with relationship="==". The external reconciliation calculates archive-key presence and duplicates and isolates unknown scope. The SDK does not automatically open EVTX files or repair Windows bookmarks. [1, 2, 3]
Scope recovery completion
After backfill, reconcile the archive and new live intake separately. A reader that caught up before rollover may have no unread backlog, so configuration alone does not establish a gap. If the original records cannot be verified, keep the id gap unresolved rather than filling it with a guessed recovery count of 0. [1, 3]
Application conditions
Preserve archives and identify records by channel, generation and record id; distinguish a jump from verified missing records.
Alternatives
Backfill through documented EVTX file input and apply the existing retransmission policy for already landed records.
Limitations
Truthound does not automatically recover EVTX or establish the entire record-id gap as confirmed loss.
Evidence
- Event checked
- Subject checked
- Modified
