Commit 066601d0 authored by bescoto's avatar bescoto

Added note on how to skip regressing


git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup@417 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
parent c3b644da
...@@ -27,8 +27,14 @@ bandwidth usage, as in rsync's --bwlimit option?</a></li> ...@@ -27,8 +27,14 @@ bandwidth usage, as in rsync's --bwlimit option?</a></li>
memory leak?</a></li> memory leak?</a></li>
<li><a href="#dir_not_empty">I use NFS and keep getting some error that includes "OSError: [Errno 39] Directory not empty"</a></li> <li><a href="#dir_not_empty">I use NFS and keep getting some error that includes "OSError: [Errno 39] Directory not empty"</a></li>
<li><a href="#regress_failure">For some reason rdiff-backup failed
while backing up. Now every time it runs it says "regressing
destination" and then fails again. What should I do?</a></li>
</ol> </ol>
<h3>Questions and Answers</h3> <h3>Questions and Answers</h3>
<ol> <ol>
...@@ -377,5 +383,24 @@ run rdiff-backup locally on both ends instead of over NFS. This ...@@ -377,5 +383,24 @@ run rdiff-backup locally on both ends instead of over NFS. This
should be faster anyway. should be faster anyway.
</li> </li>
<a name="regress_failure">
<li><strong>For some reason rdiff-backup failed
while backing up. Now every time it runs it says "regressing
destination" and then fails again. What should I do?</strong>
<P>Firstly, this shouldn't happen. If it does, it indicates a
corrupted destination directory, a bug in rdiff-backup, or some other
serious recurring problem.</p>
<p>However, here is a workaround that you might want to use, even
though it probably won't solve the underlying problem: In the
destination's rdiff-backup-data directory, there should be two
"current_mirror" files, for instance
current_mirror.2003-09-08T04:22:01-07:00.data and
current_mirror.2003-09-07T16:43:00-07:00.data. Just delete the one
with the earlier date. The next time rdiff-backup runs it won't try
regressing the destination.
</li>
</ol> </ol>
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment