Backups and restore

Backups protect the library database and application data from failed upgrades, bad imports, accidental deletion, and storage problems.

Create a backup

1. Open Settings → Data & Import → Backup Manager.
2. Choose Create Backup.
3. Add a description that explains why the backup was made.
4. Wait for the success message.
5. Download a copy to storage outside the application host.

Create a backup before:

• Upgrading the application
• Importing a large collection or reading history
• Running ISBN or cover repairs
• Restoring another backup
• Changing backup storage

Automatic backups

The Backup Manager can configure automatic backup behavior and storage. Store backups inside a mounted persistent volume or use an absolute path that is backed up separately. A backup on the same disk is useful for quick recovery but is not protection from disk failure.

Restore a backup

Restore replaces current data

Restore is a destructive operation for the current library state. Create a fresh backup first, confirm the backup file, and make sure no one is actively editing the library.

1. Open the Backup Manager.
2. Identify the backup by name, date, and description.
3. Create a safety backup of the current state.
4. Choose Restore and confirm.
5. Wait for the restore to complete.
6. Sign in and verify users, books, reading logs, covers, and settings.

If the application does not recover cleanly, check container logs and use the deployment guide before attempting another restore.

Storage and permissions

In Docker deployments, backup paths must be inside a mounted volume. The default application path is data/backups. Protect backup files because they may contain the complete library and personal reading information.

A backup is not a test

Periodically download a backup and verify that it can be opened or restored in a disposable environment. Keep at least one recent backup away from the production host.