1 % bup-restore(1) Bup %BUP_VERSION%
2 % Avery Pennarun <apenwarr@gmail.com>
7 bup-restore - extract files from a backup set
11 bup restore [\--outdir=*outdir*] [\--exclude-rx *pattern*] [-v] [-q]
16 `bup restore` extracts files from a backup set (created
17 with `bup-save`(1)) to the local filesystem.
19 The specified *paths* are of the form
20 /_branch_/_revision_/_some/where_. The components of the
24 : the name of the backup set to restore from; this
25 corresponds to the `--name` (`-n`) option to `bup save`.
28 : the revision of the backup set to restore. The
29 revision *latest* is always the most recent
30 backup on the given branch. You can discover other
31 revisions using `bup ls /branch`.
34 : the previously saved path (after any stripping/grafting) that you
35 want to restore. For example, `etc/passwd`.
37 If _some/where_ names a directory, `bup restore` will restore that
38 directory and then recursively restore its contents.
40 If _some/where_ names a directory and ends with a slash (ie.
41 path/to/dir/), `bup restore` will restore the children of that
42 directory directly to the current directory (or the `--outdir`). If
43 _some/where_ does not end in a slash, the children will be restored to
44 a subdirectory of the current directory.
46 If _some/where_ names a directory and ends in '/.' (ie.
47 path/to/dir/.), `bup restore` will do exactly what it would have done
48 for path/to/dir, and then restore _dir_'s metadata to the current
49 directory (or the `--outdir`). See the EXAMPLES section.
51 Whenever path metadata is available, `bup restore` will attempt to
52 restore it. When restoring ownership, bup implements tar/rsync-like
53 semantics. It will normally prefer user and group names to uids and
54 gids when they're available, but it will not try to restore the user
55 unless running as root, and it will fall back to the numeric uid or
56 gid whenever the metadata contains a user or group name that doesn't
57 exist on the current system. The use of user and group names can be
58 disabled via `--numeric-ids` (which can be important when restoring a
59 chroot, for example), and as a special case, a uid or gid of 0 will
60 never be remapped by name. Additionally, some systems don't allow
61 setting a uid/gid that doesn't correspond with a known user/group. On
62 those systems, bup will log an error for each relevant path.
64 The `--map-user`, `--map-group`, `--map-uid`, `--map-gid` options may
65 be used to adjust the available ownership information before any of
66 the rules above are applied, but note that due to those rules,
67 `--map-uid` and `--map-gid` will have no effect whenever a path has a
68 valid user or group. In those cases, either `--numeric-ids` must be
69 specified, or the user or group must be cleared by a suitable
70 `--map-user foo=` or `--map-group foo=`.
72 Hardlinks will also be restored when possible, but at least currently,
73 no links will be made to targets outside the restore tree, and if the
74 restore tree spans a different arrangement of filesystems from the
75 save tree, some hardlink sets may not be completely restored.
77 Also note that changing hardlink sets on disk between index and save
78 may produce unexpected results. With the current implementation, bup
79 will attempt to recreate any given hardlink set as it existed at index
80 time, even if all of the files in the set weren't still hardlinked
81 (but were otherwise identical) at save time.
83 Note that during the restoration process, access to data within the
84 restore tree may be more permissive than it was in the original
85 source. Unless security is irrelevant, you must restore to a private
86 subdirectory, and then move the resulting tree to its final position.
87 See the EXAMPLES section for a demonstration.
91 -C, \--outdir=*outdir*
92 : create and change to directory *outdir* before
96 : restore numeric IDs (user, group, etc.) rather than names.
98 \--exclude-rx=*pattern*
99 : exclude any path matching *pattern*, which must be a Python
100 regular expression (http://docs.python.org/library/re.html). The
101 pattern will be compared against the full path rooted at the top
102 of the restore tree, without anchoring, so "x/y" will match
103 "ox/yard" or "box/yards". To exclude the contents of /tmp, but
104 not the directory itself, use "^/tmp/.". (can be specified more
107 Note that the root of the restore tree (which matches '^/') is the
108 top of the archive tree being restored, and has nothing to do with
109 the filesystem destination. Given "restore ... /foo/latest/etc/",
110 the pattern '^/passwd$' would match if a file named passwd had
111 been saved as '/foo/latest/etc/passwd'.
115 * '/foo$' - exclude any file named foo
116 * '/foo/$' - exclude any directory named foo
117 * '/foo/.' - exclude the content of any directory named foo
118 * '^/tmp/.' - exclude root-level /tmp's content, but not /tmp itself
120 \--map-user *old*=*new*
121 : restore *old* user as *new* user. Specifying "" for *new* will
122 clear the user, i.e. `--map-user foo=`.
124 \--map-group *old*=*new*
125 : restore *old* group as *new* group. Specifying "" for *new* will
126 clear the group, i.e. `--map-user foo=`.
128 \--map-uid *old*=*new*
129 : restore *old* uid as *new* uid.
131 \--map-gid *old*=*new*
132 : restore *old* gid as *new* gid.
135 : increase log output. Given once, prints every
136 directory as it is restored; given twice, prints every
140 : don't show the progress meter. Normally, is stderr is
141 a tty, a progress display is printed that shows the
142 total number of files restored.
146 Create a simple test backup set:
149 $ bup save -n mybackup /etc/passwd /etc/profile
151 Restore just one file:
153 $ bup restore /mybackup/latest/etc/passwd
157 -rw-r--r-- 1 apenwarr apenwarr 1478 2010-09-08 03:06 passwd
159 Restore etc to test (no trailing slash):
161 $ bup restore -C test /mybackup/latest/etc
170 Restore the contents of etc to test (trailing slash):
172 $ bup restore -C test /mybackup/latest/etc/
180 Restore the contents of etc and etc's metadata to test (trailing
183 $ bup restore -C test /mybackup/latest/etc/.
186 # At this point test and etc's metadata will match.
192 Restore a tree without risk of unauthorized access:
194 # mkdir --mode 0700 restore-tmp
196 # bup restore -C restore-tmp /somebackup/latest/foo
199 # mv restore-tmp/foo somewhere
203 Restore a tree, remapping an old user and group to a new user and group:
205 # bup restore -C dest --map-user foo=bar --map-group baz=bax /x/latest/y
208 Restore a tree, remapping an old uid to a new uid. Note that the old
209 user must be erased so that bup won't prefer it over the uid:
211 # bup restore -C dest --map-user foo= --map-uid 1000=1042 /x/latest/y
214 An alternate way to do the same by quashing users/groups universally
215 with `--numeric-ids`:
217 # bup restore -C dest --numeric-ids --map-uid 1000=1042 /x/latest/y
222 `bup-save`(1), `bup-ftp`(1), `bup-fuse`(1), `bup-web`(1)
226 Part of the `bup`(1) suite.