Improve backup support

[der]

Should have option to create a complete store dump in a portable format.

Either directly or by migrating to a manageable separate storage service like Fuseki.

[der]

Current implementation supports a "schedule backup" admin action which creates a compressed nquads dump.

[dr-shorthair]

So how to use this to restore?

[dr-shorthair]

Can you point to documentation for scheduled & ad-hoc backup.

[der]

Looks like the documentation is out of date.

Short summary is that "POST" to the endpoint {registry}/system/backup will trigger a backup of the database which will then run as a background task.

The UI calls an internal service to check the status of the backup task. There is currently no REST endpoint for checking backup status but there probably should be.

In the deployed systems a cron job uses curl to trigger a backup at regular intervals.

The backup is a compressed nquads file in /var/opt/ldregistry/backup (location configurable on services.conf). It can be restored by using the jena utilities tdbloader or tdbloader2 to create a loaded database, then install that at /var/opt/ldregistry/store or wherever you have the store configured.

Re:opening issue since the documentation needs doing properly.

[der]

Updated documentation: https://github.com/UKGovLD/registry-core/wiki/Operation#backups