| Previous | Next |
| hrLogFileNotFound | hrNoFullRestore |
hrCircularLogging
The exact boundary reported here
For hrCircularLogging, treat the value as part of a state machine: it says what remained valid and what did not. The decisive boundary is the Directory Service component is using circular logs, so the historical range needed for an incremental backup is not guaranteed to remain.
The stored Value is 0xC7FF000B (facility-specific HRESULT). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. The legacy this result name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that a full backup can still be valid; the incompatibility is specifically with an incremental chain that depends on retained generations. Start by capture the circular-logging setting, checkpoint generation, oldest retained log, requested backup type, and previous full backup. That separates a reproducible incident from a later generic cleanup or service error.
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 boundary | the Directory Service component is using circular logs, so the historical range needed for an incremental backup is not guaranteed to remain |
| Narrow corrective direction | perform a full backup or change logging policy through the supported product configuration before establishing a new chain |
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.
Adjacent conditions
This result specifically means that a full backup can still be valid; the incompatibility is specifically with an incremental chain that depends on retained generations. Related values below can appear in the same workflow but require a different response:
hrMissingFullBackup | an incremental backup set does not have the earlier full backup required to establish its database baseline |
|---|---|
hrLogFileNotFound | an incremental Directory Service backup cannot assemble the required transaction-log set |
hrFullBackupNotTaken | the caller requested an incremental backup without a completed full backup recorded as its baseline |
Keep the original constant and hexadecimal value in telemetry. Replacing this result with “backup failed” or “database warning” removes the state information needed to select the next legal API call.
Diagnostic record
Preserve the first result before retries, cleanup, service restart, or file replacement changes the evidence. The diagnostic record should identify the exact API phase and the owner of every handle or artifact involved.
- Code-specific observation: capture the circular-logging setting, checkpoint generation, oldest retained log, requested backup type, and previous full backup.
- Generation range and checkpoint: record it together with this result and the timestamp of the first occurrence.
- Catalog and truncation history: record it together with it and the timestamp of the first occurrence.
- Full and incremental backup IDs: record it together with it and the timestamp of the first occurrence.
- Database and log signatures: record it together with it and the timestamp of the first occurrence.
Use hashes, lengths, IDs, generation numbers, and redacted samples instead of copying directory contents or sensitive database values into routine logs. For this it investigation, a complete provenance chain is often more useful than a second automatic retry.
Actions that can make diagnosis worse
- do not combine an incremental set with an unrelated full backup.
- do not delete logs manually to make a directory look clean.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
Corrective path
- Record it,
0xC7FF000B, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by capture the circular-logging setting, checkpoint generation, oldest retained log, requested backup type, and previous full backup.
- Apply only the narrow correction: perform a full backup or change logging policy through the supported product configuration before establishing a new chain.
- After it, recreate any context invalidated by the failure; do not carry stale HBC, cursor, file, or restore-map state into the retry.
- repeat the smallest non-destructive test that reaches the same boundary, then verify both the return value and the resulting file, cursor, backup, or database state.
Acceptance criteria for a fix
Technical references
- AD backup walkthrough — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- 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.