What Does It Back Up?

Each backup produces a timestamped ZIP archive — something like omeka backup-20240115-103000.zip — containing up to three components, all configurable:

• Database dump (db.sql) — a complete SQL dump of every table and view in your MySQL database. This is done entirely through PHP using your existing database connection, so there's no dependency on mysqldump being installed on the server. Data is streamed row-by-row to keep memory usage flat even on large collections.

• Files (files/) — a copy of Omeka's entire files directory, including originals, thumbnails, and all derivative sizes.

• JSON-LD API export (export/) — a set of JSON files produced by Omeka's own API, one per resource type: items, item sets, media files, vocabularies, resource templates, properties, resource classes, and sites. This export isn't used for restore (Omeka doesn't have a bulk import API), but it's invaluable as a portable, human-readable snapshot of your data that can be read, searched, or imported into other systems.

• A metadata.json manifest is always included, recording the module version, creation timestamp, and which components are present — so you can inspect any archive and know exactly what's inside without extracting it.