1 bup: It backs things up
2 =======================
4 bup is a program that backs things up. It's short for "backup." Can you
5 believe that nobody else has named an open source program "bup" after all
8 Despite its unassuming name, bup is pretty cool. To give you an idea of
9 just how cool it is, I wrote you this poem:
12 What rhymes with awesome?
14 But that's irrelevant.
16 Hmm. Did that help? Maybe prose is more useful after all.
19 Reasons bup is awesome
20 ----------------------
22 bup has a few advantages over other backup software:
24 - It uses a rolling checksum algorithm (similar to rsync) to split large
25 files into chunks. The most useful result of this is you can backup huge
26 virtual machine (VM) disk images, databases, and XML files incrementally,
27 even though they're typically all in one huge file, and not use tons of
28 disk space for multiple versions.
30 - It uses the packfile format from git (the open source version control
31 system), so you can access the stored data even if you don't like bup's
34 - Unlike git, it writes packfiles *directly* (instead of having a separate
35 garbage collection / repacking stage) so it's fast even with gratuitously
36 huge amounts of data. bup's improved index formats also allow you to
37 track far more filenames than git (millions) and keep track of far more
38 objects (hundreds or thousands of gigabytes).
40 - Data is "automagically" shared between incremental backups without having
41 to know which backup is based on which other one - even if the backups
42 are made from two different computers that don't even know about each
43 other. You just tell bup to back stuff up, and it saves only the minimum
44 amount of data needed.
46 - You can back up directly to a remote bup server, without needing tons of
47 temporary disk space on the computer being backed up. And if your backup
48 is interrupted halfway through, the next run will pick up where you left
49 off. And it's easy to set up a bup server: just install bup on any
50 machine where you have ssh access.
52 - Bup can use "par2" redundancy to recover corrupted backups even if your
53 disk has undetected bad sectors.
55 - Even when a backup is incremental, you don't have to worry about
56 restoring the full backup, then each of the incrementals in turn; an
57 incremental backup *acts* as if it's a full backup, it just takes less
60 - You can mount your bup repository as a FUSE filesystem and access the
61 content that way, and even export it over Samba.
63 - It's written in python (with some C parts to make it faster) so it's easy
64 for you to extend and maintain.
67 Reasons you might want to avoid bup
68 -----------------------------------
70 - It's not remotely as well tested as something like tar, so it's
71 more likely to eat your data. It's also missing some
72 probably-critical features, though fewer than it used to be.
74 - It requires python >= 2.6, a C compiler, and an installed git
75 version >= 1.5.6. It also requires par2 if you want fsck to be
76 able to generate the information needed to recover from some types
79 - It currently only works on Linux, FreeBSD, NetBSD, OS X >= 10.4,
80 Solaris, or Windows (with Cygwin, and maybe with WSL). Patches to
81 support other platforms are welcome.
83 - Any items in "Things that are stupid" below.
86 Notable changes introduced by a release
87 =======================================
89 - <a href="note/0.30.1-from-0.30.md">Changes in 0.30.1 as compared to 0.30</a>
90 - <a href="note/0.30-from-0.29.3.md">Changes in 0.30 as compared to 0.29.3</a>
91 - <a href="note/0.29.3-from-0.29.2.md">Changes in 0.29.3 as compared to 0.29.2</a>
92 - <a href="note/0.29.2-from-0.29.1.md">Changes in 0.29.2 as compared to 0.29.1</a>
93 - <a href="note/0.29.1-from-0.29.md">Changes in 0.29.1 as compared to 0.29</a>
94 - <a href="note/0.29-from-0.28.1.md">Changes in 0.29 as compared to 0.28.1</a>
95 - <a href="note/0.28.1-from-0.28.md">Changes in 0.28.1 as compared to 0.28</a>
96 - <a href="note/0.28-from-0.27.1.md">Changes in 0.28 as compared to 0.27.1</a>
97 - <a href="note/0.27.1-from-0.27.md">Changes in 0.27.1 as compared to 0.27</a>
103 | branch | Debian | FreeBSD | macOS |
104 |--------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
105 | master | [](https://cirrus-ci.com/github/bup/bup) | [](https://cirrus-ci.com/github/bup/bup) | [](https://cirrus-ci.com/github/bup/bup) |
106 | 0.29.x | [](https://cirrus-ci.com/github/bup/bup) | [](https://cirrus-ci.com/github/bup/bup) | [](https://cirrus-ci.com/github/bup/bup) |
114 - Check out the bup source code using git:
117 git clone https://github.com/bup/bup
120 - This will leave you on the master branch, which is perfect if you
121 would like to help with development, but if you'd just like to use
122 bup, please check out the latest stable release like this:
128 You can see the latest stable release here:
129 https://github.com/bup/bup/releases.
131 - Install the required python libraries (including the development
134 On very recent Debian/Ubuntu versions, this may be sufficient (run
138 apt-get build-dep bup
141 Otherwise try this (substitute python2.6-dev if you have an older
145 apt-get install python2.7-dev python-fuse
146 apt-get install python-pyxattr python-pylibacl
147 apt-get install linux-libc-dev
148 apt-get install acl attr
149 apt-get install python-tornado # optional
152 On CentOS (for CentOS 6, at least), this should be sufficient (run
156 yum groupinstall "Development Tools"
157 yum install python python-devel
158 yum install fuse-python pyxattr pylibacl
159 yum install perl-Time-HiRes
162 In addition to the default CentOS repositories, you may need to add
163 RPMForge (for fuse-python) and EPEL (for pyxattr and pylibacl).
165 On Cygwin, install python, make, rsync, and gcc4.
167 If you would like to use the optional bup web server on systems
168 without a tornado package, you may want to try this:
174 - Build the python module and symlinks:
186 or if you're in a bit more of a hurry:
192 The tests should pass. If they don't pass for you, stop here and
193 send an email to bup-list@googlegroups.com. Though if there are
194 symbolic links along the current working directory path, the tests
195 may fail. Running something like this before "make test" should
196 sidestep the problem:
202 - You can install bup via "make install", and override the default
203 destination with DESTDIR and PREFIX.
205 Files are normally installed to "$DESTDIR/$PREFIX" where DESTDIR is
206 empty by default, and PREFIX is set to /usr/local. So if you wanted to
207 install bup to /opt/bup, you might do something like this:
210 make install DESTDIR=/opt/bup PREFIX=''
213 - The Python executable that bup will use is chosen by ./configure,
214 which will search for a reasonable version unless PYTHON is set in
215 the environment, in which case, bup will use that path. You can
216 see which Python executable was chosen by looking at the
217 configure output, or examining cmd/python-cmd.sh, and you can
218 change the selection by re-running ./configure.
223 Binary packages of bup are known to be built for the following OSes:
226 http://packages.debian.org/search?searchon=names&keywords=bup
228 http://packages.ubuntu.com/search?searchon=names&keywords=bup
229 - pkgsrc (NetBSD, Dragonfly, and others)
230 http://pkgsrc.se/sysutils/bup
231 http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/bup/
233 https://www.archlinux.org/packages/?sort=&q=bup
235 https://apps.fedoraproject.org/packages/bup
241 - Get help for any bup command:
252 - Initialize the default BUP_DIR (~/.bup -- you can choose another by
253 either specifying `bup -d DIR ...` or setting the `BUP_DIR`
254 environment variable for a command):
260 - Make a local backup (-v or -vv will increase the verbosity):
264 bup save -n local-etc /etc
267 - Restore a local backup to ./dest:
270 bup restore -C ./dest local-etc/latest/etc
274 - Look at how much disk space your backup took:
280 - Make another backup (which should be mostly identical to the last one;
281 notice that you don't have to *specify* that this backup is incremental,
282 it just saves space automatically):
286 bup save -n local-etc /etc
289 - Look how little extra space your second backup used (on top of the first):
295 - Get a list of your previous backups:
301 - Restore your first backup again:
304 bup restore -C ./dest-2 local-etc/2013-11-23-11195/etc
307 - Make a backup to a remote server which must already have the 'bup' command
308 somewhere in its PATH (see /etc/profile, etc/environment, ~/.profile, or
309 ~/.bashrc), and be accessible via ssh.
310 Make sure to replace SERVERNAME with the actual hostname of your server:
313 bup init -r SERVERNAME:path/to/remote-bup-dir
315 bup save -r SERVERNAME:path/to/remote-bup-dir -n local-etc /etc
318 - Make a remote backup to ~/.bup on SERVER:
322 bup save -r SERVER: -n local-etc /etc
325 - See what saves are available in ~/.bup on SERVER:
331 - Restore the remote backup to ./dest:
334 bup restore -r SERVER: -C ./dest local-etc/latest/etc
338 - Defend your backups from death rays (OK fine, more likely from the
339 occasional bad disk block). This writes parity information
340 (currently via par2) for all of the existing data so that bup may
341 be able to recover from some amount of repository corruption:
347 - Use split/join instead of index/save/restore. Try making a local
351 tar -cvf - /etc | bup split -n local-etc -vv
354 - Try restoring the tarball:
357 bup join local-etc | tar -tf -
360 - Look at how much disk space your backup took:
366 - Make another tar backup:
369 tar -cvf - /etc | bup split -n local-etc -vv
372 - Look at how little extra space your second backup used on top of
379 - Restore the first tar backup again (the ~1 is git notation for "one
380 older than the most recent"):
383 bup join local-etc~1 | tar -tf -
386 - Get a list of your previous split-based backups:
389 GIT_DIR=~/.bup git log local-etc
392 - Save a tar archive to a remote server (without tar -z to facilitate
396 tar -cvf - /etc | bup split -r SERVERNAME: -n local-etc -vv
399 - Restore the archive:
402 bup join -r SERVERNAME: local-etc | tar -tf -
405 That's all there is to it!
411 - FreeBSD's default 'make' command doesn't like bup's Makefile. In order to
412 compile the code, run tests and install bup, you need to install GNU Make
413 from the port named 'gmake' and use its executable instead in the commands
414 seen above. (i.e. 'gmake test' runs bup's test suite)
416 - Python's development headers are automatically installed with the 'python'
417 port so there's no need to install them separately.
419 - To use the 'bup fuse' command, you need to install the fuse kernel module
420 from the 'fusefs-kmod' port in the 'sysutils' section and the libraries from
421 the port named 'py-fusefs' in the 'devel' section.
423 - The 'par2' command can be found in the port named 'par2cmdline'.
425 - In order to compile the documentation, you need pandoc which can be found in
426 the port named 'hs-pandoc' in the 'textproc' section.
429 Notes on NetBSD/pkgsrc
430 ----------------------
432 - See pkgsrc/sysutils/bup, which should be the most recent stable
433 release and includes man pages. It also has a reasonable set of
434 dependencies (git, par2, py-fuse-bindings).
436 - The "fuse-python" package referred to is hard to locate, and is a
437 separate tarball for the python language binding distributed by the
438 fuse project on sourceforge. It is available as
439 pkgsrc/filesystems/py-fuse-bindings and on NetBSD 5, "bup fuse"
442 - "bup fuse" presents every directory/file as inode 0. The directory
443 traversal code ("fts") in NetBSD's libc will interpret this as a
444 cycle and error out, so "ls -R" and "find" will not work.
446 - There is no support for ACLs. If/when some enterprising person
447 fixes this, adjust t/compare-trees.
453 - There is no support for ACLs. If/when some enterprising person
454 fixes this, adjust t/compare-trees.
456 - In t/test.sh, two tests have been disabled. These tests check to
457 see that repeated saves produce identical trees and that an
458 intervening index doesn't change the SHA1. Apparently Cygwin has
459 some unusual behaviors with respect to access times (that probably
460 warrant further investigation). Possibly related:
461 http://cygwin.com/ml/cygwin/2007-06/msg00436.html
467 - There is no support for ACLs. If/when some enterprising person
468 fixes this, adjust t/compare-trees.
477 bup stores its data in a git-formatted repository. Unfortunately, git
478 itself doesn't actually behave very well for bup's use case (huge numbers of
479 files, files with huge sizes, retaining file permissions/ownership are
480 important), so we mostly don't use git's *code* except for a few helper
481 programs. For example, bup has its own git packfile writer written in
484 Basically, 'bup split' reads the data on stdin (or from files specified on
485 the command line), breaks it into chunks using a rolling checksum (similar to
486 rsync), and saves those chunks into a new git packfile. There is at least one
487 git packfile per backup.
489 When deciding whether to write a particular chunk into the new packfile, bup
490 first checks all the other packfiles that exist to see if they already have that
491 chunk. If they do, the chunk is skipped.
493 git packs come in two parts: the pack itself (*.pack) and the index (*.idx).
494 The index is pretty small, and contains a list of all the objects in the
495 pack. Thus, when generating a remote backup, we don't have to have a copy
496 of the packfiles from the remote server: the local end just downloads a copy
497 of the server's *index* files, and compares objects against those when
498 generating the new pack, which it sends directly to the server.
500 The "-n" option to 'bup split' and 'bup save' is the name of the backup you
501 want to create, but it's actually implemented as a git branch. So you can
502 do cute things like checkout a particular branch using git, and receive a
503 bunch of chunk files corresponding to the file you split.
505 If you use '-b' or '-t' or '-c' instead of '-n', bup split will output a
506 list of blobs, a tree containing that list of blobs, or a commit containing
507 that tree, respectively, to stdout. You can use this to construct your own
508 scripts that do something with those values.
513 'bup index' walks through your filesystem and updates a file (whose name is,
514 by default, ~/.bup/bupindex) to contain the name, attributes, and an
515 optional git SHA1 (blob id) of each file and directory.
517 'bup save' basically just runs the equivalent of 'bup split' a whole bunch
518 of times, once per file in the index, and assembles a git tree
519 that contains all the resulting objects. Among other things, that makes
520 'git diff' much more useful (compared to splitting a tarball, which is
521 essentially a big binary blob). However, since bup splits large files into
522 smaller chunks, the resulting tree structure doesn't *exactly* correspond to
523 what git itself would have stored. Also, the tree format used by 'bup save'
524 will probably change in the future to support storing file ownership, more
525 complex file permissions, and so on.
527 If a file has previously been written by 'bup save', then its git blob/tree
528 id is stored in the index. This lets 'bup save' avoid reading that file to
529 produce future incremental backups, which means it can go *very* fast unless
530 a lot of files have changed.
533 Things that are stupid for now but which we'll fix later
534 ========================================================
536 Help with any of these problems, or others, is very welcome. Join the
537 mailing list (see below) if you'd like to help.
539 - 'bup save' and 'bup restore' have immature metadata support.
541 On the plus side, they actually do have support now, but it's new,
542 and not remotely as well tested as tar/rsync/whatever's. However,
543 you have to start somewhere, and as of 0.25, we think it's ready
544 for more general use. Please let us know if you have any trouble.
546 Also, if any strip or graft-style options are specified to 'bup
547 save', then no metadata will be written for the root directory.
548 That's obviously less than ideal.
550 - bup is overly optimistic about mmap. Right now bup just assumes
551 that it can mmap as large a block as it likes, and that mmap will
552 never fail. Yeah, right... If nothing else, this has failed on
553 32-bit architectures (and 31-bit is even worse -- looking at you,
556 To fix this, we might just implement a FakeMmap[1] class that uses
557 normal file IO and handles all of the mmap methods[2] that bup
558 actually calls. Then we'd swap in one of those whenever mmap
561 This would also require implementing some of the methods needed to
562 support "[]" array access, probably at a minimum __getitem__,
563 __setitem__, and __setslice__ [3].
565 [1] http://comments.gmane.org/gmane.comp.sysutils.backup.bup/613
566 [2] http://docs.python.org/2/library/mmap.html
567 [3] http://docs.python.org/2/reference/datamodel.html#emulating-container-types
569 - 'bup index' is slower than it should be.
571 It's still rather fast: it can iterate through all the filenames on my
572 600,000 file filesystem in a few seconds. But it still needs to rewrite
573 the entire index file just to add a single filename, which is pretty
574 nasty; it should just leave the new files in a second "extra index" file
577 - bup could use inotify for *really* efficient incremental backups.
579 You could even have your system doing "continuous" backups: whenever a
580 file changes, we immediately send an image of it to the server. We could
581 give the continuous-backup process a really low CPU and I/O priority so
582 you wouldn't even know it was running.
584 - bup only has experimental support for pruning old backups.
586 While you should now be able to drop old saves and branches with
587 `bup rm`, and reclaim the space occupied by data that's no longer
588 needed by other backups with `bup gc`, these commands are
589 experimental, and should be handled with great care. See the
590 man pages for more information.
592 Unless you want to help test the new commands, one possible
593 workaround is to just start a new BUP_DIR occasionally,
594 i.e. bup-2013, bup-2014...
596 - bup has never been tested on anything but Linux, FreeBSD, NetBSD,
597 OS X, and Windows+Cygwin.
599 There's nothing that makes it *inherently* non-portable, though, so
600 that's mostly a matter of someone putting in some effort. (For a
601 "native" Windows port, the most annoying thing is the absence of ssh in
602 a default Windows installation.)
604 - bup needs better documentation.
606 According to an article about bup in Linux Weekly News
607 (https://lwn.net/Articles/380983/), "it's a bit short on examples and
608 a user guide would be nice." Documentation is the sort of thing that
609 will never be great unless someone from outside contributes it (since
610 the developers can never remember which parts are hard to understand).
612 - bup is "relatively speedy" and has "pretty good" compression.
614 ...according to the same LWN article. Clearly neither of those is good
615 enough. We should have awe-inspiring speed and crazy-good compression.
616 Must work on that. Writing more parts in C might help with the speed.
620 Actually, that's not stupid, but you might consider it a
621 limitation. See the ["Related Projects"](https://bup.github.io/)
622 list for some possible options.
627 bup has an extensive set of man pages. Try using 'bup help' to get
628 started, or use 'bup help SUBCOMMAND' for any bup subcommand (like split,
629 join, index, save, etc.) to get details on that command.
631 For further technical details, please see ./DESIGN.
637 bup is a work in progress and there are many ways it can still be improved.
638 If you'd like to contribute patches, ideas, or bug reports, please join the
641 You can find the mailing list archives here:
643 http://groups.google.com/group/bup-list
645 and you can subscribe by sending a message to:
647 bup-list+subscribe@googlegroups.com
649 Please see <a href="HACKING">./HACKING</a> for
650 additional information, i.e. how to submit patches (hint - no pull
651 requests), how we handle branches, etc.
projects / bup.git / blob