/usr/share/doc/bup/bup-save.html is in bup-doc 0.29-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="generator" content="pandoc" />
<meta name="author" content="Avery Pennarun apenwarr@gmail.com" />
<meta name="date" content="2017-04-01" />
<title>bup-save(1) Bup debian/0.29-3</title>
<style type="text/css">code{white-space: pre;}</style>
</head>
<body>
<div id="header">
<h1 class="title">bup-save(1) Bup debian/0.29-3</h1>
<h2 class="author">Avery Pennarun <a href="mailto:apenwarr@gmail.com">apenwarr@gmail.com</a></h2>
<h3 class="date">2017-04-01</h3>
</div>
<h1 id="name">NAME</h1>
<p>bup-save - create a new bup backup set</p>
<h1 id="synopsis">SYNOPSIS</h1>
<p>bup save [-r <em>host</em>:<em>path</em>] <-t|-c|-n <em>name</em>> [-#] [-f <em>indexfile</em>] [-v] [-q] [--smaller=<em>maxsize</em>] <paths...>;</p>
<h1 id="description">DESCRIPTION</h1>
<p><code>bup save</code> saves the contents of the given files or paths into a new backup set and optionally names that backup set.</p>
<p>Note that in order to refer to your backup set later (i.e. for restoration), you must either specify <code>--name</code> (the normal case), or record the tree or commit id printed by <code>--tree</code> or <code>--commit</code>.</p>
<p>Before trying to save files using <code>bup save</code>, you should first update the index using <code>bup index</code>. The reasons for separating the two steps are described in the man page for <code>bup-index</code>(1).</p>
<p>By default, metadata will be saved for every path, and the metadata for any unindexed parent directories of indexed paths will be taken directly from the filesystem. However, if <code>--strip</code>, <code>--strip-path</code>, or <code>--graft</code> is specified, metadata will not be saved for the root directory (<em>/</em>). See <code>bup-restore</code>(1) for more information about the handling of metadata.</p>
<h1 id="options">OPTIONS</h1>
<dl>
<dt>-r, --remote=<em>host</em>:<em>path</em></dt>
<dd>save the backup set to the given remote server. If <em>path</em> is omitted, uses the default path on the remote server (you still need to include the ':'). The connection to the remote server is made with SSH. If you'd like to specify which port, user or private key to use for the SSH connection, we recommend you use the <code>~/.ssh/config</code> file.
</dd>
<dt>-t, --tree</dt>
<dd>after creating the backup set, print out the git tree id of the resulting backup.
</dd>
<dt>-c, --commit</dt>
<dd>after creating the backup set, print out the git commit id of the resulting backup.
</dd>
<dt>-n, --name=<em>name</em></dt>
<dd>after creating the backup set, create a git branch named <em>name</em> so that the backup can be accessed using that name. If <em>name</em> already exists, the new backup will be considered a descendant of the old <em>name</em>. (Thus, you can continually create new backup sets with the same name, and later view the history of that backup set to see how files have changed over time.)
</dd>
<dt>-d, --date=<em>date</em></dt>
<dd>specify the date of the backup, in seconds since the epoch, instead of the current time.
</dd>
<dt>-f, --indexfile=<em>indexfile</em></dt>
<dd>use a different index filename instead of <code>$BUP_DIR/bupindex</code>.
</dd>
<dt>-v, --verbose</dt>
<dd>increase verbosity (can be used more than once). With one -v, prints every directory name as it gets backed up. With two -v, also prints every filename.
</dd>
<dt>-q, --quiet</dt>
<dd>disable progress messages.
</dd>
<dt>--smaller=<em>maxsize</em></dt>
<dd>don't back up files >= <em>maxsize</em> bytes. You can use this to run frequent incremental backups of your small files, which can usually be backed up quickly, and skip over large ones (like virtual machine images) which take longer. Then you can back up the large files less frequently. Use a suffix like k, M, or G to specify multiples of 1024, 1024<em>1024, 1024</em>1024*1024 respectively.
</dd>
<dt>--bwlimit=<em>bytes/sec</em></dt>
<dd>don't transmit more than <em>bytes/sec</em> bytes per second to the server. This is good for making your backups not suck up all your network bandwidth. Use a suffix like k, M, or G to specify multiples of 1024, 1024<em>1024, 1024</em>1024*1024 respectively.
</dd>
<dt>--strip</dt>
<dd><p>strips the path that is given from all files and directories.</p>
<p>A directory <em>/root/chroot/etc</em> saved with "bup save -n chroot --strip /root/chroot" would be saved as <em>/etc</em>. Note that currently, metadata will not be saved for the root directory (<em>/</em>) when this option is specified.</p>
</dd>
<dt>--strip-path=<em>path-prefix</em></dt>
<dd><p>strips the given path prefix <em>path-prefix</em> from all files and directories.</p>
<p>A directory <em>/root/chroot/webserver</em> saved with "bup save -n webserver --strip-path=/root/chroot" would be saved as <em>/webserver/etc</em>. Note that currently, metadata will not be saved for the root directory (<em>/</em>) when this option is specified.</p>
</dd>
<dt>--graft=<em>old_path</em>=<em>new_path</em></dt>
<dd><p>a graft point <em>old_path</em>=<em>new_path</em> (can be used more than once).</p>
<p>A directory <em>/root/chroot/a/etc</em> saved with "bup save -n chroot --graft /root/chroot/a=/chroot/a" would be saved as <em>/chroot/a/etc</em>. Note that currently, metadata will not be saved for the root directory (<em>/</em>) when this option is specified.</p>
</dd>
<dt>-<em>#</em>, --compress=<em>#</em></dt>
<dd>set the compression level to # (a value from 0-9, where 9 is the highest and 0 is no compression). The default is 1 (fast, loose compression)
</dd>
</dl>
<h1 id="examples">EXAMPLES</h1>
<pre><code>$ bup index -ux /etc
Indexing: 1981, done.
$ bup save -r myserver: -n my-pc-backup --bwlimit=50k /etc
Reading index: 1981, done.
Saving: 100.00% (998/998k, 1981/1981 files), done.
$ ls /home/joe/chroot/httpd
bin var
$ bup index -ux /home/joe/chroot/httpd
Indexing: 1337, done.
$ bup save --strip -n joes-httpd-chroot /home/joe/chroot/httpd
Reading index: 1337, done.
Saving: 100.00% (998/998k, 1337/1337 files), done.
$ bup ls joes-httpd-chroot/latest/
bin/
var/
$ bup save --strip-path=/home/joe/chroot -n joes-chroot \
/home/joe/chroot/httpd
Reading index: 1337, done.
Saving: 100.00% (998/998k, 1337/1337 files), done.
$ bup ls joes-chroot/latest/
httpd/
$ bup save --graft /home/joe/chroot/httpd=/http-chroot \
-n joe
/home/joe/chroot/httpd
Reading index: 1337, done.
Saving: 100.00% (998/998k, 1337/1337 files), done.
$ bup ls joe/latest/
http-chroot/</code></pre>
<h1 id="see-also">SEE ALSO</h1>
<p><code>bup-index</code>(1), <code>bup-split</code>(1), <code>bup-on</code>(1), <code>bup-restore</code>(1), <code>ssh_config</code>(5)</p>
<h1 id="bup">BUP</h1>
<p>Part of the <code>bup</code>(1) suite.</p>
</body>
</html>
|