HEART data.backup-failed H-10004
Backup failed. A backup did not complete.
| Code | HEART data.backup-failed; inside a message "code": "data.backup-failed" |
|---|---|
| H-number | H-10004: area 10, code 004 |
| Area | data: Data quality, sync, backups |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Servers, gateways and products that keep backups |
Likely causes
- No space left where backups are stored.
- The backup target, such as a server or cloud bucket, cannot be reached.
- Credentials for the backup target expired or were changed.
- Files locked or changing while the backup ran.
- The source storage is failing, so reading it fails.
How to fix or prevent it
- Read the alert: it gives the reason.
- Check space and access at the backup target.
- Renew credentials if they expired.
- Run the backup again by hand, and check that it completes.
- To prevent it: test a restore from time to time. A backup that has never been restored is not proven.
What the HEART does by itself
It raises a warning with the reason. A Playbook may try the backup again later, within its guards. It resolves after the next good backup.
When to call service
If backups keep failing for more than a day or two, or the data cannot be lost.
Related codes
storage.fullH-04002: Storage fullconnectivity.dependency-unreachableH-03003: A service it relies on cannot be reachedstorage.wearing-outH-04004: Storage wearing out
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)