Skip to main content

System Backups

QuickStack stores its configuration in a SQLite database at storage/db/data.db inside the QuickStack container. System backups capture the entire configuration state: projects, users, app definitions, environment variables, settings.

Not the same as volume/database backups

System backups cover the QuickStack configuration only — not your application data volumes or database contents. Set up volume backups and database backups separately.

Creating a system backup

  1. Go to QuickStack SettingsStorage & Backups.
  2. Choose an S3 target for storing system backups.
  3. Click Run Backup Now for an immediate backup.

If an S3 target is configured, QuickStack also creates a backup automatically every 24 hours.

Downloading a backup

  1. Click View & Restore Backups.
  2. Choose a backup from the list.
  3. The backup file downloads to your local machine.

Restoring a system backup

Critical Warning

Restoring a system backup replaces ALL current configuration data:

  • All projects and applications
  • User accounts and permissions
  • Environment variables and secrets
  • App configurations and settings

This action cannot be undone! After restoring, clear your browser cache and log in again.

  1. Go to QuickStack SettingsStorage & Backups.
  2. Click View & Restore Backups.
  3. Select a previously downloaded backup file.
  4. Confirm the restore operation.
  5. QuickStack replaces the database and restarts automatically.

Manual backup (advanced)

Since QuickStack runs as a Kubernetes pod, you can copy the database file directly:

# Find the QuickStack pod name
kubectl get pods -n quickstack

# Copy the database file from the pod to the host
kubectl cp quickstack/<pod-name>:/app/storage/db/data.db ./quickstack-backup.db

Replace <pod-name> with the actual name of your QuickStack pod.

Best practices

  • Download a system backup before major changes (updates, restructuring projects)
  • Before k3s or Longhorn upgrades — ensure a recent system backup exists
  • Periodically verify backups can be restored on a test instance