Restoring Backups

Click Restore next to an archive. The restore page shows what the archive holds (the site, when and on which Omeka version it was made, its tables, items, files and theme) and what a restore will do here.

Before you restore#

The page warns about anything to sort out first:

• Plugins the site uses that are not installed here. Their records come back with the database, but their content shows only once the plugin is installed. Install them before or after restoring.
• A theme that is not installed here. The site keeps its current theme until you install the archive's theme and choose it under Appearance.
• An older Omeka version. After the restore, sign in: Omeka asks to upgrade the database, as after any Omeka upgrade.
• Plugin and theme folders in the archive. A restore never installs code; copy the folders you need from the archive, or install them the usual way.

Restoring is refused when the archive was made on a newer Omeka version than this site runs (upgrade Omeka here first), when the files would not fit on this server, or when the archive has not passed its check.

Restoring#

Choose what to restore:

• Database: replaces this site's tables with the archive's.
• Files: stores the archive's files through this site's storage, replacing files with the same names.
• Back up this site first (on by default): a full backup, listed as "Before restoring …", so you can go back.

Type RESTORE and click Restore. The restore runs in the background:

1. An archive kept in cloud storage is copied to the server. The archive's checksum is compared with the one recorded when it was added, and every file in it is read and checked against the ZIP's checksums. Nothing changes if one does not match.
2. The backup of this site is made, if chosen.
3. The database is loaded. When the archive's tables have another prefix than this site's (omeka_ and wren_, say), they are renamed as they load.
4. The files are stored, one at a time, through this site's storage: on disk, or uploaded to cloud storage.

Recent restores on the Backups page shows the progress and, when it is done, what was restored.

After the restore#

• Everyone is signed out. The accounts are now the archive's: sign in with one of them. The page you were on says so when it happens.
• This server keeps what belongs to it: this list of archives and the restore history, Backup's settings, the ImageMagick path, and the records of this plugin and of the hosting storage adapter, so the site goes on working.
• Tables the archive does not have are left alone, such as those of a plugin installed here after the archive was made.
• Files are added, not cleared. Files already here that the archive does not have stay where they are.