bup-restore - extract files from a backup set
bup restore [-r host:[path]] [--outdir=outdir] [--exclude-rx pattern] [--exclude-rx-from filename] [-v] [-q] <paths…>
bup restore extracts files from a backup set (created with
bup-save(1)) to the local filesystem.
The specified paths are of the form /branch/revision/some/where. The components of the path are as follows:
-n) option to
bup ls /branch.
If some/where names a directory,
bup restore will restore that directory and then recursively restore its contents.
If some/where names a directory and ends with a slash (ie. path/to/dir/),
bup restore will restore the children of that directory directly to the current directory (or the
--outdir). If some/where does not end in a slash, the children will be restored to a subdirectory of the current directory.
If some/where names a directory and ends in ‘/.’ (ie. path/to/dir/.),
bup restore will do exactly what it would have done for path/to/dir, and then restore dir’s metadata to the current directory (or the
--outdir). See the EXAMPLES section.
As a special case, if some/where names the “latest” symlink, e.g.
bup restore /foo/latest, then bup will act exactly as if the save that “latest” points to had been specified, and restore that, rather than the “latest” symlink itself.
Whenever path metadata is available,
bup restore will attempt to restore it. When restoring ownership, bup implements tar/rsync-like semantics. It will normally prefer user and group names to uids and gids when they’re available, but it will not try to restore the user unless running as root, and it will fall back to the numeric uid or gid whenever the metadata contains a user or group name that doesn’t exist on the current system. The use of user and group names can be disabled via
--numeric-ids (which can be important when restoring a chroot, for example), and as a special case, a uid or gid of 0 will never be remapped by name. Additionally, some systems don’t allow setting a uid/gid that doesn’t correspond with a known user/group. On those systems, bup will log an error for each relevant path.
--map-gid options may be used to adjust the available ownership information before any of the rules above are applied, but note that due to those rules,
--map-gid will have no effect whenever a path has a valid user or group. In those cases, either
--numeric-ids must be specified, or the user or group must be cleared by a suitable
--map-user foo= or
Hardlinks will also be restored when possible, but at least currently, no links will be made to targets outside the restore tree, and if the restore tree spans a different arrangement of filesystems from the save tree, some hardlink sets may not be completely restored.
Also note that changing hardlink sets on disk between index and save may produce unexpected results. With the current implementation, bup will attempt to recreate any given hardlink set as it existed at index time, even if all of the files in the set weren’t still hardlinked (but were otherwise identical) at save time.
Note that during the restoration process, access to data within the restore tree may be more permissive than it was in the original source. Unless security is irrelevant, you must restore to a private subdirectory, and then move the resulting tree to its final position. See the EXAMPLES section for a demonstration.
exclude any path matching pattern, which must be a Python regular expression (http://docs.python.org/library/re.html). The pattern will be compared against the full path rooted at the top of the restore tree, without anchoring, so “x/y” will match “ox/yard” or “box/yards”. To exclude the contents of /tmp, but not the directory itself, use “^/tmp/.”. (can be specified more than once)
Note that the root of the restore tree (which matches ‘^/’) is the top of the archive tree being restored, and has nothing to do with the filesystem destination. Given “restore … /foo/latest/etc/”, the pattern ‘^/passwd$’ would match if a file named passwd had been saved as ‘/foo/latest/etc/passwd’.
Create a simple test backup set:
$ bup index -u /etc $ bup save -n mybackup /etc/passwd /etc/profile
Restore just one file:
$ bup restore /mybackup/latest/etc/passwd Restoring: 1, done. $ ls -l passwd -rw-r--r-- 1 apenwarr apenwarr 1478 2010-09-08 03:06 passwd
Restore etc to test (no trailing slash):
$ bup restore -C test /mybackup/latest/etc Restoring: 3, done. $ find test test test/etc test/etc/passwd test/etc/profile
Restore the contents of etc to test (trailing slash):
$ bup restore -C test /mybackup/latest/etc/ Restoring: 2, done. $ find test test test/passwd test/profile
Restore the contents of etc and etc’s metadata to test (trailing “/.”):
$ bup restore -C test /mybackup/latest/etc/. Restoring: 2, done. # At this point test and etc's metadata will match. $ find test test test/passwd test/profile
Restore a tree without risk of unauthorized access:
# mkdir --mode 0700 restore-tmp # bup restore -C restore-tmp /somebackup/latest/foo Restoring: 42, done. # mv restore-tmp/foo somewhere # rmdir restore-tmp
Restore a tree, remapping an old user and group to a new user and group:
# ls -l /original/y -rw-r----- 1 foo baz 3610 Nov 4 11:31 y # bup restore -C dest --map-user foo=bar --map-group baz=bax /x/latest/y Restoring: 42, done. # ls -l dest/y -rw-r----- 1 bar bax 3610 Nov 4 11:31 y
Restore a tree, remapping an old uid to a new uid. Note that the old user must be erased so that bup won’t prefer it over the uid:
# ls -l /original/y -rw-r----- 1 foo baz 3610 Nov 4 11:31 y # ls -ln /original/y -rw-r----- 1 1000 1007 3610 Nov 4 11:31 y # bup restore -C dest --map-user foo= --map-uid 1000=1042 /x/latest/y Restoring: 97, done. # ls -ln dest/y -rw-r----- 1 1042 1007 3610 Nov 4 11:31 y
An alternate way to do the same by quashing users/groups universally with
# bup restore -C dest --numeric-ids --map-uid 1000=1042 /x/latest/y Restoring: 97, done.
Part of the