An open source, completely automatic on-line backup system for UNIX.
Project status: Stable, but not feature complete
More information: what it is, and how it works.
Comparisons to other backup systems
Distributed under a BSD license. Please read the license and commentary now.
Ben Summers, ben@fluffy.co.uk
This project should be considered as stable, but not feature complete. Over 6 months of testing suggests it will be reliable enough to will back up your data, and make it available for restoration.
It has always been possible to retrieve old versions of files. Planned features will implement marked versions of the store to emulute backing up onto sets of tapes in a controlled manner. This will make restoration of old versions much easier, although in the case of retrieving a single old file will not make much difference to the usability as the FTP-like utility is already effective.
Given that this is a backup system, I am being very conservative about when I consider it ready for production use. That said, I trust my data to it! However, as this is quite a young system compared to the alternatives, and operates in a slightly different manner, for production use I must recommend that you regularly verify your backups.
The documentation is not yet complete, and the error messages you get when things go wrong are not as clear as they should be. (see the troubleshooting page.) Please follow the instructions carefully and read everything to avoid problems -- following the instructions on this web site will result in a working installation.
Because tape is not a reliable solution, unless you...
which is hardly likely to happen in real life.
Backing up to media such as CDROMs is not really a solution either. It needs to be something which just happens without user intervention, and without media which is liable to be corrupted.
So, for the same price as a decent tape backup system, you could buy a server with three big hard discs. And for the money you spend on tapes per year (you do replace them regularly, don't you?), you could host it in a nice data centre somewhere.
We all have internet connections these days, so connectivity isn't really a problem. Although it might be best to archive those static files, like MP3s and images, to CDROM or something.
The costs are even less if you pool resources amongst a group of friends. Remember, you don't have to trust the server admin to not look at your files as they're encrypted. You just have to trust them to make the files available when you need them.
I would like as many people as possible to test this software. To help, I have a large amount of disc space on a server, and am likely to give out a few Gb to people who ask nicely.
As I'm sure I have mentioned, everything is encrypted so you aren't trusting me with your data. You will of course wish to review the code to check my claims are true.
Please join the project mailing list, boxbackup@fluffy.co.uk, for announcements of new versions and discussion of the system. Join at the sign up page.
Many thanks to Alaric for hosting this list.
There are three main elements
Running the store server is a multi-step process, but the backup client is easy.
TLS (SSL revised) is used to encrypt connections, and more importantly, to authenticate servers and clients with both server and client side certificates. Scripts are provided to generate and manage these certificates.
Stored files are encrypted using AES for file data and Blowfish for metadata. This does mean that the one thing you do need to back up off-site and look after is a 1k file containing your keys -- the data on the server is useless without it. But it never changes, so that's OK.
I develop under Darwin and deploy on OpenBSD. The software is designed to take advantage of BSD features where useful, but not to rely on them. It should be easily portable to other UNIX like operating systems. I have done ports to the following platforms:
On these platforms, the software compiles and the tests pass. I do all my deployment on OpenBSD, but I know of several people who have had good results under Linux.
More platforms will arrive over time. It takes in general a couple of hours to get it compiling on a BSD-like UNIX, and a bit longer on something like Linux which deviates from the BSD way of doing things.
I welcome patches for other platforms, and volunteers to look after ports for a particular platform. Programmers notes describing how everything works are included in the notes directory within the distribution archive.
Source only distribution. See documentation on this web site for compilation and installation notes. See notes directory inside distribution archive for programmers notes.
boxbackup-0.08.tgz (486k, released 23 September 2004)
(download via SourceForge)
Notes on upgrading from 0.06 to 0.07, 0.05 to 0.06, 0.04 to 0.05
A 0.08 or later server requires all clients to be version 0.08 or later too. Existing backup store accounts are compatible with 0.08, and do not require conversion.
Changes:
This is basic documentation, which will be improved. Note that configuration uses a number of scripts to do the hard work -- these all output a lot of detailed instructions on exactly what to do. Please read it.
Programmers notes on how the system works can be found within the notes directory inside the distribution archive. In particular, read notes/backup_encryption.txt for details of how the encryption scheme works, and where to look in the code to verify it.
© Ben Summers, 2003, 2004
Web design by Joe Gillespie