8 Commits

Author	SHA1	Message	Date
Joshua Tauberer	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
Joshua Tauberer	f66914d634	backup: automatically take a full backup when the sum of the increments get very large	2014-08-11 11:38:32 +00:00
Joshua Tauberer	58e300e113	backup must be full on the first run because incremental backup will fail, fixes #134	2014-08-11 07:16:58 -04:00
Joshua Tauberer	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
Joshua Tauberer	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
Joshua Tauberer	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
Joshua Tauberer	cecda9cec5	management: shell out external programs in a more secure way	2014-06-09 08:09:45 -04:00
Joshua Tauberer	89730bd643	new backup script, see #11	2014-06-03 21:16:38 +00:00