Where Does DejaDup Store Settings and Backups?
DejaDup dconf settings, duplicity cache and backup destinations on Linux.
Last updated
DejaDup keeps its schedule, folders and destination in dconf under the GNOME settings tree, engine working files in the duplicity cache directory, and the actual encrypted backup sets at whatever destination was chosen (local drive, network or cloud). Passwords live in the GNOME keyring.
Three places, three jobs: dconf for what to back up and where, cache for engine manifests between runs, destination for the restorable sets. Clearing the cache is safe (it rebuilds from the destination); clearing dconf forgets the job definition itself.
Where DejaDup stores this, by platform
dconf /org/gnome/deja-dup (settings) plus ~/.cache/duplicity (engine cache)
View settings with dconf-editor; passwords in Seahorse keyring. Newer builds use Restic behind the scenes. Purge settings with package purge plus dconf reset of the deja-dup path.
Frequently asked questions
how do I reset DejaDup completely
Purge the package, reset dconf at the deja-dup path, and remove the duplicity cache. Reconfigure destination and folders fresh; old backup sets at the destination remain restorable.
can I delete the duplicity cache folder
Yes. It holds manifests and signatures that rebuild from the backup destination on next run. Never delete the destination sets themselves unless retiring the backup.
Notice an outdated path? Let us know.