| Previous | Next |
| hrDeleteBackupFileFail | hrInvalidBackup |
hrMakeBackupDirectoryFail
Operational meaning
hrMakeBackupDirectoryFail means ESE could not create the temporary directory required by the backup workflow.
The stored value is 0xC800020D (negative JET error -525; -525). Current ESE documentation uses JET_errMakeBackupDirectoryFail for the corresponding published JET condition.
The first useful distinction is that hrNoBackupDirectory means no path was supplied; this code means creation at a supplied location failed. Start by capturing the resolved parent path, service identity, ACLs, free space, path length, filesystem type, and Win32 error.
Before altering files or retrying
- Code-specific observation: capture the resolved parent path, service identity, ACLs, free space, path length, filesystem type, and Win32 error.
Comparison points
It specifically means that hrNoBackupDirectory means no path was supplied; this code means creation at a supplied location failed. Related values below can appear in the same workflow but require a different response:
hrDeleteBackupFileFail | backup cleanup could not delete an artifact it was responsible for removing |
|---|---|
hrGivenLogFileIsNotContiguous | the logs supplied from backup media contain a mandatory generation gap |
hrBackupDirectoryNotEmpty | the selected backup destination contains artifacts that would make the new set ambiguous |
Objects and state involved
| Diagnostic layer | temporary backup directories, copied artifacts, cleanup ownership, and final status |
|---|---|
| Relevant API surface | external backup setup/teardown and filesystem operations around copied files |
| Code-specific condition | ESE could not create the temporary directory required by the backup workflow |
| Narrow corrective direction | correct the parent directory and permissions, then restart the entire backup session |
Cleanup errors can leave a destination that is unsafe for the next backup attempt. A cleanup path must distinguish artifacts owned by the current job from prior verified backups.
Recommended handling
- Record it,
0xC800020D, the API name, the current phase, and all live context or file owners. - Verify the condition by capturing the resolved parent path, service identity, ACLs, free space, path length, filesystem type, and Win32 error.
- Apply only the targeted fix: correct the parent directory and permissions, then restart the entire backup session.
Acceptance criteria for a fix
A useful regression test should force the condition “ESE could not create the temporary directory required by the backup workflow”, call one documented API transition, and assert the exact HRESULT.
Actions that can make diagnosis worse
- Do not hide cleanup failure behind the original successful copy status.
- Do not recursively delete a destination whose provenance is unknown.
Technical references
- ESE backup error codes — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- Begin external backup
- End external backup
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.