| Previous | Next |
| hrBackupDirectoryNotEmpty | hrMissingPreviousLogFile |
hrBackupInProgress
Operational meaning
For hrBackupInProgress, the useful interpretation begins with the object and phase that returned the value. The decisive boundary is an external backup session is already active for the relevant ESE instance.
The stored Value is 0xC80001F9 (negative JET error -505; -505). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errBackupInProgress for the corresponding published JET condition.
The first useful distinction is that this is ESE instance backup exclusivity; hrRestoreInProgress indicates the competing workflow is restore. Start by identify the owner, start time, current open file, phase, and whether stop/end cleanup has been requested. That separates a reproducible incident from a later generic cleanup or service error.
Before altering files or retrying
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: identify the owner, start time, current open file, phase, and whether stop/end cleanup has been requested.
- Database/log enumeration transition: record it together with this result and the timestamp of the first occurrence.
- Ordered API trace: record it together with this result and the timestamp of the first occurrence.
- Instance and active backup owner: record it together with this result and the timestamp of the first occurrence.
- Open backup file handles: 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.
Comparison points
It specifically means that this is ESE instance backup exclusivity; hrRestoreInProgress indicates the competing workflow is restore. Related values below can appear in the same workflow but require a different response:
hrNoBackupDirectory | the external-backup operation has no destination directory configured for its temporary or copied artifacts |
|---|---|
hrInvalidBackupSequence | backup APIs were called in an order that violates the ESE external-backup state machine |
hrNoBackup | a backup-only API was called when no external backup session is active |
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.
Objects and state involved
| Diagnostic layer | the ESE external-backup state machine and its single active session |
|---|---|
| Relevant API surface | JetBeginExternalBackup, JetGetAttachInfo, JetOpenFile/ReadFile/CloseFile, JetGetLogInfo, and JetEndExternalBackup |
| Code-specific boundary | an external backup session is already active for the relevant ESE instance |
| Narrow corrective direction | finish or abort the active backup through its documented end path before starting another |
Database files are enumerated and copied before the backup advances to the log-file phase., the engine tracks outstanding backup file handles and rejects calls made in the wrong phase.
Recommended handling
- Record it,
0xC80001F9, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by identify the owner, start time, current open file, phase, and whether stop/end cleanup has been requested.
- Apply only the narrow correction: finish or abort the active backup through its documented end path before starting another.
- 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
Actions that can make diagnosis worse
- do not omit the final end/abort path.
- do not continue using a context after a sequence failure.
- 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
- Begin external backup — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- Enumerating backup logs
- End external backup
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.