Where Does Déjà Dup Store Config on Linux?
Deja Dup keeps backup prefs in dconf with duplicity archives wherever you point them. First backup verifies the whole chain.
Last updated
Déjà Dup stores preferences in dconf with backup destinations you choose. Local folders, network shares and cloud targets all work. Encryption passwords guard the archives.
Prefs and archives split. Export dconf settings to move schedules. Copy or reconnect archives at the destination. The backend stays duplicity throughout, so archives remain standard.
Where Déjà Dup stores this, by platform
dconf prefs plus backup destination you choose (duplicity backend)
Prefs in dconf, archives at your chosen destination. Export settings plus reconnect archives for moves. Encryption password required.
Frequently asked questions
How do I restore Déjà Dup elsewhere?
Point the new install at the same destination and enter the same encryption password. Prefs in dconf travel separately via export. First backup after moving verifies the chain.
Backups stopped running. What do I check?
Open the app prefs and check destination, schedule and encryption. Those three decide everything. The backend tool duplicity does the actual file work.
Notice an outdated path? Let us know.