| Previous | Next |
| hrMissingFullBackup | hrTermInProgress |
hrBadBackupDatabaseSize
The exact condition reported here
hrBadBackupDatabaseSize means the backed-up database file length is not aligned to the database page-size boundary expected by ESE.
The stored value is 0xC8000231 (negative JET error -561; -561). Current ESE documentation uses JET_errBadBackupDatabaseSize for the corresponding published JET condition.
The first useful distinction is that the legacy message names 4 KiB, while modern ESE documentation describes alignment to the database page size. Start by recording exact byte length, page size from metadata, transfer byte counts, final chunk size, storage object length, and hashes.
Objects and state involved
| Diagnostic layer | database, patch, log, and backup metadata that establish one recoverable lineage |
|---|---|
| Relevant API surface | hard recovery, database-header inspection, patch application, and post-restore validation |
| Code-specific condition | the backed-up database file length is not aligned to the database page-size boundary expected by ESE |
| Narrow corrective direction | recopy the complete file and verify length and hash; never pad or truncate a database to force alignment |
A hard-recovery failure leaves the restored database invalid; retry begins from a fresh restored copy. Database state, signature, page size, consistent time, and required logs must agree.
Adjacent conditions
This result specifically means that the legacy message names 4 KiB, while modern ESE documentation describes alignment to the database page size. Related values below can appear in the same workflow but require a different response:
hrPatchFileMismatch | the database patch file was not generated from the backup database being restored |
|---|---|
hrDatabaseInconsistent | the database is not in a clean transaction-consistent state and requires recovery before normal use |
hrConsistentTimeMismatch | the database last-consistent timestamp does not match the recovery or backup lineage being applied |
Diagnostic record
- Code-specific observation: record exact byte length, page size from metadata, transfer byte counts, final chunk size, storage object length, and hashes.
- Backup identity and restore map: capture the value and timestamp from the first occurrence.
- Required log positions: capture the value and timestamp from the first occurrence.
- Database header and state: capture the value and timestamp from the first occurrence.
- Signatures, page size, and hashes: capture the value and timestamp from the first occurrence.
Actions that can make diagnosis worse
- Do not modify the only backup copy in place.
- Do not attach a dirty or mismatched database as if it were clean.
Corrective path
- Record it,
0xC8000231, the API name, the current phase, and all live context or file owners. - Verify the condition by recording exact byte length, page size from metadata, transfer byte counts, final chunk size, storage object length, and hashes.
- Apply only the targeted fix: recopy the complete file and verify length and hash; never pad or truncate a database to force alignment.
Technical references
- JetExternalRestore behavior — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- Database header information
- ESE error-code table
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.