How to Restore a Backup Safely Print

The restore tool on the Admin page lets you upload a backup package and replace matching data inside the panel. Because restore actions can overwrite live configuration, it should always be treated as a deliberate recovery or migration step.

When to Use This

• You need to recover from a bad change.
• You are moving a known-good configuration between panels.
• You want to restore settings after a failed update or experiment.
• You need a safe checklist before using the restore form.

Important Warning

Restore actions overwrite matching data sets inside Cockpit. Only use a backup package you trust and only when you understand what you are replacing.

Steps

1. Open the Admin page.
2. Go to the Restore Configuration area.
3. Confirm the backup archive you plan to upload is the correct one.
4. Use the file input to choose the backup package.
5. Read the warning message shown next to the restore form.
6. Click Upload & Restore.
7. Wait for the restore process to finish before navigating away.
8. Reload the panel and verify the pages or settings you expected to recover.

Expected Result

After a successful restore, the panel should reflect the contents of the uploaded backup for the matching components it replaced.

Before You Restore

• Take a fresh backup of the current live state first whenever possible.
• Make sure you know the age and purpose of the backup package.
• Do not mix recovery work with unrelated changes during the same session.
• If this is a production panel, tell other operators what you are about to overwrite.

Common Mistakes

• Uploading the wrong archive: Double-check the file before starting the restore.
• Skipping a pre-restore backup: If the result is not what you expected, you will want a way back.
• Using restore as a casual test tool: Restore should be treated as a recovery or controlled migration action.
• Not verifying the panel afterward: Always recheck the sections you expected to recover.

Example Use Cases

• Recovery after a mistake: An operator changes settings in the wrong direction and restores a known-good package from earlier that day.
• Migration: A reseller moves a stable panel setup into a new environment and restores matching configuration data from backup.
• Testing rollback safety: Before making a larger maintenance change, the owner confirms they know how to restore if needed.

After the Restore

1. Check Dashboard, Admin, and Settings.
2. Confirm critical modules still appear as expected.
3. Re-test the workflow or setting you were trying to recover.
4. Take a fresh backup again once the restored state is confirmed good.

Related Articles

• Admin Page Tour
• How to Update Cockpit from the Admin Page
• Using the Download Backup Feature