Viewing backup details

We can check a given backup’s size, path, date and time of creation, and time it took to create it.

Example Call

curl -s -X GET -H "Authorization: $TC_OIDC_TOKEN" https://telicent.core.domain/api/sparql/backups/details/1

Response

The response below describes backup “1”.

Click to expand JSON response

```json { "backup-id": "1", "date": "2025-07-30_07-23-32", "details": { "backup-id": "1", "details-path": "/fuseki/backups/1", "zip-size-in-bytes": 604, "zip-size": "604 bytes", "start-time": "2025-07-29T09:20:46.269040089Z[GMT]", "end-time": "2025-07-29T09:20:46.282842172Z[GMT]", "backup-duration": "13ms", "backup-duration-in-ms": 13 } } ```

Overall Response

The response can be broken down to

Date & Time of the call and backup ID.
The details of the backup.

If the requested backup has no readable ZIP archive, the details object will consist of only the backup ID and path, like so:

{
  "backup-id": "10000000",
  "date": "2025-07-30_07-41-18",
  "details": {
    "backup-id": "10000000",
    "details-path": "/fuseki/backups/10000000"
  }
}

Backup details fields

backup-id — the requested backup ID.
details-path — the base filesystem path for the backup; the ZIP archive has a .zip suffix.
zip-size-in-bytes and zip-size — the archive size in bytes and a readable size.
start-time and end-time — when backup creation started and finished.
backup-duration and backup-duration-in-ms — the elapsed creation time, as text and milliseconds.
kafka-state — Kafka state read from the ZIP archive, when available.

The outer date is the time of the details request, not the backup creation time. Timing fields appear only when the corresponding metadata is available. Older backups may therefore return size fields without timing fields.

The details endpoint reads an unencrypted .zip archive. A backup stored only as .zip.enc can return just its ID and base path; this does not establish that the backup is missing. Use the list operation to find available backups.