| Previous | Next |
| hrMissingRestoreLogFiles | hrBadBackupDatabaseSize |
hrMissingFullBackup
How to read this HRESULT
hrMissingFullBackup means an incremental backup set does not have the earlier full backup required to establish its database baseline.
The stored value is 0xC8000230 (negative JET error -560; -560). Current ESE documentation uses JET_errMissingFullBackup for the corresponding published JET condition.
The first useful distinction is that this is a chain-completeness failure even if every incremental log file is present. Start by tracing parent backup IDs, database signature, full/incremental timestamps, catalog retention, and copied media sets.
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 backup set does not have the earlier full backup required to establish its database baseline |
| Narrow corrective direction | locate the matching full backup or discard the orphan incremental chain and create a new 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.
What to collect first
- Code-specific observation: trace parent backup IDs, database signature, full/incremental timestamps, catalog retention, and copied media sets.
Controlled remediation
- Record it,
0xC8000230, the API name, the current phase, and all live context or file owners. - Verify the condition by tracing parent backup IDs, database signature, full/incremental timestamps, catalog retention, and copied media sets.
- Apply only the targeted fix: locate the matching full backup or discard the orphan incremental chain and create a new full backup.
Acceptance criteria for a fix
A useful regression test should force the condition “an incremental backup set does not have the earlier full backup required to establish its database baseline”, call one documented API transition, and assert the exact HRESULT.
Related codes
It specifically means that this is a chain-completeness failure even if every incremental log file is present. Related values below can appear in the same workflow but require a different response:
hrInvalidBackup | an incremental external backup was requested while circular logging prevents preservation of the required historical log range |
|---|---|
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 |
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.
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.