In this section · 5 articles

Restore a backup

Check that a backup is healthy with a dry run, then put your Laramin's database, uploaded files or both back to how they were when the backup was made.

Applies to
Backup 1.1 and later
Who can do this
Platform owner
Permission
feature.backup.backup.restore
Where
Backups › Backups History
On this page

Danger: A restore replaces the live database and uploaded files with the ones in the backup. Everything people added or changed after the backup was made is lost: new records, edits, new users, and password changes. You can't undo a restore from this screen. Make a fresh Full backup first, so you can go back if you need to.

Before you start

  • You need Restore Backup (feature.backup.backup.restore). Super admins have it.
  • A real restore runs as a background job. Make sure the queue worker is running. Queue & Worker Status on Extra Utilities shows the jobs waiting to run. A dry run doesn't need it.
  • Make a Full backup of how things are now. See Make a backup now and download it.
  • Tell the people who use your Laramin, and ask them to stop working until you're done. You may want to turn on maintenance mode.
  • The backup's archive must still be on your Laramin's server. Laramin restores from that copy only, never from a copy in cloud storage.

What a restore changes

Backup typeWhat the restore puts back
FullThe database and the uploaded files.
DatabaseThe database only.
FilesThe uploaded files only.
IncrementalThe uploaded files only. Laramin first applies the full or files backup the incremental one was based on, then the incremental one, and deletes the files it records as deleted.

An encrypted archive is opened with the Archive Password saved in Backup settings. If you changed that password since the backup was made, put the old one back before you restore.

Careful: An Incremental restore skips any incremental backups made between the base backup and the one you chose. A file that changed only in one of those comes back as it was in the base backup.

Some things are never restored, so they stay as they are now: the background job queue, the cache, sign-in sessions, and the list of backups and restores. Uploaded files that were added after the backup are kept. Restoring overwrites files that exist in the backup, but doesn't delete the newer ones.

Steps

1. Run a dry run

A dry run checks the archive without changing anything. It checks that the file exists, can be read, matches the checksum recorded when it was made, opens as a ZIP archive (with the Archive Password, if it's encrypted), and holds what a restore of its type needs. It then reads back every part the restore would use and checks that it comes out intact.

  1. In the sidebar, open Backups › Backups History.

  2. In the row of the backup you want, open the row actions menu.

  3. Select Restore. This only appears for a backup whose status is Completed or Partial.

  4. Check the name next to Target backup:.

  5. Leave Run a dry-run integrity validation first (recommended) turned on.

  6. In Confirmation Code, type RESTORE in capital letters.

  7. In Confirm Your Password, enter the password you sign in with.

  8. Select Run Dry-Run.

The dialog stays open and shows each check under Validation Output. If the archive passed, the last line says Validation completed. Archive is healthy. If it didn't, you see Integrity dry run failed: and the reason. Don't restore a backup that fails the dry run.

2. Restore

  1. In the same dialog, turn off Run a dry-run integrity validation first (recommended).

  2. Check that Confirmation Code still says RESTORE and your password is still entered.

  3. Select Restore Now.

You see Real restoration process queued in the background. Monitor progress in history log. The dialog closes.

If the code or the password is wrong, you see Password or confirmation code does not match with your profile. Nothing is changed.

What happens next

  1. Laramin unpacks the backup and checks every part of it. If anything is wrong, the restore stops here with Failed, and the process log says Nothing was changed: the restore stopped before applying any data.
  2. Before it changes anything, Laramin makes its own copy of what it is about to replace, for each part the restore touches.
  3. It then applies the backup.
  4. When it finishes, the Backups History screen shows a message such as Restore “backup-2026-11-07-10-30-00-a1b2c.zip” completed.

Open Backups › Restore Logs to follow it. Each restore, and each dry run, has a row with its Status:

StatusMeaning
PendingWaiting for the queue worker.
ProcessingThe restore is running.
CompletedThe backup was applied in full.
Rolled BackThe restore failed partway, and Laramin put back the copy it made first. Your Laramin is as it was before the restore.
FailedThe restore failed. Either it stopped before changing anything, and the process log says Nothing was changed, or it failed partway and Laramin couldn't put everything back.
Dry Run OK / Dry Run FailedThe result of a dry run. Nothing was changed.

To see each step, open the row actions menu and select View Process Log.

Careful: If a restore shows Failed and its process log doesn't say Nothing was changed, your data may be half restored. Read the process log, then restore the Full backup you made before you started. If that fails too, raise a ticket from Support Center in your Laramin app.

After a restore that touched the database, everyone's account, password and permissions are as they were when the backup was made. So are all settings, including maintenance mode and the Backup module's own settings. If you changed your own password since then, sign in with the old one.

A dry run checks only the archive you chose. For an incremental backup, it doesn't check the backup it was based on. Before you rely on a backup, try a restore on a copy of your Laramin.