1 % bup-save(1) Bup %BUP_VERSION%
2 % Avery Pennarun <apenwarr@gmail.com>
7 bup-save - create a new bup backup set
11 bup save [-r *host*:*path*] <-t|-c|-n *name*> [-f *indexfile*]
12 [-v] [-q] [--smaller=*maxsize*] <paths...>
16 `bup save` saves the contents of the given files or paths
17 into a new backup set and optionally names that backup set.
19 Before trying to save files using `bup save`, you should
20 first update the index using `bup index`. The reasons
21 for separating the two steps are described in the man page
26 -r, --remote=*host*:*path*
27 : save the backup set to the given remote server. If
28 *path* is omitted, uses the default path on the remote
29 server (you still need to include the ':')
32 : after creating the backup set, print out the git tree
33 id of the resulting backup.
36 : after creating the backup set, print out the git commit
37 id of the resulting backup.
40 : after creating the backup set, create a git branch
41 named *name* so that the backup can be accessed using
42 that name. If *name* already exists, the new backup
43 will be considered a descendant of the old *name*.
44 (Thus, you can continually create new backup sets with
45 the same name, and later view the history of that
46 backup set to see how files have changed over time.)
48 -f, --indexfile=*indexfile*
49 : use a different index filename instead of
53 : increase verbosity (can be used more than once). With
54 one -v, prints every directory name as it gets backed up. With
55 two -v, also prints every filename.
58 : disable progress messages.
61 : don't back up files >= *maxsize* bytes. You can use
62 this to run frequent incremental backups of your small
63 files, which can usually be backed up quickly, and skip
64 over large ones (like virtual machine images) which
65 take longer. Then you can back up the large files
66 less frequently. Use a suffix like k, M, or G to
67 specify multiples of 1024, 1024*1024, 1024*1024*1024
71 : don't transmit more than *bytes/sec* bytes per second
72 to the server. This is good for making your backups
73 not suck up all your network bandwidth. Use a suffix
74 like k, M, or G to specify multiples of 1024,
75 1024*1024, 1024*1024*1024 respectively.
78 : strips the path that is given from all files and directories.
80 A directory */root/chroot/etc* saved with
81 "bup save -n chroot --strip /root/chroot" would be saved
84 --strip-prefix=*path-prefix*
85 : strips the given path-prefix *path-prefix* from all
86 files and directories.
88 A directory */root/chroots/webserver* saved with
89 "bup save -n webserver --strip-path=/root/chroots" would
90 be saved as */webserver/etc*
92 --graft=*old_path*=*new_path*
93 : a graft point *old_path*=*new_path* (can be used more than
96 A directory */root/chroot/a/etc* saved with
97 "bup save -n chroots --graft /root/chroot/a/etc=/chroots/a"
98 would be saved as */chroots/a/etc*
103 Indexing: 1981, done.
105 $ bup save -r myserver: -n my-pc-backup --bwlimit=50k /etc
106 Reading index: 1981, done.
107 Saving: 100.00% (998/998k, 1981/1981 files), done.
111 $ ls /home/joe/chroots/httpd
114 $ bup index -ux /home/joe/chroots/httpd
115 Indexing: 1337, done.
117 $ bup save --strip -n joes-httpd-chroot /home/joe/chroots/httpd
118 Reading index: 1337, done.
119 Saving: 100.00% (998/998k, 1337/1337 files), done.
121 $ bup ls joes-httpd-chroot/latest/
126 $ bup save --strip-prefix=/home/joe/chroots -n joes-chroots \
127 /home/joe/chroots/httpd
128 Reading index: 1337, done.
129 Saving: 100.00% (998/998k, 1337/1337 files), done.
131 $ bup ls joes-chroots/latest/
135 $ bup save --graft /home/joe/chroots/httpd=/http-chroot \
137 /home/joe/chroots/httpd
138 Reading index: 1337, done.
139 Saving: 100.00% (998/998k, 1337/1337 files), done.
147 `bup-index`(1), `bup-split`(1), `bup-on`(1),
152 Part of the `bup`(1) suite.