| Previous | Next |
| hrMissingRestoreLogFiles | hrBadBackupDatabaseSize |
hrMissingFullBackup
How to read this HRESULT
For hrMissingFullBackup, a correct handler first decides whether the value is success, warning, or failure, then examines the documented outputs. The decisive boundary is 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). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. 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 trace parent backup IDs, database signature, full/incremental timestamps, catalog retention, and copied media sets. 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 | 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
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: trace parent backup IDs, database signature, full/incremental timestamps, catalog retention, and copied media sets.
- Database and log signatures: record it together with this result and the timestamp of the first occurrence.
- 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 this result and the timestamp of the first occurrence.
- Full and incremental backup IDs: record it together with this result 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.
Controlled remediation
- Record it,
0xC8000230, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by trace parent backup IDs, database signature, full/incremental timestamps, catalog retention, and copied media sets.
- Apply only the narrow correction: locate the matching full backup or discard the orphan incremental chain and create a new full backup.
- 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
A useful regression test for this HRESULT 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. The corrected the case should change only the decisive precondition and should verify cleanup as well as the primary output. For the result backup or restore path, also prove that the resulting set can be enumerated and that no file handle or context remains active after finalization.
Boundary with 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 |
Keep the original constant and hexadecimal value in telemetry. Replacing it with “backup failed” or “database warning” removes the state information needed to select the next legal API call.
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.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
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.