Page Comparison

...

#!/bin/bash
echo "Backup Script for Exporting Ontology from Graph Database Using enapso-graphdb-cli"

# Set Variables
DB_URL="http://localhost/fuseki"
REPOSITORY_NAME="Test"
FORMAT="application/x-trig"
EXPORT_FILE="export.trig"
REPORT_FILE="report.txt"
TRIPLESTORE="fuseki"
CONTEXT="http://ont.enapso.com/views"
# Remove Previous Report File
echo "Removing Previous Report File..."
rm $REPORT_FILE

# Export ontology
enapsogdb export --dburl $DB_URL --repository $REPOSITORY_NAME --targetfile $EXPORT_FILE --context $CONTEXT --triplestore $TRIPLESTORE  >> $REPORT_FILE 2>&1

echo "Backup made successfully"

...

1. DB_URL: URL where the triplestore is running.

2. REPOSITORY_NAME: Name of the repository.

3. FORMAT: Data format, For Fuseki, the data is only returned in the application/x-trig format, so specifying the format is not necessary. For other triplestores like GraphDB and Stardog, the recommended format is application/x-trig due to its support of named graphs.

4. EXPORT_FILE: Path and filename for the backup file.

5. REPORT_FILE: Path and filename for the report file, which contains the response from the script's execution.

6. TRIPLESTORE: Type of the triplestore (fuseki, graphdb, stardog).

7. CONTEXT: Context to be exported. If left empty, the entire repository is exported. If a string is provided, it saves the context's data. If an array of contexts is provided, it creates a zip file containing each context's data.

Context Exporting Details

1. Without Context:

   • For Fuseki: Exports the entire repository in application/x-trig format.

   • For GraphDB and Stardog: Exports the whole repository in the specified format.

2. With Context as String:

   • For Fuseki: Exports the specified context in text/turtle format.

   • For GraphDB and Stardog: Exports the specified context in the provided format.

3. With Context as Array:

   • For Fuseki: Exports each context in text/turtle format and saves them in a zip file.

   • For GraphDB and Stardog: Exports each context in the provided format and saves them in a zip file with each file named its context.

Save the Script

1. Save the file with a .sh extension, such as backup_script.sh.

...

Include this step if you use the ENAPSO platform because it is necessary for the cache mechanism. When you upload data, you need to create a cache because the information about the class model for auto-generating templates or managing templates is retrieved from the cache, not directly from the graph database repository. If you do not create a cache and upload the ontology, and there is a class for which you want to create an auto CRUD template, you will be unable to create it and got an error message because the cache will not have information about that class.This enhanced documentation provides clear instructions and additional context for using the enapso-graphdb-cli tool effectively, ensuring users can manage their graph databases with confidence.

Conclusion

Regular backups and effective restoration capabilities are essential for managing graph database repositories securely. Using the enapso-graphdb-cli tool, users can easily safeguard their data and restore it quickly if necessary. It's important to maintain a consistent backup routine and periodically test your restoration process to ensure data integrity and minimize downtime.

...