| Previous | Next |
| ERROR_LOG_ARCHIVE_NOT_IN_PROGRESS | ERROR_LOG_EPHEMERAL |
ERROR_LOG_ARCHIVE_IN_PROGRESS
CLFS is already processing an archive of this physical log
PrepareLogArchive takes a snapshot of the active physical log and allocates an archive context used to enumerate metadata and extents. Archive-tail changes can also be deferred while archive contexts remain outstanding. An operation that conflicts with this live snapshot may be rejected until the archive workflow is completed and its contexts are terminated.
Enumerate archive workers and trace every successful PrepareLogArchive to a matching TerminateLogArchive, including cancellation and error paths. If multiple jobs can archive the same physical log, serialize them at the log identity level rather than only per logical stream. Do not simply retry in a tight loop; a leaked context will keep the state active. After the current archive completes, re-query the archive tail and active range because the values captured before the conflict may have changed.
What to inspect
- Match each successful archive preparation with exactly one termination path.
- Serialize archive jobs by physical log, including streams in a multiplexed log.
- Re-query log boundaries after the active archive ends before starting the next snapshot.
References
- Microsoft: PrepareLogArchive and active-log extent snapshots
- Microsoft: SetLogArchiveTail and physical archive-tail LSN requirements
- Microsoft: CLFS archive mode, archive tail, and physical-log archive contexts
Looking for a different code? Search another status or error code.