Binary database dump
Required for production system During recovery, past binary logs are replayed for database recovery. Sample cron entry on Unix: Dump the tables in an transaction. Later changes by other sessions will not be seen. It ensure tables are not modified and therefore remain consistence during the dump.
Flushes and rotates the binary logs at the moment of the full backup mysqldump. This information is needed for data replication or point-in-time recovery It performs a full DB backup. Any data changes made after it is logged in log-bin.
To invoke the export repository operation several interfaces are available:. Export the repository with the GraphDB Workbench. Export the database contents using the Workbench. Export all statements with curl. The same operation can be executed once with Java code by calling the RepositoryConnection.
The returned iterator can be used to visit every explicit statement in the repository and one of the RDF4J RDF writer implementations can be used to output the statements in the chosen format. This is the fastest method to backup a repository, but it requires stopping the database. For more information about the data directory, see here. All RDF data is stored only in your repository. Previous versions GraphDB 8. Export the repository to an RDF file - this operation can run in parallel to read and write, but it takes more time to complete.
Copy the repository image directory to a backup - this is a much faster option, but in non-cluster setups it requires to shutdown the database process. Note We recommend all repository backups to be scheduled during periods of lower user activities. To invoke the export repository operation several interfaces are available: Choose the files you want to export.
Click Export graph as TriG.