support system backups (set up a backup run by root)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
Confirmed
|
Wishlist
|
Unassigned | ||
deja-dup (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
It would be great if you could "fix Deja Dup to ask for permission to read things it can't." (From answer to question #67726).
Also from that thread:
---
This is what I'm using now:
sudo duplicity / scp://username@
I can *almost* do this via [deja-dup], but when I run it as root it I don't have access to the typical Nautilus style "Connect to Server" options. It seams there isn't a way to specify an scp destination. Then there's also the scheduling issue mentioned above.
---
Deja-dup might not have to run as root just to go through the GUI to configure the system backup (profile). It might be enough to be able to trigger backups from the command line as root (su, sudo), or by dropping a script into /etc/cron.daily.
OTOH with backintime you run it as root to create the config files for root.
Changed in deja-dup (Ubuntu): | |
importance: | Undecided → Wishlist |
I agree this would be nice. But since Deja Dup's focus is really simple home backups, I'm marking this wishlist.
There are some technical challenges here too. Duplicity tells us when we can't read a file. But then we'd need to be able to go back with sudo and get them. And if we try to run duplicity under sudo, we can't use GIO. So maybe we'd need to move the files ourselves to a place that the user can read before backing them up...