Skip to end of metadata
Go to start of metadata

Page Contents


Backup Enterprise Data Governance

  1. Stop your EDG server, because the backup must occur offline.
  2. Backup your entire workspace, by performing a tar or zip operation on it.
  3. Backup your configured database (TDB, RDBMS, or MarkLogic). Note: This step depends on what persistence store you have configured, e.g., see your RDBMS manufacturer's website for more information. NOTE: Be sure to backup the correct database/schema, as configured for your EDG server per EDG Administration: Configuring the active database type for new asset collections.
  4. Store these two files together offline.
  5. Start EDG backup once all of the above steps have been completed.

Restore Enterprise Data Governance

  1. Stop EDG server.
  2. Locate and delete your current EDG workspace. The workspace location is stored in the web.xml file.
  3. Replace the existing EDG workspace with your backed-up copy.
  4. Restore your database from the backup.
  5. Before starting EDG confirm that your EDG is set up to point at your newly restored database. This can be done by editing  [Workspace]/server.topbraidlive.org/dynamic/config.ttl and confirming settings, e.g., the URL points at the newly restored database.
  6. Start EDG server.

Backup data stored in TDB databases

It is possible to take a filesystem copy of these databases if the EDG server is stopped. If the server is running, the database snapshot may be invalid.

Live Data Backup of A Shared Graph TDB

In addition to the backup procedures described above for a complete server backup, it is possible to backup server-held data for data held in shared TDB-backed storage and the Data Platform EDG cache database can be backed up during normal operation of the EDG server. 

NOTE: This only creates a back up of the data stored in <workspace>/_Data/TDB/, the connector (.xdb) files will need to be backed up separately.

This is provided with a web API for scripts to invoke.

The backup service is available to administrators at:

Backup API
/tbl/backup

and is accessed with an HTTP POST request (and not an HTTP GET request).

It is also possible to focus on a single graph:

Backup One Graph
/tbl/backup?graph=TheGraphURI

Example: to capture all graphs held in the shared graph TDB database of the local server:

curl -v -XPOST 'http://localhost:8080/tbl/backup?storage=xdb' --output test.trig

Example: to capture all graphs held in the database for the Data
Platform:

curl -v -XPOST 'http://localhost:8080/tbl/backup?storage=dp'

In each case, the result is a RDF file in standard RDF TriG format with addition information for restoring per-graph prefixes if required.

To restore:

  1. Stop the EDG server.
  2. Make sure you have Jena 3.7.0 installed and added to your PATH (OSX/Linux) or your Environment Variables (Windows).
  3. Use tdbloader from the Apache Jena TDB tools to build a TDB database (example below).
  4. Replace the database in the EDG deployment.
  5. Restart the server.

Example: to build a new database with the exported trig file above:

tdbloader --loc /your/database/location/_Data/TDB test.trig 

NOTE: This just restores the database, the connector (.xdb) files should be restored separately into the relevant project folder (Repositories) location.

The database locations are:

StorageLocation
Shared graph TDB (XDB) storage
<workspace>/_Data/TDB/
Data Platfrom EDG cache storage
<workspace>/_Data/dp-cache.tdb

 

Per-graph prefixes can be restored by creating an RDF Turtle with just the prefixes loading that file into the graph. 

Backup and Recovery of Supported Relational Databases (RDBMS)


  • No labels