| Previous | Next |
| ERROR_LOG_ARCHIVE_IN_PROGRESS | ERROR_LOG_NOT_ENOUGH_CONTAINERS |
ERROR_LOG_EPHEMERAL
The CLFS log is ephemeral and is not an archivable persistent log
CLFS distinguishes non-ephemeral logs, whose data is retained until archived, from ephemeral logs that are not archived and can discard older data to make room for newer records. Archive and restore operations apply to physical logs that participate in the archive model. An archive-dependent operation is therefore invalid when the log was created or configured for ephemeral behavior.
Confirm whether the workload actually requires durable historical log retention or only a rolling recovery window. If archival is required, the log design must use a non-ephemeral log and the application must periodically archive extents and advance the archive tail. Do not treat this error as a request to copy container files manually: a live file copy is not the CLFS archive protocol. If ephemeral behavior is intentional, remove the archive-only code path and design recovery around the records that remain in the active range.
What to inspect
- Determine whether long-term archive retention is a requirement for the owning client.
- Inspect log creation/configuration for ephemeral versus archivable behavior.
- Use CLFS archive APIs only for non-ephemeral physical logs.
References
- Microsoft: CLFS archive mode, archive tail, and physical-log archive contexts
- Microsoft: PrepareLogArchive and active-log extent snapshots
- Microsoft: CLFS base log files, containers, dedicated and multiplexed logs
Looking for a different code? Search another status or error code.