/usr/share/doc/bup/bup-prune-older.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 | <!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="Rob Browning rlb@defaultvalue.org" />
<meta name="date" content="2017-04-01" />
<title>bup-prune-older(1) bup debian/0.29-3 | bup debian/0.29-3</title>
<style type="text/css">code{white-space: pre;}</style>
</head>
<body>
<div id="header">
<h1 class="title">bup-prune-older(1) bup debian/0.29-3 | bup debian/0.29-3</h1>
<h2 class="author">Rob Browning <a href="mailto:rlb@defaultvalue.org">rlb@defaultvalue.org</a></h2>
<h3 class="date">2017-04-01</h3>
</div>
<h1 id="name">NAME</h1>
<p>bup-prune-older - remove older saves (CAUTION: EXPERIMENTAL)</p>
<h1 id="synopsis">SYNOPSIS</h1>
<p>bup prune-older [options...] <<em>branch</em>...></p>
<h1 id="description">DESCRIPTION</h1>
<p><code>bup prune-older</code> removes (permanently deletes) all saves except those preserved by the various keep arguments detailed below. At least one keep argument must be specified. This command is equivalent to a suitable <code>bup rm</code> invocation followed by <code>bup gc</code>.</p>
<p>WARNING: This is one of the few bup commands that modifies your archive in intentionally destructive ways. Though if an attempt to <code>join</code> or <code>restore</code> the data you still care about after a <code>prune-older</code> succeeds, that's a fairly encouraging sign that the commands worked correctly. (The <code>t/compare-trees</code> command in the source tree can be used to help test before/after results.)</p>
<h1 id="keep-periods">KEEP PERIODS</h1>
<p>A <code>--keep</code> PERIOD (as required below) must be an integer followed by a scale, or "forever". For example, 12y specifies a PERIOD of twelve years. Here are the valid scales:</p>
<ul>
<li>s indicates seconds</li>
<li>min indicates minutes (60s)</li>
<li>h indicates hours (60m)</li>
<li>d indicates days (24h)</li>
<li>w indicates weeks (7d)</li>
<li>m indicates months (31d)</li>
<li>y indicates years (366d)</li>
<li>forever is infinitely far in the past</li>
</ul>
<p>As indicated, the PERIODS are computed with respect to the current time, or the <code>--wrt</code> value if specified, and do not respect any calendar, so <code>--keep-dailies-for 5d</code> means a period starting exactly 5 * 24 * 60 * 60 seconds before the starting point.</p>
<h1 id="options">OPTIONS</h1>
<dl>
<dt>--keep-all-for PERIOD</dt>
<dd>when no smaller time scale --keep option applies, retain all saves within the given period.
</dd>
<dt>--keep-dailies-for PERIOD</dt>
<dd>when no smaller time scale --keep option applies, retain the oldest save for any day within the given period.
</dd>
<dt>--keep-monthlies-for PERIOD</dt>
<dd>when no smaller time scale --keep option applies, retain the oldest save for any month within the given period.
</dd>
<dt>--keep-yearlies-for PERIOD</dt>
<dd>when no smaller time scale --keep option applies, retain the oldest save for any year within the given period.
</dd>
<dt>--wrt UTC_SECONDS</dt>
<dd>when computing a keep period, place the most recent end of the range at UTC_SECONDS, and any saves newer than this will be kept.
</dd>
<dt>--pretend</dt>
<dd><p>don't do anything, just list the actions that would be taken to standard output, one action per line like this:</p>
<pre><code>- SAVE
+ SAVE
...</code></pre>
</dd>
<dt>--gc</dt>
<dd>garbage collect the repository after removing the relevant saves. This is the default behavior, but it can be avoided with <code>--no-gc</code>.
</dd>
<dt>--gc-threshold N</dt>
<dd>only rewrite a packfile if it's over N percent garbage; otherwise leave it alone. The default threshold is 10%.
</dd>
<dt>-<em>#</em>, --compress <em>#</em></dt>
<dd>set the compression level when rewriting archive data to # (a value from 0-9, where 9 is the highest and 0 is no compression). The default is 1 (fast, loose compression).
</dd>
<dt>-v, --verbose</dt>
<dd>increase verbosity (can be specified more than once).
</dd>
</dl>
<h1 id="notes">NOTES</h1>
<p>When <code>--verbose</code> is specified, the save periods will be summarized to standard error with lines like this:</p>
<pre><code>keeping monthlies since 1969-07-20-201800
keeping all yearlies
...</code></pre>
<p>It's possible that the current implementation might not be able to format the date if, for example, it is far enough back in time. In that case, you will see something like this:</p>
<pre><code>keeping yearlies since -30109891477 seconds before 1969-12-31-180000
...</code></pre>
<h1 id="examples">EXAMPLES</h1>
<pre><code># Keep all saves for the past month, and any older monthlies for
# the past year. Delete everything else.
$ bup prune-older --keep-all-for 1m --keep-monthlies-for 1y
# Keep all saves for the past 6 months and delete everything else,
# but only on the semester branch.
$ bup prune-older --keep-all-for 6m semester</code></pre>
<h1 id="see-also">SEE ALSO</h1>
<p><code>bup-rm</code>(1), <code>bup-gc</code>(1), and <code>bup-fsck</code>(1)</p>
<h1 id="bup">BUP</h1>
<p>Part of the <code>bup</code>(1) suite.</p>
</body>
</html>
|