Linux · Backups & Archiving

An admin sets up Deja Dup to protect a whole server including /etc and installed system files. Why is that the wrong tool for the job?

Sign in to see the full answer — free to start on the web.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app, free to start on the web. iOS & Android are coming soon.

Get started — it’s free

Already have an account? Sign in →

More in Backups & Archiving

In Grsync, why does turning on Delete on Destination change the safety profile of your backup, and what is the default?

A colleague asks which Linux backup tool is objectively the best. Why is there no single right answer, and what factors actually drive the choice?

Someone runs Deja Dup for the first time expecting only their changed files to be copied. What actually happens on that first run versus later runs, and how can restored data be read back?

Deja Dup and Back In Time both do incremental backups, but restoring a single old file behaves very differently. Where does the duplicity-based approach hurt?

When configuring what Deja Dup should skip, which folders are ignored by default, and which large items are worth adding manually?

Back In Time is described as fast and simple to restore from. What mechanism gives it those properties, and what filesystem requirement does that impose?