An archive holds everything needed to set a site up on another server: its database and files, and, if you include them, its plugin and theme folders. It restores whatever each server uses for file storage, and whatever table prefix each uses.
Steps
- On the new server, install Omeka Classic (the same version as the old site, or newer) and the Backup plugin, and install the plugins and theme the site uses.
- On the old site, install Backup if it is not there, go to Backups and click Back up now with Database and Files ticked. Add Plugins and themes if the new server cannot get them otherwise.
- Bring the archive across, in whichever way suits its size:
- From a link (best for any size): on the old site, click Get download link next to the archive and copy the link. On the new site, paste it under Bring in an archive > From a link and click Download. The new server downloads the archive directly, resuming if the connection drops. See Download Links.
- Upload: download the archive to your computer from the old site, then on the new site choose it under Bring in an archive > Upload. It goes up in pieces, so the server's upload limit does not stop it, and a dropped connection is retried.
- Copied to the server: for very large archives, copy the ZIP into the new site's backup directory (shown on the Backups page) with SFTP or FTP, in binary mode. It appears under Copied to the server: click Add, which moves it into a folder with a random name. Until then it is under its own name, so where the files folder is served publicly, add it soon or use a backup directory outside the web root. (On a site that keeps archives in cloud storage, set a backup directory under Settings first.)
- Wait until it is checked. Every archive brought in is read file by file and checked against the ZIP's checksums before it can be restored.
- Click Restore, read the page, type
RESTOREand click Restore. See Restoring Backups. - Sign in again with an account from the old site, once the restore has finished. If the old site ran an older Omeka version, Omeka asks to upgrade the database: click Upgrade.
Moving to or from cloud storage
Nothing changes in the steps. An archive made on a server that keeps files on disk restores into cloud storage, file by file through the new site's storage, and an archive made from cloud storage restores to disk. File names and paths stay the same, so every link to a file keeps working on the new site.
The new server's own storage settings, its ImageMagick path and this plugin's settings are kept; the site's settings, accounts and content come from the archive.
Restoring without the plugin
Every archive also restores by hand, without the plugin (see the README.txt inside it):
- Load
database.sqlwith the mysql client:mysql -u USER -p DATABASE < database.sql. - Set
prefixindb.inito the prefix in the archive's manifest (for exampleomeka_). - Copy the
files/folder into Omeka'sfiles/folder, and theplugins/andthemes/folders, if included, into Omeka's.
Keep the old site until the new one works
Check the new site (items, files, exhibits, pages, theme) before you close the old one.