Merge lp:~angusgr/duplicity/exclude-older-than into lp:~duplicity-team/duplicity/0.7-series
Status: | Merged |
---|---|
Merged at revision: | 1065 |
Proposed branch: | lp:~angusgr/duplicity/exclude-older-than |
Merge into: | lp:~duplicity-team/duplicity/0.7-series |
Diff against target: |
72 lines (+33/-0) 3 files modified
bin/duplicity.1 (+9/-0) duplicity/commandline.py (+4/-0) duplicity/selection.py (+20/-0) |
To merge this branch: | bzr merge lp:~angusgr/duplicity/exclude-older-than |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
duplicity-team | Pending | ||
Review via email: mp+247922@code.launchpad.net |
Description of the change
Hi,
I have a small change that I've been using for over a year now for my own backups, and I realised I should probably submit it back. I'm not sure if you'll want to include it, but it's been useful for me.
The change is an "--exclude-
How I personally use it is for my off-site backups. Every couple of months I swap a physical hard disk off-site which contains a full disk backup via duplicity. However every hour or so I run an incremental backup to S3 covering my most used directories. The S3 backup has the option --exclude-
Provided I rotate the "large" off-site backup more regularly than every 90 days, I can expect that between the two backups I have a complete set of the data that matters to me. If I backuped everything up to S3 then it'd be expensive and clog up my poor low-bandwidth upstream ADSL link, but a lot of it is data that hasn't changed in months.
I don't know if this kind of configuration will work for anyone apart from just me, but I thought you might find the option interesting anyhow.
Thanks very much for duplicity btw, it's a great tool that has saved me several times now!
Angus