Warning: Restoring overwrites your current database and/or files. This cannot be undone. Take a fresh backup of your current state and download it first if you want a fallback.

Restore from a backup in the list#

1. Go to Admin > Backup and click Restore next to the backup you want.
2. A dry-run preview page shows exactly what actions will be performed (which database and which files path will be overwritten).
3. Choose whether to restore the database, the files, or both.
4. Type RESTORE (all caps) in the confirmation field and submit.
5. The restore runs as a background job. Monitor progress via the job link in the success message. The module verifies the SHA-256 checksum of the ZIP before touching anything. If the file has been modified or corrupted since it was created, the restore is aborted.

Upload and restore a backup from another server#

1. Click Upload Backup on the backup list page.
2. Select a .zip file that was previously created by this module (it must contain metadata.json).
3. The file is imported into the backup library. You can then restore it using the same steps above.
4. This is the recommended way to migrate an Omeka S installation to a new server.

From the command line#

## List backups to find the ID you want
php modules/Backup/bin/backup.php restore 5

# Restore database only
php modules/Backup/bin/backup.php restore 5 --no-files

# Restore files only
php modules/Backup/bin/backup.php restore 5 --no-db

The CLI will print a dry-run summary and prompt you to type RESTORE before proceeding.