| Previous | Next |
| hrIncrementalBackupDisabled | hrCircularLogging |
hrLogFileNotFound
State represented by this code
hrLogFileNotFound means an incremental Directory Service backup cannot assemble the required transaction-log set.
The stored value is 0xC7FF000A (facility-specific HRESULT). The legacy symbolic name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that hrMissingLogFile is an ESE current-log failure; this code is the higher-level incremental-backup contract. Start by enumerating the expected and present log generations, checkpoint position, prior truncation, circular-logging state, and backup catalog.
Data for a reproducible incident
- Code-specific observation: enumerate the expected and present log generations, checkpoint position, prior truncation, circular-logging state, and backup catalog.
Objects and state involved
| Diagnostic layer | full-backup baseline, incremental descendants, retained log generations, and catalog lineage |
|---|---|
| Relevant API surface | DsBackupPrepare backup type, log enumeration/truncation, and ESE external backup |
| Code-specific condition | an incremental Directory Service backup cannot assemble the required transaction-log set |
| Narrow corrective direction | recover the missing log only from the same lineage or abandon the incremental attempt and create a full backup |
An incremental backup depends on a previous full database image and a continuous required log history. Circular logging retires old generations based on checkpoint state rather than backup-chain retention needs.
Actions that can make diagnosis worse
- Do not delete logs manually to make a directory look clean.
- Do not combine an incremental set with an unrelated full backup.
Nearby ESE or AD backup states
It specifically means that hrMissingLogFile is an ESE current-log failure; this code is the higher-level incremental-backup contract. Related values below can appear in the same workflow but require a different response:
hrFullBackupNotTaken | the caller requested an incremental backup without a completed full backup recorded as its baseline |
|---|---|
hrMissingFullBackup | an incremental backup set does not have the earlier full backup required to establish its database baseline |
hrCircularLogging | the Directory Service component is using circular logs, so the historical range needed for an incremental backup is not guaranteed to remain |
Next actions
- Record it,
0xC7FF000A, the API name, the current phase, and all live context or file owners. - Verify the condition by enumerating the expected and present log generations, checkpoint position, prior truncation, circular-logging state, and backup catalog.
- Apply only the targeted fix: recover the missing log only from the same lineage or abandon the incremental attempt and create a full backup.
Technical references
- AD backup walkthrough — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- ESE files and circular logging
- External backup sequence
- Microsoft JET_ERR enumeration
- Microsoft list of AD DS backup errors
Looking for a different code? Search another status or error code.