| Previous | Next |
| hrBackupDirectoryNotEmpty | hrMissingPreviousLogFile |
hrBackupInProgress
Operational meaning
hrBackupInProgress means an external backup session is already active for the relevant ESE instance.
The stored value is 0xC80001F9 (negative JET error -505; -505). 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 identifying the owner, start time, current open file, phase, and whether stop/end cleanup has been requested.
Before altering files or retrying
- Code-specific observation: identify the owner, start time, current open file, phase, and whether stop/end cleanup has been requested.
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 |
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 condition | 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 condition by identifying the owner, start time, current open file, phase, and whether stop/end cleanup has been requested.
- Apply only the targeted fix: finish or abort the active backup through its documented end path before starting another.
Actions that can make diagnosis worse
- Do not omit the final end/abort path.
- Do not continue using a context after a sequence failure.
Technical references
- Begin external backup — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- Enumerating backup logs
- End external backup
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.