Creating a single backup

In this case, we are looking to back up a single dataset, say “ontology”, rather than the entire collection of datasets.

Example Call

Note: The dataset name is passed as a path suffix to the backup endpoint. If it is incorrect, the call will return an error.

Second, an optional description field. This allows more meaning to be added to the snapshot taken - in this case that it’s Jeff’s backup.

Naturally, backing up a single dataset is faster than backing up all datasets.

curl -s -X POST  --header "Authorization: ${TC_OIDC_TOKEN}" --data "description=Ontology backup by Jeff" --location 'https://telicent.core.domain/api/sparql/backups/create/ontology'

Response

The response returned is similar to that described here but with only a single dataset’s details (“ontology”) and a new ID - 4.

Click here to see response

```json { "id" : "/ontology", "date" : "2025-06-26_18-58-22", "user" : "jeff.tester@demo.co.uk", "description" : "Ontology backup by Jeff", "backup" : { "backup-id" : 4, "date" : "2025-06-26_18-58-22", "datasets" : [ { "dataset-id" : "ontology", "tdb" : { "folder" : "/fuseki/backups/4/ontology/tdb/", "success" : true, "files" : { "files" : [ "ontology_backup.nq.gz" ] } }, "kafka" : { "folder" : "/fuseki/backups/4/ontology/kafka/", "/ontology" : [ { "name" : "ontology", "source" : "/fuseki/databases/Replay-Ontology-RDF.state", "destination" : "/fuseki/backups/4/ontology/kafka//ontology.json", "success" : true } ], "files" : { "files" : [ "ontology.json" ] } }, "labels" : { "folder" : "/fuseki/backups/4/ontology/labels/", "success" : true, "files" : { "meta" : { "files" : [ "1" ] }, "private" : { "1" : { "files" : [ "OPTIONS-000012", "MANIFEST-000010", "000009.log", "CURRENT" ] } }, "shared_checksum" : { "files" : [ "000008_s6L1QU9I29RZSDZ2TN8SF_2992501.sst" ] } } } } ] } } ```