Look at that.
root@halleck:~# tarsnap --list-archives -v | sort -k2 | head -n1 M2009-09 2009-09-01 05:24:01 root@halleck:~#
Having been using the Tarsnap backup service for five years kind of deserves a blog post? Let me share a few of the reason why I keep using Tarsnap for offsite backups, and why you too might want to.
- Encryption happens locally, allowing one to worry less about the files being included.
- Data deduplication on a block level, allowing for every kept backup to be a full snapshot.
- Client uses basically the same command line option as regular tar, making Tarsnap familiar as well as scriptable.
- While not open source, the Tarsnap client source code is fully available, coupled with a serious bug bounty program.
- Server side Tarsnap uses Amazon S3 for storage, which has a proven record for durability.
- IPv6 support.
Then there are these potential issues, which may or may not be an issue for you.
- Restoring files tend to be a bit slow. That limitation can partially be worked around by restoring separate folders in parallel.
- You can only use the Tarsnap backup client together with the Tarsnap backup service. Backing up to your own infrastructure is not supported.
- Payment can only be made a head of time, and if your account runs out of money there is a relatively short window before your backups are deleted. Personally I can keep track of that, but it makes me hesitant to recommend Tarsnap in any work environment.
In case you start using Tarsnap, then feel free to take a look at my tarsnap-helpers git repository. It contains a couple of monitoring scripts as well as some bash completions.