# Backup & Import ## Backup types - **Full ZIP** — SQLite database, attachments and encryption key. Self-contained and highly sensitive. - **Raw DB/SQLite** — database only. Preserve `vodum.encryption_key` separately. Automatic backup and cleanup tasks enforce configured age and file-count retention. Database integrity diagnostics are visible on the page. Portal accounts, identities, sessions, tokens and audit events live in the main database and are therefore included in every full backup and restored atomically with it. A personal-data erasure affects the live database and future backups; older backups may still contain the erased data until normal backup retention deletes them. Restoring such a backup restores that historical state, so operators must reapply any erasure request after a rollback when legally required. ## Restore Select an existing backup or upload `.zip`, `.db` or `.sqlite`. VODUM validates SQLite integrity, required tables, ZIP paths, member count and extracted size. Restore enters maintenance mode, waits for work already running in the task lanes to finish and suspends new starts. It replaces data safely and exits the process so the container can restart. New work remains suspended until restart. Pending portal media requests from the restored database are closed to avoid replaying an ARR addition that may already have happened. Check the actual provider state before submitting a request again. Historical subscription, portal and collection data reflect the restored point in time. When an encryption key is supplied through the environment, it must match the key contained in a full backup. Never restore an untrusted archive. ## Tautulli import Upload a Tautulli SQLite database, select the destination Plex server and choose how unknown users/libraries are handled. Imports are queued, deduplicated and cleaned after processing. The direct CLI supports `--summary-only` for a single machine-readable JSON result.