Backing up a repository¶

Several options are available:

Option 1: Using the GraphDB Workbench

Export the database contents using the GraphDB Workbench. To preserve the contexts (named graph) when exporting/importing the whole database, use a context-aware RDF file format, e.g., TriG.

1. Go to Data -> Export
2. Choose the files you want to export.
3. Click Export graph as TriG.

Option 2: Exporting the data of each repository

1. Export the data of each repository, while the database is running.

   Note

   All updates executed after the EXPORT had been started will not be put in the exported data (due to the READ COMMITTED transaction isolation in GraphDB).

2. Shutdown the database (stop Tomcat) and delete the older GraphDB application(s) – .war files and the expanded folder.

Option 3: Using the graph store protocol and curl

This can be achieved on the command line in a single step using the graph store protocol (change the repository URL and name of the export file accordingly).

curl -X GET -H "Accept:application/x-trig"
"http://localhost:7200/repositories/test_repo/rdf-graphs/service?
graph=http://www.ontotext.com/explicit"  >  export.trig

Option 4: Programmatically using the Sesame API.

Use the RepositoryConnection.exportStatements() method with the includeInferred flag set to false (in order not to serialise the inferred statements).

Example:

RepositoryConnection connection = repository.getConnection();
FileOutputStream outputStream = new FileOutputStream(new File("/tmp/test.txt"));
RDFWriter writer = Rio.createWriter(RDFFormat.NTRIPLES, outputStream);
connection.exportStatements(null, null, null, false, writer);
IOUtils.closeQuietly(outputStream);

Use the RepositoryConnection.getStatements() method with the includeInferred flag set to false (in order not to serialise the inferred statements).

Example:

java.io.OutputStream out = ...;
RDFWriter writer = Rio.createWriter(RDFFormat.NTRIPLES, out);
writer.startRDF();
RepositoryResult<Statement> statements =
repositoryConnection.getStatements(null, null, null, false);
while (statements.hasNext()) {
    writer.handleStatement(statements.next());
}
statements.close();
writer.endRDF();
out.flush();

The returned iterator can be used to visit every explicit statement in the repository and one of the Sesame RDF writer implementations can be used to output the statements in the chosen format. If the data will be re-imported, we recommend the N-Triples format as it can easily be broken into large ‘chunks’ that can be inserted and committed separately.

Option 5: Copying GraphDB storage folders

1. Stop GraphDB/Tomcat.

2. Manually copy the storage folders to the backup location.

   kill <pid-of-graphdb>
   sleep 10 #wait some time for the graphdb to stop
   cp -r {your data directory}/repositories/your-repo ~/your-backups/TODAY-DATE/
   

Restoring a repository¶

Several options are available:

Option 1: Importing data with preserved contexts in Sesame Workbench

1. Go to Add.
2. Choose Data format: TriG.
3. Choose RDF Data File: e.g., export.trig.
4. Clear the context text field (it will have been set to the URL of the file). If this is not cleared, all the imported RDF statements will be given a context of file://export.trig or similar.
5. Upload.

Option 2: Importing data with preserved contexts in GraphDB Workbench

See Load your data.

Option 3: Replacing the GraphDB storage directory (and any subdirectories)

1. Replace the entire contents of the storage directory (and any subdirectories) with the backup.
2. Restart the repository.
3. Check the log file to ensure a successful start up.