From c5fa7e7f24c5f28e3267523f09a03ccfa6c18a4c Mon Sep 17 00:00:00 2001 From: bescoto Date: Fri, 12 Aug 2005 05:32:15 +0000 Subject: Updated FAQ, added note on free space, removed v2.2 message now that v2.2 is 4 years old. git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@609 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109 --- rdiff-backup/FAQ-body.html | 89 +++++++++++++++++++++++----------------------- 1 file changed, 44 insertions(+), 45 deletions(-) diff --git a/rdiff-backup/FAQ-body.html b/rdiff-backup/FAQ-body.html index 475e3ef..199df1e 100644 --- a/rdiff-backup/FAQ-body.html +++ b/rdiff-backup/FAQ-body.html @@ -2,11 +2,7 @@

Table of contents

-
  1. When I try to run rdiff-backup it says -"ImportError: No module named __future__" or "SyntaxError: invalid -syntax". What's happening?
    2. - -
  2. What do the different verbosity levels mean?
    3. +
    1. What do the different verbosity levels mean?
    2. Does rdiff-backup run under Windows?
      3. @@ -34,6 +30,10 @@ memory leak? while backing up. Now every time it runs it says "regressing destination" and then fails again. What should I do? +
    3. Where does rdiff-backup need free space and +how much is required? What is the problem if rdiff-backup says +"ValueError: Incorrect length of data produced"?
      4. +
    @@ -41,25 +41,6 @@ destination" and then fails again. What should I do?
      -
    1. When I try to run rdiff-backup it says "ImportError: No -module named __future__" or "SyntaxError: invalid syntax". What's -happening? - -

      rdiff-backup versions 0.2.x require Python version 2.1 or later, -and versions 0.3.x and later require Python version 2.2 or later. If -you don't know what version of python you are running, type in "python --V" from the shell. I'm sorry if this is inconvenient, but -rdiff-backup uses generators, iterators, nested scoping, and -static/class methods extensively, and these were only added in version -2.2.

      - -

      If you have two versions of python installed, and running "python" -defaults to an early version, you'll probably have to change the first -line of the rdiff-backup script. For instance, you could set it to:

      - -
      #!/usr/bin/env python2.2
      -
      2. -
    2. What do the different verbosity levels mean?

      There is no formal specification, but here is a rough description @@ -128,7 +109,9 @@ be autodetected and compensated for by rdiff-backup.

    3. Does rdiff-backup run under Mac OS X? -

      Yes, but there may be some issues installing librsync. The easiest +

      Yes, quite a few people seem to be using rdiff-backup under Mac OS +X. rdiff-backup can also backup resource forks to a traditional unix +filesystem, which is can be a handy feature for Mac users. The easiest option is probably to use Fink http://fink.sourceforge.net/, which can install rdiff-backup automatically for you. If you want to @@ -148,31 +131,18 @@ these instructions build it fine with all tests running OK make make install -

      Also, if you are backing up to a file system that is not case -sensitive you may need to use "--chars-to-quote A-Z". If you do use ---chars-to-quote, remember to use it with the same arguments when -restoring or listing increments.

    4. My backup set contains some files that I just realized I don't want/need backed up. How do I remove them from the backup volume to save space? -

      Let's take an example. Suppose you ran:

      +

      The only official way to remove files from an rdiff-backup +repository is by letting them expire using the --remove-older-than +option. Deleting increments from the rdiff-backup-data directory will +prevent you from recovering those files, but shouldn't prevent the +rest of the repository from being restored.

      -
      rdiff-backup /usr /backup
      - -

      and now realize that you don't want /usr/local backed up on /backup. -Next time you back up, you run:

      - -
      rdiff-backup --exclude /usr/local /usr /backup
      -so that /usr/local is no longer copied to /backup/usr/local. - -

      However, old information about /usr/local is still present in -/backup/rdiff-backup-data/increments/usr/local. You can try to -manually remove this old information, but it's safer to let it be -removed by rdiff-backup when you run it with the --remove-older-than -option.

    5. Does rdiff-backup work under Solaris? @@ -339,8 +309,8 @@ hard linked together, rdiff-backup may need tens of MB.

      If rdiff-backup seems to be leaking memory, it is probably because it is using an early version of librsync. librsync 0.9.5 -leaks lots of memory. Version 0.9.5.1 should not leak and is -available from the rdiff-backup homepage.

      +leaks lots of memory. Later versions should not leak and are +available from the librsync homepage.

    6. I use NFS and keep getting some error that includes "OSError: [Errno 39] Directory not empty" @@ -391,4 +361,33 @@ result in some extra files being backed up, but there shouldn't be any data loss.

      7. +
    7. Where does rdiff-backup need free +space and how much is required? What is the problem when rdiff-backup +says "ValueError: Incorrect length of data +produced"? + +

      When backing up, rdiff-backup needs free space in the mirror +directory. The amount of free space required is usually a bit more +than the size of the file getting backed up, but can be as much as +twice the size of the current file. For instance, suppose you ran +rdiff-backup foo bar and the largest file, +foo/largefile, was 1GB. Then rdiff-backup would need +1+GB of free space in the bar directory.

      + +

      When restoring, rdiff-backup needs free space in the default temp +directory. Under unix systems this is usually the /tmp +directory---see the entry for tempfile.tempdir in the Python +tempfile docs for more +information on the default temp directory. The amount of free space +required can vary, but it usually about the size of the largest file +being restored.

      + +

      Usually free space errors are intelligible, like IOError: +[Errno 28] No space left on device or similar. However, do to +a gzip quirk they may look like ValueError: Incorrect length of data produced.

      + +
      8. + +
    -- cgit v1.2.1