#Jottacloud version history install#
#Jottacloud version history software#

#Jottacloud version history install#

Assuming your Pi is up and running, all you need to do is install rdiff-backup from your repository, ports, or extras site. You don't need any special setup to turn your Raspberry Pi into a backup server. It's lightweight and runs on both Linux and FreeBSD, so it's trivial to run even on the oldest Raspberry Pi. Rdiff-backup performs incremental backups locally or over a network using standard UNIX tools ( tar, rdiff, rsync, and so on), so even if it does fade away, the backup files it creates are still useful. Then I found rdiff-backup, a simple backup tool based on rsync (it uses librsync), and thereby inheriting its reliability (it has, however, only been around since 2001, so it doesn't have quite the history that rsync has). This served me quite well, but I started finding myself wanting versioned backups of certain files rsync does a backup for files that have changed, but it overwrites the old version with the new, so if my problem isn't that a file has been deleted but that I've messed up a file beyond recognition, then having rsync'd backup files don't do me a bit of good, because the backup almost always ends up being the bad version of a file that I was looking to replace. That gets annoying after a while, so I started using rsync, the venerable old UNIX command that's been around for decades. There are several tools for auto backups, but I've found over the years that most of the nice slick graphical backup solutions end up falling out of maintenance until they fade away, forcing me to switch to something different.

#Jottacloud version history software#

rdiff-backupįirst, you need to choose some backup software to have your backup server (your Pi) and your clients (your laptop, desktop, and whatever else) run. All you need is a Raspberry Pi and a big hard drive and you have built, essentially, a custom version of those annoying 'easy backup' systems that hard drive companies come out with every few years (you know the ones? the ones you hook up to your network, waste a weekend trying to configure only to discover in a hidden online forum that nothing works as advertised due to a bug in the firmware, which the hard drive company promised they'll fix 'soon' two years ago). You can leave the Pi on all day and all night and never notice it on your power bill, and you can task it with the simple activity of running backups across your home network. And that's exactly what a Raspberry Pi is best at. Such a system is best when it's always on, running in the background.

And that's precisely why the best backup solution is the solution that you don't do at all it's the one you automate. That's because going through the backup process requires us to remember to do it, it takes effort, and it takes time. Making backups of our digital lives is, as most of us begrudgingly admit, the most important thing of daily computing that none of us bother to do.

Whitepaper: Data-intensive intelligent applications in a hybrid cloud blueprint.

eBook: Running Kubernetes on your Raspberry Pi.

Getting started with Raspberry Pi cheat sheet.