5b62cb070a
Pass passphrase through to all duplicity calls
...
Empirical evidence (a failed cron job) shows that cleanup requires the
passphrase (so it presumably needs to decrypt metadata), and though
remove-older-than has been working fine without it, it won't do any harm
to set it in case that changes or there are any special cases.
2015-03-30 09:42:48 +01:00
2c6941c34c
Final corrections and tweaks
2015-03-28 17:32:35 +00:00
108cc55ca1
Guard via idempotency against termination between migration operations
2015-03-27 19:23:16 +00:00
2726b15764
Use built in duplicity encryption (GPG) for backups, closes #362
2015-03-26 23:51:29 +00:00
c18d58b13f
backups: predict when the next backup will occur
2015-03-21 15:22:45 +00:00
86a5394f07
fix control panel when no backup has been made yet
2014-10-15 12:31:08 -04:00
048e35a80f
fix display of backups that are past due to be reaped
2014-10-13 14:12:16 +00:00
fb3045f456
retain backups only for 3 days; beyond that the user is responsible for copying files off of the machine
2014-10-13 14:12:11 +00:00
4cf53cd8ee
backup status relativedelta was displaying wrong for deltas greater than 1 month
2014-10-05 18:23:29 +00:00
98fc449b49
only hold onto backups for 14 days (not 31) and show when the backups will be deleted in the control panel
2014-09-08 20:09:18 +00:00
bab8b515ea
new logic for determining when to take a full backup
2014-09-08 19:42:54 +00:00
3853e8dd93
show the status of backups in the control panel
2014-09-01 13:06:53 +00:00
a32806da32
create STORAGE_ROOT/backup/duplicity if it doesn't exist
...
fixes #158
2014-08-25 23:29:00 +00:00
18f0406541
update comments in backup.py
2014-08-25 23:28:43 +00:00
1312b0254b
backup: dont remove old increments because then we lose the backup history right before the last full backup, instead let them disappear along with full backups when a whole chain becomes very old
2014-08-11 11:45:40 +00:00
f66914d634
backup: automatically take a full backup when the sum of the increments get very large
2014-08-11 11:38:32 +00:00
58e300e113
backup must be full on the first run because incremental backup will fail, fixes #134
2014-08-11 07:16:58 -04:00
6a512042dc
after creating the local encrypted backup, execute the after-backup script if the user has provided one to copy the files to a remote location
2014-08-02 14:16:08 +00:00
8bd62aa3bc
increase duplicity's volume size from the default of 25MB to 100MB so we create fewer files
2014-06-09 13:47:41 +00:00
5490142df5
re-do the backup script to use the duplicity program
...
Duplicity will manage the process of creating incremental backups for us.
Although duplicity can both encrypt & copy files to a remote host, I really
don't like PGP and so I don't want to use that.
Instead, we'll back up to a local directory unencrypted, then manually
encrypt the full & incremental backup files. Synchronizing the encrypted
backup directory to a remote host is a TODO.
2014-06-09 09:34:52 -04:00
cecda9cec5
management: shell out external programs in a more secure way
2014-06-09 08:09:45 -04:00
89730bd643
new backup script, see #11
2014-06-03 21:16:38 +00:00
David Piggott
Joshua Tauberer