Site icon EfmSoft

What does HRESULT 0xC8000229 (hrRestoreLogTooLow) mean?

 
Previous Next
hrPatchFileMismatch hrRestoreLogTooHigh

hrRestoreLogTooLow

Interpretation in the backup state machine

hrRestoreLogTooLow means the configured upper or ending restore generation is below a log that the restore set requires.

The stored value is 0xC8000229 (negative JET error -553; -553). Current ESE documentation uses JET_errEndingRestoreLogTooLow for the corresponding published JET condition.

The first useful distinction is that the legacy name can be misleading: validate the actual range relationship rather than guessing from “too low”. Start by recording genLow, genHigh, every supplied generation, database required range, and the API parameters passed to hard recovery.

Start with these observations

  • Code-specific observation: record genLow, genHigh, every supplied generation, database required range, and the API parameters passed to hard recovery.

Objects and state involved

Diagnostic layerthe explicit low/high transaction-log generation range used for hard recovery
Relevant API surfaceJetExternalRestore and JET_LOGINFO range parameters
Code-specific conditionthe configured upper or ending restore generation is below a log that the restore set requires
Narrow corrective directionexpand the restore range to include all mandatory generations from the same sequence

Phase I requires every mandatory generation needed to bring the backup database to consistency. Later roll-forward logs are optional only after the mandatory range has been satisfied.

Recovery or retry plan

  1. Record it, 0xC8000229, the API name, the current phase, and all live context or file owners.
  2. Verify the condition by recording genLow, genHigh, every supplied generation, database required range, and the API parameters passed to hard recovery.
  3. Apply only the targeted fix: expand the restore range to include all mandatory generations from the same sequence.

Not the same as

It specifically means that the legacy name can be misleading: validate the actual range relationship rather than guessing from “too low”. Related values below can appear in the same workflow but require a different response:

hrRestoreLogTooHighthe configured starting restore generation is above an available log that belongs to the required set
hrSeekNotEquala less-than-or-equal or greater-than-or-equal seek positioned the cursor without finding an exact key match
hrLogFileNotFoundan incremental Directory Service backup cannot assemble the required transaction-log set

Actions that can make diagnosis worse

  • Do not skip a mandatory generation to make recovery continue.
  • Do not guess range endpoints from filenames alone.

Acceptance criteria for a fix

A useful regression test should force the condition “the configured upper or ending restore generation is below a log that the restore set requires”, call one documented API transition, and assert the exact HRESULT.

Technical references


Looking for a different code? Search another status or error code.

Exit mobile version