Backups: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
* rdiff-backup | * rdiff-backup | ||
* deja-dup | * deja-dup | ||
* rclone (for backing up from/to cloud services such as Google Docs) | |||
== | == Writing new software == | ||
* | MVP: | ||
* Include file (one per line) | |||
* Exclude file (one per line) | |||
* Copy files from X to Y | |||
* Database (SQLite?) to hold metadata (map hashes to file paths) | |||
* MD5 for deduplication | |||
== GitHub == | == GitHub == | ||
Revision as of 15:24, 19 December 2022
Topics for consideration
- How can I start backups automatically when I login? Don't want to do this until a network connection is available, and possibly my keyring has been unlocked.
- How can I start a backup run periodically? Is this necessary given that I usually login at least once every 24 hours?
- How can I put an icon in the system menu that shows backup status/process? Similar to Nextcloud would be useful with a tick for complete, circular arrows for in process, and a cross for failed.
Existing software
- tar
- Obnam
- restic
- Borg
- rdiff-backup
- deja-dup
- rclone (for backing up from/to cloud services such as Google Docs)
Writing new software
MVP:
- Include file (one per line)
- Exclude file (one per line)
- Copy files from X to Y
- Database (SQLite?) to hold metadata (map hashes to file paths)
- MD5 for deduplication