| Previous | Next |
| hrCircularLogging | hrCommunicationError |
hrNoFullRestore
Operational meaning
hrNoFullRestore means an incremental restore was requested before a full backup had established the destination database baseline.
The stored value is 0xC7FF000C (facility-specific HRESULT). The legacy symbolic name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that hrMissingFullBackup concerns backup-chain history; this code describes the restore sequence at the destination. Start by recording the restore catalog order, target database state, full-backup identity, and which set the application marked as current.
Before altering files or retrying
- Code-specific observation: record the restore catalog order, target database state, full-backup identity, and which set the application marked as current.
Comparison points
It specifically means that hrMissingFullBackup concerns backup-chain history; this code describes the restore sequence at the destination. Related values below can appear in the same workflow but require a different response:
hrRestoreMapExists | a restore map is already registered for the component while the caller attempts to add another mapping |
|---|---|
hrExistingLogFileIsNotContiguous | the log sequence already present in the target path contains a generation gap required by recovery |
hrFileOpenReadOnly | the database file was opened in read-only mode and the resulting handle cannot support logged updates |
Objects and state involved
| Diagnostic layer | offline AD restore preparation, path mapping, directory locking, and HBC lifetime |
|---|---|
| Relevant API surface | DsRestorePrepare, DsRestoreGetDatabaseLocations, DsRestoreRegister, DsRestoreRegisterComplete, and DsRestoreEnd |
| Code-specific condition | an incremental restore was requested before a full backup had established the destination database baseline |
| Narrow corrective direction | restore and validate the matching full set first, then apply only its contiguous incremental descendants |
Legacy AD restore is performed offline and the restore directories are registered and locked before files are replaced. Restore completion status affects whether Active Directory is allowed to start.
Recommended handling
- Record it,
0xC7FF000C, the API name, the current phase, and all live context or file owners. - Verify the condition by recording the restore catalog order, target database state, full-backup identity, and which set the application marked as current.
- Apply only the targeted fix: restore and validate the matching full set first, then apply only its contiguous incremental descendants.
Acceptance criteria for a fix
A useful regression test should force the condition “an incremental restore was requested before a full backup had established the destination database baseline”, call one documented API transition, and assert the exact HRESULT.
Actions that can make diagnosis worse
- Do not report success to completion when file restoration failed.
- Do not copy files before the restore directories are prepared and locked.
Technical references
- AD restore walkthrough — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- DsRestorePrepare contract
- Restore completion contract
- Microsoft list of AD DS backup errors
Looking for a different code? Search another status or error code.