New backup and restore operations #51

New issue

Open

opened 2026-03-16 20:09:01 +00:00 by scossu · 0 comments

scossu commented

2026-03-16 20:09:01 +00:00

Owner

Backup and restore are still possible with standard UNIX tools, but Pocket Archive should offer a one-step, complete backup operation and a matching restore operation:

The metadata backup is done on the raw DB instead of exporting to RDF (less chances of data corruption without RDF encoding)
Verify checksums as part of the copy process (as the old backup tools is already doing).
A double check of the destination files against the source checksum and the one stored in the DB may provide an additional integrity check.
Configuration, data, and DB are backed up and restored as a unit.

Separately from this, #26 provides a metadata export to RDF with a different purpose, i. e. data manipulation and import into foreign systems.

The current backup and restore operations won't work with the new metadata store that uses named graphs. A TriG decode function in Volksdata is in progress but it will take a while to implement and test. Because of that, the current backup and restore CLI commands are being disabled. Backup and restore are still possible with standard UNIX tools, but Pocket Archive should offer a one-step, complete backup operation and a matching restore operation: - The metadata backup is done on the raw DB instead of exporting to RDF (less chances of data corruption without RDF encoding) - Verify checksums as part of the copy process (as the old backup tools is already doing). - A double check of the destination files against the source checksum and the one stored in the DB may provide an additional integrity check. - Configuration, data, and DB are backed up and restored as a unit. Separately from this, #26 provides a metadata *export* to RDF with a different purpose, i. e. data manipulation and import into foreign systems.