| Previous | Next |
| hrRestoreMapExists | hrLogFileNotFound |
hrIncrementalBackupDisabled
Why this result matters
hrIncrementalBackupDisabled means the database lineage no longer permits the requested incremental backup and requires a new full baseline.
The stored value is 0xC7FF0009 (facility-specific HRESULT). The legacy symbolic name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that missing one log file is hrLogFileNotFound; this result says the incremental chain itself has been invalidated. Start by recording the last successful full backup identity, intervening maintenance or modification, current database signature, and backup history.
Do not confuse it with
This result specifically means that missing one log file is hrLogFileNotFound; it says the incremental chain itself has been invalidated. Related values below can appear in the same workflow but require a different response:
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 |
hrCircularLogging | the Directory Service component is using circular logs, so the historical range needed for an incremental backup is not guaranteed to remain |
Forensic checklist
- Code-specific observation: record the last successful full backup identity, intervening maintenance or modification, current database signature, and backup history.
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 | the database lineage no longer permits the requested incremental backup and requires a new full baseline |
| Narrow corrective direction | take and verify a new full backup, then start a new incremental chain from that baseline |
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 combine an incremental set with an unrelated full backup.
- Do not delete logs manually to make a directory look clean.
Validation after correction
- Record it,
0xC7FF0009, the API name, the current phase, and all live context or file owners. - Verify the condition by recording the last successful full backup identity, intervening maintenance or modification, current database signature, and backup history.
- Apply only the targeted fix: take and verify a new full backup, then start a new incremental chain from that baseline.
Acceptance criteria for a fix
A useful regression test should force the condition “the database lineage no longer permits the requested incremental backup and requires a new full baseline”, call one documented API transition, and assert the exact HRESULT.
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.