Files
authentik/website/docs/sys-mgmt/ops/backup-restore.md
T
Dominic R 20f5875784 website/docs: Update location of media storage and outdated references (#19885)
* website/docs: Update location of media storage and outdated references

* lint

* Add content-type header info

* Apply suggestion from @dominic-r

Signed-off-by: Dominic R <dominic@sdko.org>

---------

Signed-off-by: Dominic R <dominic@sdko.org>
Co-authored-by: dewi-tik <dewi@goauthentik.io>
2026-02-02 14:02:37 +00:00

3.0 KiB
Raw Blame History

title, sidebar_label
title sidebar_label
Backup and restore your authentik instance Backup & Restore

This guide outlines the critical components to back up and restore in authentik.

PostgreSQL database

Backup

  • Role: Stores all persistent data (users, policies, configurations, etc.).
  • Impact of Loss: Complete data loss, requiring full restoration to recover functionality.
  • Backup Guidance:
  • Official Documentation: PostgreSQL Backup and Restore

Restore

  • Restoration Importance: Essential for full recovery; authentik will not function without it.
  • Restoration Guidance:
    • Use PostgreSQL's pg_restore or other official methods.

Static directories

These directories are mounted as volumes in containerized installations and must be restored if they were part of the backup to maintain authentiks expected functionality.

Directory Purpose Backup and Restore Notes
/data Stores application icons, flow backgrounds, uploaded files, and CSV reports. Only required if not using S3 external storage. External storage should be backed up using the AWS S3 Sync utility.
/certs Stores TLS certificates in the filesystem. Backup if you rely on these certificates present in the filesystem. Not needed if authentik has already imported them, as certificates are stored in the database.
/custom-templates Stores custom changes to the authentik UI. Required if you modified authentik's default appearance.
/blueprints Stores blueprints. Optional but recommended if using custom blueprints.