Merge lp:~louis/ubuntu/trusty/backuppc/backuppc-merge into lp:ubuntu/trusty/backuppc

[Louis Bouchard]

- Merged upstream debian
- Edited debian/patch/config.pl.diff to adapt to updated upstream
- Fixed double entry in debian/control Depends:
- fixed doc/BackupPC.pod according to previous version

[Chris J Arges (arges)]

I was able to run sponsor-patch on this and it built locally just fine. I reviewed the debdiff and it looks ok.

[Chris J Arges (arges)]

review: Approve

Unmerged revisions

41. By Louis Bouchard on 2014-01-06

* Merge from Debian unstable. Remaining changes:
  - debian/backuppc.init, debian/rules, debian/postinst: Do not call init
    script on shutdown and reboot (TearDown) (Debian #488660).
  - debian/control:
    + Remove estraneous libtime-modules-perl (Debian #734356).
    + Depend on default-mta | mail-transport-agent, instead of enumerating a
      long list of alternative MTAs.
* New upstream release. Closes: #716824
* Fix Typo in kill signal name (ALRM vs ARLM). Closes: #698441
* Enable Apache2 (2.4) configuration by default. Closes: #718550 #710956
* Non-maintainer upload.
* Patch BackupPC.pod for POD errors with Perl 5.18
  pod2man has become more strict with perl 5.18. The applied patch
  converts the non-7-bit clean character into UTF-8 and declares the
  file's encoding as such.
  Thanks to Dominic Hargreaves <email address hidden> (Closes: #719827)
* Non-maintainer upload.
* Do not ship /etc/backuppc/config.pl as a conffile; it is handled
  by ucf already (Closes: #706315)
* Added libtime-modules-perl dependency. Closes: #525395
* Remove /var/lib/backuppc/pc/localhost if it's empty
  Closes: #672372
* Added stuff to support Apache 2.4. Closes: #669765
* Added NICE support in /etc/default/backuppc. Closes: #639102
* Changed the default display date format. Closes: #663975

=== modified file 'ChangeLog' (properties changed: +x to -x)
--- ChangeLog	2011-09-19 00:55:51 +0000
+++ ChangeLog	2014-01-06 14:04:46 +0000
@@ -11,13 +11,79 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 #========================================================================
 
 #------------------------------------------------------------------------
+# Version 3.3.0, 14 Apr 2013
+#------------------------------------------------------------------------
+
+* Changed restore file name from restore.{zip|tar} to restore_$host_YYYY-MM-DD.{zip|tar},
+  where the date is the start date of the backup.  Originally suggested by Brad Alexander,
+  with a healthy debate among Les, Holger, Jeffrey, Adam, Carl and others.
+
+* Changed the timeStamp2 function in lib/BackupPC/CGI/Lib.pm so that times more than 330
+  days ago also include the year.  More recent times continue to use just the day of month
+  and month.
+
+* Made the directory path display (when browsing backups or history) a sequence of links,
+  allowing any parent directory to be quick selected.
+
+* Added Japanese language file lib/BackupPC/Lang/ja.pm submitted by Rikiya
+  Yamamoto.
+
+* Added Ukrainian language file lib/BackupPC/Lang/uk.pm submitted by Serhiy Yakimchuck.
+
+* Added Russian language file lib/BackupPC/Lang/ru.pm submitted by Sergei Butakov.
+
+* Patch from Alexander Moisseev that fixed file name encodings in zip files.
+  The default charset is now utf8.  Added a menu option to override the codepage.
+
+* Removed -N option from smbclient command in conf/config.pl to remain compatible
+  with more recent versions (3.2.3 and later) of smbclient.  Reported and discussed
+  by various people on the mail list, most recently by Jeff Boyce, Les Mikesell and
+  Holger Parplies.  Alexander Moisseev also submitted a patch.
+
+  Using smbclient >= 3.2.3 with the -N option will give a "tree connect failed:
+  NT_STATUS_ACCESS_DENIED" error.
+
+* Reapplied a patch from Tyler Wagner for lib/BackupPC/CGI/HostInfo.pl so that
+  empty email status info doesn't appear.  Somehow this missed 3.2.1.
+
+* Fixed check on $parfile in bin/BackupPC_archiveHost since it is numeric.
+  Fix submitted by Tim Massey.
+
+* Ensure $num is numeric in lib/BackupPC/CGI/View.pm error message
+  to avoid XSS attack.  Report and patch by Jamie Strandboge.
+
+* Ensure $num and $share in lib/BackupPC/CGI/RestoreFile.pm error messages
+  are escaped, to avoid XSS vulnerability.  Report and patch by Jamie Strandboge.
+  Also added some additional error checking and tweaked the handling of the
+  invalid number error message.
+
+* Fixed qw(...) deprecated syntax warnings in lib/BackupPC/Storage/Text.pm
+  and lib/BackupPC/Lib.pm.  Patch supplied by Juergen Harms.  Also got a
+  patch from Alexander Moisseev and report from Richard Shaw.
+
+* Fixed error in bin/BackupPC_sendEmail that caused accumulation of
+  per-host errors in the admin email to be skipped if a host's user
+  is not defined.  Reported by Marco Dalla Via.
+
+* Fixed lib/BackupPC/CGI/RSS.pm so that the base_url is correct for https.
+  Report and fix by Samuel Monsarrat.
+
+* Added more careful checking that IO::Dirent returns valid inodes and file types.
+  Suggested by Daniel Harvey.
+
+* Removed redundant setting of $Lang{CfgEdit_Title_Other} from all the Lang files.
+
+* Applied couple of fixes to Lib.pm suggested by Jeffrey Kosowsky for special case of where
+  configuration commands are fragments of perl code.
+
+#------------------------------------------------------------------------
 # Version 3.2.1, 24 Apr 2011
 #------------------------------------------------------------------------
 
 
=== modified file 'LICENSE' (properties changed: +x to -x)
=== modified file 'README' (properties changed: +x to -x)
--- README	2011-09-19 00:55:51 +0000
+++ README	2014-01-06 14:04:46 +0000
@@ -1,11 +1,11 @@
 
                               BackupPC
 
-                            Version 3.2.1
-
-                            24 Apr 2011
-
-         Copyright (C) 2001-2010 Craig Barratt.  All rights reserved.
+                            Version 3.3.0
+
+                            14 Apr 2013
+
+         Copyright (C) 2001-2013  Craig Barratt.  All rights reserved.
 
       This program is free software; you can redistribute it and/or
       modify it under the terms of the GNU General Public License.
@@ -28,8 +28,8 @@
 
 To install BackupPC run these commands as root:
 
-    tar zxf BackupPC-3.2.1.tar.gz
-    cd BackupPC-3.2.1
+    tar zxf BackupPC-3.3.0.tar.gz
+    cd BackupPC-3.3.0
     perl configure.pl
 
 This will automatically determine some system information and prompt you
 
=== modified file 'bin/BackupPC'
--- bin/BackupPC	2011-09-19 00:55:51 +0000
+++ bin/BackupPC	2014-01-06 14:04:46 +0000
@@ -29,7 +29,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -47,7 +47,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_archive'
--- bin/BackupPC_archive	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_archive	2014-01-06 14:04:46 +0000
@@ -11,7 +11,7 @@
 #   Josh Marshall
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -29,7 +29,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_archiveHost'
--- bin/BackupPC_archiveHost	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_archiveHost	2014-01-06 14:04:46 +0000
@@ -20,7 +20,7 @@
 #   Josh Marshall
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -38,7 +38,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
@@ -154,7 +154,7 @@
 # ie: not a tape device).
 #
 if ( -d $outLoc && -x $parPath ) {
-    if ( length($parfile) ) {
+    if ( length($parfile) && $parfile != 0 ) {
         print("Running $parPath to create parity files\n");
 	my $parCmd = "$parPath c -r$parfile $outLocE/$host.$bkupNum.tar$fileExt.par2 $outLocE/$host.$bkupNum.tar$fileExt*";
         $ret = system($parCmd);
 
=== modified file 'bin/BackupPC_archiveStart'
--- bin/BackupPC_archiveStart	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_archiveStart	2014-01-06 14:04:46 +0000
@@ -17,7 +17,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2007-2009  Craig Barratt
+#   Copyright (C) 2007-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -35,7 +35,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_attribPrint'
--- bin/BackupPC_attribPrint	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_attribPrint	2014-01-06 14:04:46 +0000
@@ -13,7 +13,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2005-2009  Craig Barratt
+#   Copyright (C) 2005-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -31,7 +31,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_dump'
--- bin/BackupPC_dump	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_dump	2014-01-06 14:04:46 +0000
@@ -59,7 +59,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -77,7 +77,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
@@ -1066,7 +1066,7 @@
 	    # Send ALRMs to BackupPC_tarExtract if we are using it
 	    #
 	    if ( $tarPid > 0 ) {
-		kill($bpc->sigName2num("ARLM"), $tarPid);
+		kill($bpc->sigName2num("ALRM"), $tarPid);
 	    }
 
 	    #
 
=== modified file 'bin/BackupPC_fixupBackupSummary'
--- bin/BackupPC_fixupBackupSummary	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_fixupBackupSummary	2014-01-06 14:04:46 +0000
@@ -12,7 +12,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2005-2009  Craig Barratt
+#   Copyright (C) 2005-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -30,7 +30,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_link'
--- bin/BackupPC_link	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_link	2014-01-06 14:04:46 +0000
@@ -21,7 +21,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -39,7 +39,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_nightly'
--- bin/BackupPC_nightly	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_nightly	2014-01-06 14:04:46 +0000
@@ -37,7 +37,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -55,7 +55,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_restore'
--- bin/BackupPC_restore	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_restore	2014-01-06 14:04:46 +0000
@@ -11,7 +11,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -29,7 +29,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_sendEmail'
--- bin/BackupPC_sendEmail	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_sendEmail	2014-01-06 14:04:46 +0000
@@ -13,7 +13,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -31,7 +31,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
@@ -186,8 +186,6 @@
     %Conf = $bpc->Conf();
     my $user = $Hosts->{$host}{user};
 
-    next if ( $user eq "" );
-
     #
     # Accumulate host errors for the admin email below
     #
@@ -204,6 +202,7 @@
               || $Conf{XferMethod} eq "archive"
               || $Conf{BackupsDisable}
               || $Hosts->{$host}{user} eq ""
+              || $user eq ""
           );
     my @Backups = $bpc->BackupInfoRead($host);
     my $numBackups = @Backups;
 
=== modified file 'bin/BackupPC_serverMesg'
--- bin/BackupPC_serverMesg	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_serverMesg	2014-01-06 14:04:46 +0000
@@ -25,7 +25,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -43,7 +43,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_tarCreate'
--- bin/BackupPC_tarCreate	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_tarCreate	2014-01-06 14:04:46 +0000
@@ -37,7 +37,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -55,7 +55,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_tarExtract'
--- bin/BackupPC_tarExtract	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_tarExtract	2014-01-06 14:04:46 +0000
@@ -9,7 +9,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -27,7 +27,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_tarPCCopy'
--- bin/BackupPC_tarPCCopy	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_tarPCCopy	2014-01-06 14:04:46 +0000
@@ -20,7 +20,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2005-2009  Craig Barratt
+#   Copyright (C) 2005-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -38,7 +38,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_trashClean'
--- bin/BackupPC_trashClean	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_trashClean	2014-01-06 14:04:46 +0000
@@ -11,7 +11,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -29,7 +29,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_zcat'
--- bin/BackupPC_zcat	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_zcat	2014-01-06 14:04:46 +0000
@@ -14,7 +14,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -32,7 +32,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'bin/BackupPC_zipCreate'
--- bin/BackupPC_zipCreate	2011-09-19 00:55:51 +0000
+++ bin/BackupPC_zipCreate	2014-01-06 14:04:46 +0000
@@ -21,7 +21,7 @@
 #       -r pathRemove   path prefix that will be replaced with pathAdd
 #       -p pathAdd      new path prefix
 #       -c level        compression level (default is 0, no compression)
-#       -e charset      charset for encoding file names (default: cp1252)
+#       -e charset      charset for encoding file names (default: utf8)
 #
 #     The -h, -n and -s options specify which dump is used to generate
 #     the zip archive.  The -r and -p options can be used to relocate
@@ -33,7 +33,7 @@
 #   Based on Backup_tarCreate by Craig Barratt <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2002-2009  Craig Barratt and Guillaume Filion
+#   Copyright (C) 2002-2013  Craig Barratt and Guillaume Filion
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -51,7 +51,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
@@ -93,7 +93,7 @@
      -r pathRemove   path prefix that will be replaced with pathAdd
      -p pathAdd      new path prefix
      -c level        compression level (default is 0, no compression)
-     -e charset      charset for encoding file names (default: cp1252)
+     -e charset      charset for encoding file names (default: utf8)
 EOF
     exit(1);
 }
@@ -135,7 +135,7 @@
     exit(1);
 }
 
-my $Charset = "cp1252";
+my $Charset = ""; # default: utf8
 $Charset = $opts{e} if ( $opts{e} ne "" );
 
 my $PathRemove = $1 if ( $opts{r} =~ /(.+)/ );
@@ -311,6 +311,14 @@
     # Specify the compression level for this member
     $zipmember->desiredCompressionLevel($compLevel) if ($compLevel =~ /[0-9]/);
     
+    if ( $Charset =~ /^(?:utf[-_]?8)?$/i ) {
+        # Set general purpose bit 11 for UTF-8 code page
+        $zipmember->{bitFlag} = $zipmember->{bitFlag} | 0x0800 ;
+    } elsif ( $Charset =~ /^cp(?:437|720|737|775|85[02578]|86[069]|874|93[26]|949|950)$/i ) {
+        # Set "version made by" field to 0 (MS-DOS) for OEM code pages
+        $zipmember->fileAttributeFormat('FA_MSDOS');
+    }
+    
     # Finally Zip the member
     $zipfh->addMember($zipmember);
 }
 
=== modified file 'cgi-bin/BackupPC_Admin'
--- cgi-bin/BackupPC_Admin	2011-09-19 00:55:51 +0000
+++ cgi-bin/BackupPC_Admin	2014-01-06 14:04:46 +0000
@@ -21,7 +21,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -39,7 +39,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
 
=== modified file 'conf/BackupPC_stnd.css'
--- conf/BackupPC_stnd.css	2011-09-19 00:55:51 +0000
+++ conf/BackupPC_stnd.css	2014-01-06 14:04:46 +0000
@@ -1,7 +1,7 @@
 /*
  * BackupPC standard CSS definitions
  *
- * Version 3.2.1, released 24 Apr 2011.
+ * Version 3.3.0, released 14 Apr 2013.
  *
  * See http://backuppc.sourceforge.net.
  *
@@ -9,7 +9,7 @@
  *   Craig Barratt  <[e-mail]>
  *
  * COPYRIGHT
- *   Copyright (C) 2004-2009  Craig Barratt
+ *   Copyright (C) 2004-2013  Craig Barratt
  */
 
 body {
 
=== modified file 'conf/BackupPC_stnd_orig.css'
--- conf/BackupPC_stnd_orig.css	2011-09-19 00:55:51 +0000
+++ conf/BackupPC_stnd_orig.css	2014-01-06 14:04:46 +0000
@@ -1,7 +1,7 @@
 /*
  * BackupPC standard CSS definitions
  *
- * Version 3.2.1, released 24 Apr 2011.
+ * Version 3.3.0, released 14 Apr 2013.
  *
  * See http://backuppc.sourceforge.net.
  *
@@ -9,7 +9,7 @@
  *   Craig Barratt  <[e-mail]>
  *
  * COPYRIGHT
- *   Copyright (C) 2004-2009  Craig Barratt
+ *   Copyright (C) 2004-2013  Craig Barratt
  */
 
 body {
 
=== modified file 'conf/config.pl'
--- conf/config.pl	2011-03-07 11:35:50 +0000
+++ conf/config.pl	2014-01-06 14:04:46 +0000
@@ -29,7 +29,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   See http://backuppc.sourceforge.net.
 #
@@ -976,7 +976,7 @@
 # redirection and pipes; put that in a script if you need it.
 #
 $Conf{SmbClientFullCmd} = '$smbClientPath \\\\$host\\$shareName'
-	    . ' $I_option -U $userName -E -N -d 1'
+	    . ' $I_option -U $userName -E -d 1'
             . ' -c tarmode\\ full -Tc$X_option - $fileList';
 
 #
@@ -990,7 +990,7 @@
 # redirection and pipes; put that in a script if you need it.
 #
 $Conf{SmbClientIncrCmd} = '$smbClientPath \\\\$host\\$shareName'
-	    . ' $I_option -U $userName -E -N -d 1'
+	    . ' $I_option -U $userName -E -d 1'
 	    . ' -c tarmode\\ full -TcN$X_option $timeStampFile - $fileList';
 
 #
@@ -1008,7 +1008,7 @@
 # redirection and pipes; put that in a script if you need it.
 #
 $Conf{SmbClientRestoreCmd} = '$smbClientPath \\\\$host\\$shareName'
-            . ' $I_option -U $userName -E -N -d 1'
+            . ' $I_option -U $userName -E -d 1'
             . ' -c tarmode\\ full -Tx -';
 
 ###########################################################################
@@ -1047,11 +1047,14 @@
 $Conf{TarShareName} = '/';
 
 #
-# Full command to run tar on the client.  GNU tar is required.  You will
+# Command to run tar on the client.  GNU tar is required.  You will
 # need to fill in the correct paths for ssh2 on the local host (server)
 # and GNU tar on the client.  Security caution: normal users should not
 # allowed to write to these executable files or directories.
 #
+# $Conf{TarClientCmd} is appended with with either $Conf{TarFullArgs} or
+# $Conf{TarIncrArgs} to create the final command that is run.
+#
 # See the documentation for more information about setting up ssh2 keys.
 #
 # If you plan to use NFS then tar just runs locally and ssh2 is not needed.
 
=== modified file 'conf/hosts'
--- conf/hosts	2010-11-21 14:59:53 +0000
+++ conf/hosts	2014-01-06 14:04:46 +0000
@@ -41,7 +41,7 @@
 #   Craig Barratt  <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2009  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   See http://backuppc.sourceforge.net.
 #
 
=== modified file 'configure.pl' (properties changed: +x to -x)
--- configure.pl	2011-09-19 00:55:51 +0000
+++ configure.pl	2014-01-06 14:04:46 +0000
@@ -19,7 +19,7 @@
 #   Craig Barratt <[e-mail]>
 #
 # COPYRIGHT
-#   Copyright (C) 2001-2010  Craig Barratt
+#   Copyright (C) 2001-2013  Craig Barratt
 #
 #   This program is free software; you can redistribute it and/or modify
 #   it under the terms of the GNU General Public License as published by
@@ -37,7 +37,7 @@
 #
 #========================================================================
 #
-# Version 3.2.1, released 24 Apr 2011.
+# Version 3.3.0, released 14 Apr 2013.
 #
 # See http://backuppc.sourceforge.net.
 #
@@ -72,7 +72,7 @@
 BackupPC distribution.  This probably means you did not cd to the
 unpacked BackupPC distribution before running configure.pl, eg:
 
-    cd BackupPC-3.2.1
+    cd BackupPC-3.3.0
     ./configure.pl
 
 Please try again.
@@ -642,9 +642,12 @@
         lib/BackupPC/Lang/es.pm
         lib/BackupPC/Lang/fr.pm
         lib/BackupPC/Lang/it.pm
+        lib/BackupPC/Lang/ja.pm
         lib/BackupPC/Lang/nl.pm
         lib/BackupPC/Lang/pl.pm
         lib/BackupPC/Lang/pt_br.pm
+        lib/BackupPC/Lang/ru.pm
+        lib/BackupPC/Lang/uk.pm
         lib/BackupPC/Lang/zh_CN.pm
         lib/BackupPC/Storage/Text.pm
         lib/BackupPC/Xfer.pm
@@ -673,7 +676,7 @@
     #
     # Install new CSS file, making a backup copy if necessary
     #
-    my $cssBackup = "$DestDir$Conf{CgiImageDir}/BackupPC_stnd.css.pre-3.2.1";
+    my $cssBackup = "$DestDir$Conf{CgiImageDir}/BackupPC_stnd.css.pre-3.3.0";
     if ( -f "$DestDir$Conf{CgiImageDir}/BackupPC_stnd.css" && !-f $cssBackup ) {
 	rename("$DestDir$Conf{CgiImageDir}/BackupPC_stnd.css", $cssBackup);
     }
@@ -893,7 +896,7 @@
 #
 # Now backup and write the config file
 #
-my $confCopy = "$dest.pre-3.2.1";
+my $confCopy = "$dest.pre-3.3.0";
 if ( -f $dest && !-f $confCopy ) {
     #
     # Make copy of config file, preserving ownership and modes
 
=== modified file 'debian/README.Debian'
--- debian/README.Debian	2011-01-14 11:02:06 +0000
+++ debian/README.Debian	2014-01-06 14:04:46 +0000
@@ -105,5 +105,15 @@
 - Data directory is /var/lib/backuppc/
 
 
+/etc/default/backuppc
+---------------------
+
+You can change the nice value by adding a line like 'NICE=10' to 
+/etc/default/backuppc
+
+
+
+
+
 
  -- Ludovic Drolez <[e-mail]>, Mon, 16 Jun 2004 10:43:48 +0200
 
=== added file 'debian/backuppc.default'
--- debian/backuppc.default	1970-01-01 00:00:00 +0000
+++ debian/backuppc.default	2014-01-06 14:04:46 +0000
@@ -0,0 +1,2 @@
+# Nice BackupPC daemon value
+NICE=0
 
=== modified file 'debian/backuppc.init'
--- debian/backuppc.init	2013-01-06 03:04:32 +0000
+++ debian/backuppc.init	2014-01-06 14:04:46 +0000
@@ -23,6 +23,9 @@
 DATADIR=/var/lib/backuppc
 USER=backuppc
 NICE=0
+
+test -f /etc/default/backuppc && . /etc/default/backuppc
+
 #
 NAME=backuppc
 DAEMON=BackupPC
 
=== modified file 'debian/backuppc.templates'
--- debian/backuppc.templates	2009-12-18 10:44:41 +0000
+++ debian/backuppc.templates	2014-01-06 14:04:46 +0000
@@ -11,7 +11,7 @@
 Template: backuppc/reconfigure-webserver
 Type: multiselect
 Choices: apache2
-Default:
+Default: apache2
 _Description: Which web server would you like to reconfigure automatically:
  BackupPC supports any web server with CGI enabled, but this automatic
  configuration process only supports Apache.
 
=== modified file 'debian/changelog'
--- debian/changelog	2013-12-20 02:17:32 +0000
+++ debian/changelog	2014-01-06 14:04:46 +0000
@@ -1,3 +1,53 @@
+backuppc (3.3.0-1ubuntu1) trusty-proposed; urgency=low
+
+  * Merge from Debian unstable. Remaining changes:
+    - debian/backuppc.init, debian/rules, debian/postinst: Do not call init
+      script on shutdown and reboot (TearDown) (Debian #488660).
+    - debian/control:
+      + Remove estraneous libtime-modules-perl (Debian #734356).
+      + Depend on default-mta | mail-transport-agent, instead of enumerating a
+        long list of alternative MTAs.
+
+ -- Louis Bouchard <[e-mail]>  Mon, 06 Jan 2014 13:26:25 +0100
+
+backuppc (3.3.0-1) unstable; urgency=low
+
+  * New upstream release. Closes: #716824
+  * Fix Typo in kill signal name (ALRM vs ARLM). Closes: #698441
+  * Enable Apache2 (2.4) configuration by default. Closes: #718550 #710956
+
+ -- Ludovic Drolez <[e-mail]>  Thu, 12 Sep 2013 6:13:50 +0200
+
+backuppc (3.2.1-5.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Patch BackupPC.pod for POD errors with Perl 5.18
+    pod2man has become more strict with perl 5.18. The applied patch
+    converts the non-7-bit clean character into UTF-8 and declares the
+    file's encoding as such.
+    Thanks to Dominic Hargreaves <[e-mail]> (Closes: #719827)
+
+ -- Salvatore Bonaccorso <[e-mail]>  Sat, 24 Aug 2013 15:29:57 +0200
+
+backuppc (3.2.1-5.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Do not ship /etc/backuppc/config.pl as a conffile; it is handled
+    by ucf already (Closes: #706315)
+
+ -- Jonathan Wiltshire <[e-mail]>  Fri, 07 Jun 2013 11:42:08 +0100
+
+backuppc (3.2.1-5) unstable; urgency=low
+
+  * Added libtime-modules-perl dependency. Closes: #525395
+  * Remove /var/lib/backuppc/pc/localhost if it's empty
+    Closes: #672372
+  * Added stuff to support Apache 2.4. Closes: #669765
+  * Added NICE support in /etc/default/backuppc. Closes: #639102
+  * Changed the default display date format. Closes: #663975
+
+ -- Ludovic Drolez <[e-mail]>  Thu, 03 Jan 2013 17:27:35 +0100
+
 backuppc (3.2.1-4ubuntu2) trusty; urgency=medium
 
   * Specify pod2man encoding.
 
=== modified file 'debian/patches/config.pl.diff'
--- debian/patches/config.pl.diff	2011-03-07 11:35:50 +0000
+++ debian/patches/config.pl.diff	2014-01-06 14:04:46 +0000
@@ -21,33 +21,6 @@
  $Conf{CatPath}   = '/bin/cat';
  $Conf{GzipPath}  = '/bin/gzip';
  $Conf{Bzip2Path} = '/bin/bzip2';
-@@ -952,7 +952,7 @@
- # redirection and pipes; put that in a script if you need it.
- #
- $Conf{SmbClientFullCmd} = '$smbClientPath \\\\$host\\$shareName'
--	    . ' $I_option -U $userName -E -N -d 1'
-+	    . ' $I_option -U $userName -E -d 1'
-             . ' -c tarmode\\ full -Tc$X_option - $fileList';
- 
- #
-@@ -966,7 +966,7 @@
- # redirection and pipes; put that in a script if you need it.
- #
- $Conf{SmbClientIncrCmd} = '$smbClientPath \\\\$host\\$shareName'
--	    . ' $I_option -U $userName -E -N -d 1'
-+	    . ' $I_option -U $userName -E -d 1'
- 	    . ' -c tarmode\\ full -TcN$X_option $timeStampFile - $fileList';
- 
- #
-@@ -984,7 +984,7 @@
- # redirection and pipes; put that in a script if you need it.
- #
- $Conf{SmbClientRestoreCmd} = '$smbClientPath \\\\$host\\$shareName'
--            . ' $I_option -U $userName -E -N -d 1'
-+            . ' $I_option -U $userName -E -d 1'
-             . ' -c tarmode\\ full -Tx -';
- 
- #
 @@ -1462,7 +1462,7 @@
  # Full path for ssh. Security caution: normal users should not
  # allowed to write to this file or directory.
 
=== modified file 'debian/postinst'
--- debian/postinst	2011-06-15 16:28:41 +0000
+++ debian/postinst	2014-01-06 14:04:46 +0000
@@ -52,6 +52,19 @@
 			> /etc/$webserver/httpd.conf
 	    fi
 	    # add new links
+	    
+	    # Apache 2.4 
+	    if [ -d /etc/$webserver/conf-available -a ! -f /etc/$webserver/conf-available/backuppc.conf -a ! -h /etc/$webserver/conf-available/backuppc.conf ]; then
+                ln -s /etc/backuppc/apache.conf /etc/$webserver/conf-available/backuppc.conf
+                [ -f /etc/$webserver/conf.d/backuppc.conf ] && rm /etc/$webserver/conf.d/backuppc.conf
+
+                if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
+                    . /usr/share/apache2/apache2-maintscript-helper
+            	    apache2_invoke enconf backuppc.conf
+                fi
+            fi
+
+	    # Apache < 2.4
 	    newfile=false
             if [ -d /etc/$webserver/conf.d -a ! -f /etc/$webserver/conf.d/backuppc.conf -a ! -h /etc/$webserver/conf.d/backuppc.conf ]; then
                 ln -s /etc/backuppc/apache.conf /etc/$webserver/conf.d/backuppc.conf
@@ -59,10 +72,10 @@
 		if [ "$webservers_rst" = "true" ]; then
 		    # restart
     		    if [ -x /usr/sbin/invoke-rc.d ]; then
-        		    invoke-rc.d $webserver restart
+        		    invoke-rc.d $webserver reload
     		    else
-        		    /etc/init.d/$webserver restart
-    		    fi		    
+        		    /etc/init.d/$webserver reload
+    		    fi
 		fi
             fi
 	    ;;
 
=== modified file 'debian/postrm'
--- debian/postrm	2011-06-15 16:28:41 +0000
+++ debian/postrm	2014-01-06 14:04:46 +0000
@@ -43,9 +43,9 @@
 			    if [ "$webservers_rst" = "true" ]; then
 				# restart
     				if [ -x /usr/sbin/invoke-rc.d ]; then
-        				invoke-rc.d $webserver restart
+        				invoke-rc.d $webserver reload
 	    			else
-        				/etc/init.d/$webserver restart
+        				/etc/init.d/$webserver reload
     				fi		    
 			    fi
         		fi
@@ -54,6 +54,14 @@
 		done
 	fi
 
+        if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
+            . /usr/share/apache2/apache2-maintscript-helper
+	    apache2_invoke disconf backuppc.conf
+        fi
+
+	if [ -h /etc/apache2/conf-available/backuppc.conf ]; then
+	    rm -f /etc/apache2/conf-available/backuppc.conf
+	fi
 
 	dpkg-statoverride --remove --force /usr/share/backuppc/cgi-bin/index.cgi
 	dpkg-statoverride --remove --force /usr/lib/backuppc/cgi-bin/index.cgi
@@ -61,6 +69,7 @@
 	if [ -x "/usr/bin/ucf" ]; then
 		ucf --purge /etc/backuppc/config.pl
 	fi
+	rmdir --ignore-fail-on-non-empty /var/lib/backuppc/pc/localhost/
 
         ;;
     remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
 
=== modified file 'debian/rules'
--- debian/rules	2011-06-15 16:28:41 +0000
+++ debian/rules	2014-01-06 14:04:46 +0000
@@ -51,6 +51,7 @@
 	dh_installdirs
 
 	# Add here commands to install the package into debian/backuppc.
+	chmod 755 ./configure.pl
 	./configure.pl --batch --no-fhs --hostname XXXXXX --uid-ignore \
 	    --install-dir /usr/share/backuppc --dest-dir $(CURDIR)/debian/backuppc/ \
 	    --data-dir /var/lib/backuppc --cgi-dir /usr/share/backuppc/cgi-bin \
@@ -73,6 +74,7 @@
 	(cd debian/backuppc/usr/share/backuppc/cgi-bin; ln -s ../image; ln -s /usr/lib/backuppc/cgi-bin/index.cgi )
 	patch --no-backup-if-mismatch -p0 < debian/patches/config.pl.diff
 	install --mode=644 debian/backuppc/etc/backuppc/config.pl debian/backuppc/usr/share/backuppc/conf
+	rm -rf debian/backuppc/etc/backuppc/config.pl
 
 # Build architecture-independent files here.
 binary-indep: build install
 
=== modified file 'doc/BackupPC.html'
--- doc/BackupPC.html	2011-09-19 00:55:51 +0000
+++ doc/BackupPC.html	2014-01-06 14:04:46 +0000
@@ -4,1267 +4,854 @@
 <head>
 <title>BackupPC</title>
 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-<link rev="made" href="mailto:[e-mail]" />
+<link rev="made" href="mailto:[e-mail]" />
 </head>
 
 <body style="background-color: white">
 <table border="0" width="100%" cellspacing="0" cellpadding="3">
-<tr><td class="block" style="background-color: #cccccc" valign="middle">
-<big><strong><span class="block">&nbsp;BackupPC</span></strong></big>
+<tr><td class="_podblock_" style="background-color: #cccccc" valign="middle">
+<big><strong><span class="_podblock_">&nbsp;BackupPC</span></strong></big>
 </td></tr>
 </table>
 
 
-<!-- INDEX BEGIN -->
-<div name="index">
-<p><a name="__index__"></a></p>
-
-<ul>
-
-	<li><a href="#backuppc_introduction">BackupPC Introduction</a></li>
-	<ul>
-
-		<li><a href="#overview">Overview</a></li>
-		<li><a href="#backup_basics">Backup basics</a></li>
-		<li><a href="#resources">Resources</a></li>
-		<li><a href="#road_map">Road map</a></li>
-		<li><a href="#you_can_help">You can help</a></li>
-	</ul>
-
-	<li><a href="#installing_backuppc">Installing BackupPC</a></li>
-	<ul>
-
-		<li><a href="#requirements">Requirements</a></li>
-		<li><a href="#what_type_of_storage_space_do_i_need">What type of storage space do I need?</a></li>
-		<li><a href="#how_much_disk_space_do_i_need">How much disk space do I need?</a></li>
-		<li><a href="#step_1__getting_backuppc">Step 1: Getting BackupPC</a></li>
-		<li><a href="#step_2__installing_the_distribution">Step 2: Installing the distribution</a></li>
-		<li><a href="#step_3__setting_up_config_pl">Step 3: Setting up config.pl</a></li>
-		<li><a href="#step_4__setting_up_the_hosts_file">Step 4: Setting up the hosts file</a></li>
-		<li><a href="#step_5__client_setup">Step 5: Client Setup</a></li>
-		<li><a href="#step_6__running_backuppc">Step 6: Running BackupPC</a></li>
-		<li><a href="#step_7__talking_to_backuppc">Step 7: Talking to BackupPC</a></li>
-		<li><a href="#step_8__checking_email_delivery">Step 8: Checking email delivery</a></li>
-		<li><a href="#step_9__cgi_interface">Step 9: CGI interface</a></li>
-		<li><a href="#how_backuppc_finds_hosts">How BackupPC Finds Hosts</a></li>
-		<li><a href="#other_installation_topics">Other installation topics</a></li>
-		<li><a href="#fixing_installation_problems">Fixing installation problems</a></li>
-	</ul>
-
-	<li><a href="#restore_functions">Restore functions</a></li>
-	<ul>
-
-		<li><a href="#cgi_restore_options">CGI restore options</a></li>
-		<li><a href="#command_line_restore_options">Command-line restore options</a></li>
-	</ul>
-
-	<li><a href="#archive_functions">Archive functions</a></li>
-	<ul>
-
-		<li><a href="#configuring_an_archive_host">Configuring an Archive Host</a></li>
-		<li><a href="#starting_an_archive">Starting an Archive</a></li>
-		<li><a href="#starting_an_archive_from_the_command_line">Starting an Archive from the command line</a></li>
-	</ul>
-
-	<li><a href="#other_cgi_functions">Other CGI Functions</a></li>
-	<ul>
-
-		<li><a href="#configuration_and_host_editor">Configuration and Host Editor</a></li>
-		<li><a href="#rss">RSS</a></li>
-	</ul>
-
-	<li><a href="#backuppc_design">BackupPC Design</a></li>
-	<ul>
-
-		<li><a href="#some_design_issues">Some design issues</a></li>
-		<li><a href="#backuppc_operation">BackupPC operation</a></li>
-		<li><a href="#storage_layout">Storage layout</a></li>
-		<li><a href="#compressed_file_format">Compressed file format</a></li>
-		<li><a href="#rsync_checksum_caching">Rsync checksum caching</a></li>
-		<li><a href="#file_name_mangling">File name mangling</a></li>
-		<li><a href="#special_files">Special files</a></li>
-		<li><a href="#attribute_file_format">Attribute file format</a></li>
-		<li><a href="#optimizations">Optimizations</a></li>
-		<li><a href="#limitations">Limitations</a></li>
-		<li><a href="#security_issues">Security issues</a></li>
-	</ul>
-
-	<li><a href="#configuration_file">Configuration File</a></li>
-	<ul>
-
-		<li><a href="#modifying_the_main_configuration_file">Modifying the main configuration file</a></li>
-	</ul>
-
-	<li><a href="#configuration_parameters">Configuration Parameters</a></li>
-	<ul>
-
-		<li><a href="#general_server_configuration">General server configuration</a></li>
-		<li><a href="#what_to_backup_and_when_to_do_it">What to backup and when to do it</a></li>
-		<li><a href="#how_to_backup_a_client">How to backup a client</a></li>
-		<li><a href="#samba_configuration">Samba Configuration</a></li>
-		<li><a href="#tar_configuration">Tar Configuration</a></li>
-		<li><a href="#rsync_rsyncd_configuration">Rsync/Rsyncd Configuration</a></li>
-		<li><a href="#ftp_configuration">FTP Configuration</a></li>
-		<li><a href="#archive_configuration">Archive Configuration</a></li>
-		<li><a href="#email_reminders__status_and_messages">Email reminders, status and messages</a></li>
-		<li><a href="#cgi_user_interface_configuration_settings">CGI user interface configuration settings</a></li>
-	</ul>
-
-	<li><a href="#version_numbers">Version Numbers</a></li>
-	<li><a href="#author">Author</a></li>
-	<li><a href="#copyright">Copyright</a></li>
-	<li><a href="#credits">Credits</a></li>
-	<li><a href="#license">License</a></li>
+
+<ul id="index">
+  <li><a href="#BackupPC-Introduction">BackupPC Introduction</a>
+    <ul>
+      <li><a href="#Overview">Overview</a></li>
+      <li><a href="#Backup-basics">Backup basics</a></li>
+      <li><a href="#Resources">Resources</a></li>
+      <li><a href="#Road-map">Road map</a></li>
+      <li><a href="#You-can-help">You can help</a></li>
+    </ul>
+  </li>
+  <li><a href="#Installing-BackupPC">Installing BackupPC</a>
+    <ul>
+      <li><a href="#Requirements">Requirements</a></li>
+      <li><a href="#What-type-of-storage-space-do-I-need-">What type of storage space do I need?</a></li>
+      <li><a href="#How-much-disk-space-do-I-need-">How much disk space do I need?</a></li>
+      <li><a href="#Step-1:-Getting-BackupPC">Step 1: Getting BackupPC</a></li>
+      <li><a href="#Step-2:-Installing-the-distribution">Step 2: Installing the distribution</a></li>
+      <li><a href="#Step-3:-Setting-up-config.pl">Step 3: Setting up config.pl</a></li>
+      <li><a href="#Step-4:-Setting-up-the-hosts-file">Step 4: Setting up the hosts file</a></li>
+      <li><a href="#Step-5:-Client-Setup">Step 5: Client Setup</a></li>
+      <li><a href="#Step-6:-Running-BackupPC">Step 6: Running BackupPC</a></li>
+      <li><a href="#Step-7:-Talking-to-BackupPC">Step 7: Talking to BackupPC</a></li>
+      <li><a href="#Step-8:-Checking-email-delivery">Step 8: Checking email delivery</a></li>
+      <li><a href="#Step-9:-CGI-interface">Step 9: CGI interface</a></li>
+      <li><a href="#How-BackupPC-Finds-Hosts">How BackupPC Finds Hosts</a></li>
+      <li><a href="#Other-installation-topics">Other installation topics</a></li>
+      <li><a href="#Fixing-installation-problems">Fixing installation problems</a></li>
+    </ul>
+  </li>
+  <li><a href="#Restore-functions">Restore functions</a>
+    <ul>
+      <li><a href="#CGI-restore-options">CGI restore options</a></li>
+      <li><a href="#Command-line-restore-options">Command-line restore options</a></li>
+    </ul>
+  </li>
+  <li><a href="#Archive-functions">Archive functions</a>
+    <ul>
+      <li><a href="#Configuring-an-Archive-Host">Configuring an Archive Host</a></li>
+      <li><a href="#Starting-an-Archive">Starting an Archive</a></li>
+      <li><a href="#Starting-an-Archive-from-the-command-line">Starting an Archive from the command line</a></li>
+    </ul>
+  </li>
+  <li><a href="#Other-CGI-Functions">Other CGI Functions</a>
+    <ul>
+      <li><a href="#Configuration-and-Host-Editor">Configuration and Host Editor</a></li>
+      <li><a href="#RSS">RSS</a></li>
+    </ul>
+  </li>
+  <li><a href="#BackupPC-Design">BackupPC Design</a>
+    <ul>
+      <li><a href="#Some-design-issues">Some design issues</a></li>
+      <li><a href="#BackupPC-operation">BackupPC operation</a></li>
+      <li><a href="#Storage-layout">Storage layout</a></li>
+      <li><a href="#Compressed-file-format">Compressed file format</a></li>
+      <li><a href="#Rsync-checksum-caching">Rsync checksum caching</a></li>
+      <li><a href="#File-name-mangling">File name mangling</a></li>
+      <li><a href="#Special-files">Special files</a></li>
+      <li><a href="#Attribute-file-format">Attribute file format</a></li>
+      <li><a href="#Optimizations">Optimizations</a></li>
+      <li><a href="#Limitations">Limitations</a></li>
+      <li><a href="#Security-issues">Security issues</a></li>
+    </ul>
+  </li>
+  <li><a href="#Configuration-File">Configuration File</a>
+    <ul>
+      <li><a href="#Modifying-the-main-configuration-file">Modifying the main configuration file</a></li>
+    </ul>
+  </li>
+  <li><a href="#Configuration-Parameters">Configuration Parameters</a>
+    <ul>
+      <li><a href="#General-server-configuration">General server configuration</a></li>
+      <li><a href="#What-to-backup-and-when-to-do-it">What to backup and when to do it</a></li>
+      <li><a href="#How-to-backup-a-client">How to backup a client</a></li>
+      <li><a href="#Samba-Configuration">Samba Configuration</a></li>
+      <li><a href="#Tar-Configuration">Tar Configuration</a></li>
+      <li><a href="#Rsync-Rsyncd-Configuration">Rsync/Rsyncd Configuration</a></li>
+      <li><a href="#FTP-Configuration">FTP Configuration</a></li>
+      <li><a href="#Archive-Configuration">Archive Configuration</a></li>
+      <li><a href="#Email-reminders-status-and-messages">Email reminders, status and messages</a></li>
+      <li><a href="#CGI-user-interface-configuration-settings">CGI user interface configuration settings</a></li>
+    </ul>
+  </li>
+  <li><a href="#Version-Numbers">Version Numbers</a></li>
+  <li><a href="#Author">Author</a></li>
+  <li><a href="#Copyright">Copyright</a></li>
+  <li><a href="#Credits">Credits</a></li>
+  <li><a href="#License">License</a></li>
 </ul>
 
-<hr name="index" />
-</div>
-<!-- INDEX END -->
-
-<p>
-</p>
-<h1><a name="backuppc_introduction">BackupPC Introduction</a></h1>
-<p>This documentation describes BackupPC version 3.2.1,
-released on 24 Apr 2011.</p>
-<p>
-</p>
-<h2><a name="overview">Overview</a></h2>
-<p>BackupPC is a high-performance, enterprise-grade system for backing up
-Unix, Linux, WinXX, and MacOSX PCs, desktops and laptops to a server's
-disk.  BackupPC is highly configurable and easy to install and maintain.</p>
-<p>Given the ever decreasing cost of disks and raid systems, it is now
-practical and cost effective to backup a large number of machines onto
-a server's local disk or network storage.  For some sites this might be
-the complete backup solution.  For other sites additional permanent
-archives could be created by periodically backing up the server to tape.</p>
+<hr />
+<h1 id="BackupPC-Introduction">BackupPC Introduction</h1>
+
+<p>This documentation describes BackupPC version 3.3.0, released on 14 Apr 2013.</p>
+
+<h2 id="Overview">Overview</h2>
+
+<p>BackupPC is a high-performance, enterprise-grade system for backing up Unix, Linux, WinXX, and MacOSX PCs, desktops and laptops to a server&#39;s disk. BackupPC is highly configurable and easy to install and maintain.</p>
+
+<p>Given the ever decreasing cost of disks and raid systems, it is now practical and cost effective to backup a large number of machines onto a server&#39;s local disk or network storage. For some sites this might be the complete backup solution. For other sites additional permanent archives could be created by periodically backing up the server to tape.</p>
+
 <p>Features include:</p>
+
 <ul>
-<li>
-<p>A clever pooling scheme minimizes disk storage and disk I/O.
-Identical files across multiple backups of the same or different PC
-are stored only once (using hard links), resulting in substantial
-savings in disk storage and disk writes.</p>
-</li>
-<li>
-<p>Optional compression provides additional reductions in storage
-(around 40%).  The CPU impact of compression is low since only
-new files (those not already in the pool) need to be compressed.</p>
-</li>
-<li>
-<p>A powerful http/cgi user interface allows administrators to view
-the current status, edit configuration, add/delete hosts, view log
-files, and allows users to initiate and cancel backups and browse
-and restore files from backups.</p>
-</li>
-<li>
-<p>The http/cgi user interface has internationalization (i18n) support,
-currently providing English, French, German, Spanish, Italian,
-Dutch, Polish, Portuguese-Brazilian and Chinese</p>
-</li>
-<li>
-<p>No client-side software is needed. On WinXX the standard smb
-protocol is used to extract backup data. On linux, unix or MacOSX
-clients, rsync, tar (over ssh/rsh/nfs) or ftp is used to extract
-backup data. Alternatively, rsync can also be used on WinXX (using
-cygwin), and Samba could be installed on the linux or unix client
-to provide smb shares).</p>
-</li>
-<li>
-<p>Flexible restore options.  Single files can be downloaded from
-any backup directly from the CGI interface.  Zip or Tar archives
-for selected files or directories from any backup can also be
-downloaded from the CGI interface.  Finally, direct restore to
-the client machine (using smb or tar) for selected files or
-directories is also supported from the CGI interface.</p>
-</li>
-<li>
-<p>BackupPC supports mobile environments where laptops are only
-intermittently connected to the network and have dynamic IP addresses
-(DHCP).  Configuration settings allow machines connected via slower WAN
-connections (eg: dial up, DSL, cable) to not be backed up, even if they
-use the same fixed or dynamic IP address as when they are connected
-directly to the LAN.</p>
-</li>
-<li>
-<p>Flexible configuration parameters allow multiple backups to be performed
-in parallel, specification of which shares to backup, which directories
-to backup or not backup, various schedules for full and incremental
-backups, schedules for email reminders to users and so on.  Configuration
-parameters can be set system-wide or also on a per-PC basis.</p>
-</li>
-<li>
-<p>Users are sent periodic email reminders if their PC has not
-recently been backed up.  Email content, timing and policies
-are configurable.</p>
-</li>
-<li>
-<p>BackupPC is Open Source software hosted by SourceForge.</p>
+
+<li><p>A clever pooling scheme minimizes disk storage and disk I/O. Identical files across multiple backups of the same or different PC are stored only once (using hard links), resulting in substantial savings in disk storage and disk writes.</p>
+
+</li>
+<li><p>Optional compression provides additional reductions in storage (around 40%). The CPU impact of compression is low since only new files (those not already in the pool) need to be compressed.</p>
+
+</li>
+<li><p>A powerful http/cgi user interface allows administrators to view the current status, edit configuration, add/delete hosts, view log files, and allows users to initiate and cancel backups and browse and restore files from backups.</p>
+
+</li>
+<li><p>The http/cgi user interface has internationalization (i18n) support, currently providing English, French, German, Spanish, Italian, Dutch, Polish, Portuguese-Brazilian and Chinese</p>
+
+</li>
+<li><p>No client-side software is needed. On WinXX the standard smb protocol is used to extract backup data. On linux, unix or MacOSX clients, rsync, tar (over ssh/rsh/nfs) or ftp is used to extract backup data. Alternatively, rsync can also be used on WinXX (using cygwin), and Samba could be installed on the linux or unix client to provide smb shares).</p>
+
+</li>
+<li><p>Flexible restore options. Single files can be downloaded from any backup directly from the CGI interface. Zip or Tar archives for selected files or directories from any backup can also be downloaded from the CGI interface. Finally, direct restore to the client machine (using smb or tar) for selected files or directories is also supported from the CGI interface.</p>
+
+</li>
+<li><p>BackupPC supports mobile environments where laptops are only intermittently connected to the network and have dynamic IP addresses (DHCP). Configuration settings allow machines connected via slower WAN connections (eg: dial up, DSL, cable) to not be backed up, even if they use the same fixed or dynamic IP address as when they are connected directly to the LAN.</p>
+
+</li>
+<li><p>Flexible configuration parameters allow multiple backups to be performed in parallel, specification of which shares to backup, which directories to backup or not backup, various schedules for full and incremental backups, schedules for email reminders to users and so on. Configuration parameters can be set system-wide or also on a per-PC basis.</p>
+
+</li>
+<li><p>Users are sent periodic email reminders if their PC has not recently been backed up. Email content, timing and policies are configurable.</p>
+
+</li>
+<li><p>BackupPC is Open Source software hosted by SourceForge.</p>
+
 </li>
 </ul>
-<p>
-</p>
-<h2><a name="backup_basics">Backup basics</a></h2>
+
+<h2 id="Backup-basics">Backup basics</h2>
+
 <dl>
-<dt><strong><a name="full_backup" class="item">Full Backup</a></strong></dt>
-
-<dd>
-<p>A full backup is a complete backup of a share. BackupPC can be
-configured to do a full backup at a regular interval (typically
-weekly).  BackupPC can be configured to keep a certain number
-of full backups.  Exponential expiry is also supported, allowing
-full backups with various vintages to be kept (for example, a
-settable number of most recent weekly fulls, plus a settable
-number of older fulls that are 2, 4, 8, or 16 weeks apart).</p>
-</dd>
-<dt><strong><a name="incremental_backup" class="item">Incremental Backup</a></strong></dt>
-
-<dd>
-<p>An incremental backup is a backup of files that have changed
-since the last successful full or incremental backup.  Starting
-in BackupPC 3.0 multi-level incrementals are supported.
-A full backup has level 0.  A new incremental of level N will
-backup all files that have changed since the most recent backup
-of a lower level.  <a href="#_conf_incrlevels_">$Conf{IncrLevels}</a> is used to specify the
-level of each successive incremental.  The default value is
-all level 1, which makes the behavior the same as earlier
-versions of BackupPC: each incremental will back up all the
-files that changed since the last full (level 0).</p>
-<p>For SMB and tar, BackupPC uses the modification time (mtime) to
-determine which files have changed since the last lower-level
-backup.  That means SMB and tar incrementals are not able to detect
-deleted files, renamed files or new files whose modification time
-is prior to the last lower-level backup.</p>
-<p>Rsync is more clever: any files whose attributes have changed (ie: uid,
-gid, mtime, modes, size) since the last full are backed up.  Deleted,
-new files and renamed files are detected by Rsync incrementals.</p>
-<p>BackupPC can also be configured to keep a certain number of incremental
-backups, and to keep a smaller number of very old incremental backups.
-If multi-level incrementals are specified then it is likely that
-more incrementals will need to be kept since lower-level incrementals
-(and the full backup) are needed to reconstruct a higher-level
-incremental.</p>
-<p>BackupPC &quot;fills-in&quot; incremental backups when browsing or restoring,
-based on the levels of each backup, giving every backup a &quot;full&quot;
-appearance.  This makes browsing and restoring backups much easier:
-you can restore from any one backup independent of whether it was
-an incremental or full.</p>
-</dd>
-<dt><strong><a name="partial_backup" class="item">Partial Backup</a></strong></dt>
-
-<dd>
-<p>When a full backup fails or is canceled, and some files have already
-been backed up, BackupPC keeps a partial backup containing just the
-files that were backed up successfully.  The partial backup is removed
-when the next successful backup completes, or if another full backup
-fails resulting in a newer partial backup.  A failed full backup
-that has not backed up any files, or any failed incremental backup,
-is removed; no partial backup is saved in these cases.</p>
-<p>The partial backup may be browsed or used to restore files just like
-a successful full or incremental backup.</p>
-<p>With the rsync transfer method the partial backup is used to resume
-the next full backup, avoiding the need to retransfer the file data
-already in the partial backup.</p>
-</dd>
-<dt><strong><a name="identical_files" class="item">Identical Files</a></strong></dt>
-
-<dd>
-<p>BackupPC pools identical files using hardlinks.  By &quot;identical
-files&quot; we mean files with identical contents, not necessary the
-same permissions, ownership or modification time.  Two files might
-have different permissions, ownership, or modification time but
-will still be pooled whenever the contents are identical.  This
-is possible since BackupPC stores the file meta-data (permissions,
-ownership, and modification time) separately from the file contents.</p>
-</dd>
-<dt><strong><a name="backup_policy" class="item">Backup Policy</a></strong></dt>
-
-<dd>
-<p>Based on your site's requirements you need to decide what your backup
-policy is.  BackupPC is not designed to provide exact re-imaging of
-failed disks.  See <a href="#limitations">Limitations</a> for more information.
-However, the addition of tar transport for linux/unix clients, plus
-full support for special file types and unix attributes in v1.4.0
-likely means an exact image of a linux/unix file system can be made.</p>
-<p>BackupPC saves backups onto disk. Because of pooling you can relatively
-economically keep several weeks of old backups.</p>
-<p>At some sites the disk-based backup will be adequate, without a
-secondary tape backup. This system is robust to any single failure: if a
-client disk fails or loses files, the BackupPC server can be used to
-restore files. If the server disk fails, BackupPC can be restarted on a
-fresh file system, and create new backups from the clients. The chance
-of the server disk failing can be made very small by spending more money
-on increasingly better RAID systems.  However, there is still the risk
-of catastrophic events like fires or earthquakes that can destroy
-both the BackupPC server and the clients it is backing up if they
-are physically nearby.</p>
-<p>Some sites might choose to do periodic backups to tape or cd/dvd.
-This backup can be done perhaps weekly using the archive function of
-BackupPC.</p>
-<p>Other users have reported success with removable disks to rotate the
-BackupPC data drives, or using rsync to mirror the BackupPC data pool
-offsite.</p>
+
+<dt id="Full-Backup">Full Backup</dt>
+<dd>
+
+<p>A full backup is a complete backup of a share. BackupPC can be configured to do a full backup at a regular interval (typically weekly). BackupPC can be configured to keep a certain number of full backups. Exponential expiry is also supported, allowing full backups with various vintages to be kept (for example, a settable number of most recent weekly fulls, plus a settable number of older fulls that are 2, 4, 8, or 16 weeks apart).</p>
+
+</dd>
+<dt id="Incremental-Backup">Incremental Backup</dt>
+<dd>
+
+<p>An incremental backup is a backup of files that have changed since the last successful full or incremental backup. Starting in BackupPC 3.0 multi-level incrementals are supported. A full backup has level 0. A new incremental of level N will backup all files that have changed since the most recent backup of a lower level. <a href="#_conf_incrlevels_">$Conf{IncrLevels}</a> is used to specify the level of each successive incremental. The default value is all level 1, which makes the behavior the same as earlier versions of BackupPC: each incremental will back up all the files that changed since the last full (level 0).</p>
+
+<p>For SMB and tar, BackupPC uses the modification time (mtime) to determine which files have changed since the last lower-level backup. That means SMB and tar incrementals are not able to detect deleted files, renamed files or new files whose modification time is prior to the last lower-level backup.</p>
+
+<p>Rsync is more clever: any files whose attributes have changed (ie: uid, gid, mtime, modes, size) since the last full are backed up. Deleted, new files and renamed files are detected by Rsync incrementals.</p>
+
+<p>BackupPC can also be configured to keep a certain number of incremental backups, and to keep a smaller number of very old incremental backups. If multi-level incrementals are specified then it is likely that more incrementals will need to be kept since lower-level incrementals (and the full backup) are needed to reconstruct a higher-level incremental.</p>
+
+<p>BackupPC &quot;fills-in&quot; incremental backups when browsing or restoring, based on the levels of each backup, giving every backup a &quot;full&quot; appearance. This makes browsing and restoring backups much easier: you can restore from any one backup independent of whether it was an incremental or full.</p>
+
+</dd>
+<dt id="Partial-Backup">Partial Backup</dt>
+<dd>
+
+<p>When a full backup fails or is canceled, and some files have already been backed up, BackupPC keeps a partial backup containing just the files that were backed up successfully. The partial backup is removed when the next successful backup completes, or if another full backup fails resulting in a newer partial backup. A failed full backup that has not backed up any files, or any failed incremental backup, is removed; no partial backup is saved in these cases.</p>
+
+<p>The partial backup may be browsed or used to restore files just like a successful full or incremental backup.</p>
+
+<p>With the rsync transfer method the partial backup is used to resume the next full backup, avoiding the need to retransfer the file data already in the partial backup.</p>
+
+</dd>
+<dt id="Identical-Files">Identical Files</dt>
+<dd>
+
+<p>BackupPC pools identical files using hardlinks. By &quot;identical files&quot; we mean files with identical contents, not necessary the same permissions, ownership or modification time. Two files might have different permissions, ownership, or modification time but will still be pooled whenever the contents are identical. This is possible since BackupPC stores the file meta-data (permissions, ownership, and modification time) separately from the file contents.</p>
+
+</dd>
+<dt id="Backup-Policy">Backup Policy</dt>
+<dd>
+
+<p>Based on your site&#39;s requirements you need to decide what your backup policy is. BackupPC is not designed to provide exact re-imaging of failed disks. See <a>Limitations</a> for more information. However, the addition of tar transport for linux/unix clients, plus full support for special file types and unix attributes in v1.4.0 likely means an exact image of a linux/unix file system can be made.</p>
+
+<p>BackupPC saves backups onto disk. Because of pooling you can relatively economically keep several weeks of old backups.</p>
+
+<p>At some sites the disk-based backup will be adequate, without a secondary tape backup. This system is robust to any single failure: if a client disk fails or loses files, the BackupPC server can be used to restore files. If the server disk fails, BackupPC can be restarted on a fresh file system, and create new backups from the clients. The chance of the server disk failing can be made very small by spending more money on increasingly better RAID systems. However, there is still the risk of catastrophic events like fires or earthquakes that can destroy both the BackupPC server and the clients it is backing up if they are physically nearby.</p>
+
+<p>Some sites might choose to do periodic backups to tape or cd/dvd. This backup can be done perhaps weekly using the archive function of BackupPC.</p>
+
+<p>Other users have reported success with removable disks to rotate the BackupPC data drives, or using rsync to mirror the BackupPC data pool offsite.</p>
+
 </dd>
 </dl>
-<p>
-</p>
-<h2><a name="resources">Resources</a></h2>
+
+<h2 id="Resources">Resources</h2>
+
 <dl>
-<dt><strong><a name="backuppc_home_page" class="item">BackupPC home page</a></strong></dt>
 
+<dt id="BackupPC-home-page">BackupPC home page</dt>
 <dd>
-<p>The BackupPC Open Source project is hosted on SourceForge.  The
-home page can be found at:</p>
-<pre>
-    <a href="http://backuppc.sourceforge.net">http://backuppc.sourceforge.net</a></pre>
-<p>This page has links to the current documentation, the SourceForge
-project page and general information.</p>
+
+<p>The BackupPC Open Source project is hosted on SourceForge. The home page can be found at:</p>
+
+<pre><code>    http://backuppc.sourceforge.net</code></pre>
+
+<p>This page has links to the current documentation, the SourceForge project page and general information.</p>
+
 </dd>
-<dt><strong><a name="sourceforge_project" class="item">SourceForge project</a></strong></dt>
+<dt id="SourceForge-project">SourceForge project</dt>
+<dd>
 
-<dd>
 <p>The SourceForge project page is at:</p>
-<pre>
-    <a href="http://sourceforge.net/projects/backuppc">http://sourceforge.net/projects/backuppc</a></pre>
+
+<pre><code>    http://sourceforge.net/projects/backuppc</code></pre>
+
 <p>This page has links to the current releases of BackupPC.</p>
-</dd>
-<dt><strong><a name="backuppc_wiki" class="item">BackupPC Wiki</a></strong></dt>
-
-<dd>
-<p>BackupPC has a Wiki at <a href="http://backuppc.wiki.sourceforge.net">http://backuppc.wiki.sourceforge.net</a>.
-Everyone is encouraged to contribute to the Wiki.  Anyone with
-a SourceForge account can edit the Wiki.</p>
-<p>The old FAQ is at <a href="http://backuppc.sourceforge.net/faq">http://backuppc.sourceforge.net/faq</a>, but
-is deprecated in favor of the Wiki.</p>
-</dd>
-<dt><strong><a name="mailing_lists" class="item">Mailing lists</a></strong></dt>
-
-<dd>
-<p>Three BackupPC mailing lists exist for announcements (backuppc-announce),
-developers (backuppc-devel), and a general user list for support, asking
-questions or any other topic relevant to BackupPC (backuppc-users).</p>
-<p>The lists are archived on SourceForge and Gmane.  The SourceForge lists
-are not always up to date and the searching is limited, so Gmane is
-a good alternative.  See:</p>
-<pre>
-    <a href="http://news.gmane.org/index.php?prefix=gmane.comp.sysutils.backup.backuppc">http://news.gmane.org/index.php?prefix=gmane.comp.sysutils.backup.backuppc</a>
-    <a href="http://sourceforge.net/mailarchive/forum.php?forum=backuppc-users">http://sourceforge.net/mailarchive/forum.php?forum=backuppc-users</a></pre>
+
+</dd>
+<dt id="BackupPC-Wiki">BackupPC Wiki</dt>
+<dd>
+
+<p>BackupPC has a Wiki at <a href="http://backuppc.wiki.sourceforge.net">http://backuppc.wiki.sourceforge.net</a>. Everyone is encouraged to contribute to the Wiki. Anyone with a SourceForge account can edit the Wiki.</p>
+
+<p>The old FAQ is at <a href="http://backuppc.sourceforge.net/faq">http://backuppc.sourceforge.net/faq</a>, but is deprecated in favor of the Wiki.</p>
+
+</dd>
+<dt id="Mailing-lists">Mailing lists</dt>
+<dd>
+
+<p>Three BackupPC mailing lists exist for announcements (backuppc-announce), developers (backuppc-devel), and a general user list for support, asking questions or any other topic relevant to BackupPC (backuppc-users).</p>
+
+<p>The lists are archived on SourceForge and Gmane. The SourceForge lists are not always up to date and the searching is limited, so Gmane is a good alternative. See:</p>
+
+<pre><code>    http://news.gmane.org/index.php?prefix=gmane.comp.sysutils.backup.backuppc
+    http://sourceforge.net/mailarchive/forum.php?forum=backuppc-users</code></pre>
+
 <p>You can subscribe to these lists by visiting:</p>
-<pre>
-    <a href="http://lists.sourceforge.net/lists/listinfo/backuppc-announce">http://lists.sourceforge.net/lists/listinfo/backuppc-announce</a>
-    <a href="http://lists.sourceforge.net/lists/listinfo/backuppc-users">http://lists.sourceforge.net/lists/listinfo/backuppc-users</a>
-    <a href="http://lists.sourceforge.net/lists/listinfo/backuppc-devel">http://lists.sourceforge.net/lists/listinfo/backuppc-devel</a></pre>
-<p>The backuppc-announce list is moderated and is used only for
-important announcements (eg: new versions).  It is low traffic.
-You only need to subscribe to one of backuppc-announce and
-backuppc-users: backuppc-users also receives any messages on
-backuppc-announce.</p>
-<p>The backuppc-devel list is only for developers who are working on BackupPC.
-Do not post questions or support requests there.  But detailed technical
-discussions should happen on this list.</p>
+
+<pre><code>    http://lists.sourceforge.net/lists/listinfo/backuppc-announce
+    http://lists.sourceforge.net/lists/listinfo/backuppc-users
+    http://lists.sourceforge.net/lists/listinfo/backuppc-devel</code></pre>
+
+<p>The backuppc-announce list is moderated and is used only for important announcements (eg: new versions). It is low traffic. You only need to subscribe to one of backuppc-announce and backuppc-users: backuppc-users also receives any messages on backuppc-announce.</p>
+
+<p>The backuppc-devel list is only for developers who are working on BackupPC. Do not post questions or support requests there. But detailed technical discussions should happen on this list.</p>
+
 <p>To post a message to the backuppc-users list, send an email to</p>
-<pre>
-    [e-mail]</pre>
+
+<pre><code>    [e-mail]</code></pre>
+
 <p>Do not send subscription requests to this address!</p>
+
 </dd>
-<dt><strong><a name="other_programs_of_interest" class="item">Other Programs of Interest</a></strong></dt>
-
+<dt id="Other-Programs-of-Interest">Other Programs of Interest</dt>
 <dd>
-<p>If you want to mirror linux or unix files or directories to a remote server
-you should use rsync, <a href="http://rsync.samba.org">http://rsync.samba.org</a>.  BackupPC uses
-rsync as a transport mechanism; if you are already an rsync user you
-can think of BackupPC as adding efficient storage (compression and
-pooling) and a convenient user interface to rsync.</p>
-<p>Two popular open source packages that do tape backup are
-Amanda (<a href="http://www.amanda.org">http://www.amanda.org</a>)
-and Bacula (<a href="http://www.bacula.org">http://www.bacula.org</a>).
-These packages can be used as complete solutions, or also as back
-ends to BackupPC to backup the BackupPC server data to tape.</p>
-<p>Various programs and scripts use rsync to provide hardlinked backups.
-See, for example, Mike Rubel's site (<a href="http://www.mikerubel.org/computers/rsync_snapshots">http://www.mikerubel.org/computers/rsync_snapshots</a>),
-JW Schultz's dirvish (<a href="http://www.dirvish.org/">http://www.dirvish.org/</a>),
-Ben Escoto's rdiff-backup (<a href="http://www.nongnu.org/rdiff-backup">http://www.nongnu.org/rdiff-backup</a>),
-and John Bowman's rlbackup (<a href="http://www.math.ualberta.ca/imaging/rlbackup">http://www.math.ualberta.ca/imaging/rlbackup</a>).</p>
-<p>Unison is a utility that can do two-way, interactive, synchronization.
-See <a href="http://freshmeat.net/projects/unison">http://freshmeat.net/projects/unison</a>.  An external wrapper around
-rsync that maintains transfer data to enable two-way synchronization is
-drsync; see <a href="http://freshmeat.net/projects/drsync">http://freshmeat.net/projects/drsync</a>.</p>
-<p>BackupPC provides many additional features, such as compressed storage,
-hardlinking any matching files (rather than just files with the same name),
-and storing special files without root privileges.  But these other programs
-provide simple, effective and fast solutions and are definitely worthy of
-consideration.</p>
+
+<p>If you want to mirror linux or unix files or directories to a remote server you should use rsync, <a href="http://rsync.samba.org">http://rsync.samba.org</a>. BackupPC uses rsync as a transport mechanism; if you are already an rsync user you can think of BackupPC as adding efficient storage (compression and pooling) and a convenient user interface to rsync.</p>
+
+<p>Two popular open source packages that do tape backup are Amanda (<a href="http://www.amanda.org">http://www.amanda.org</a>) and Bacula (<a href="http://www.bacula.org">http://www.bacula.org</a>). These packages can be used as complete solutions, or also as back ends to BackupPC to backup the BackupPC server data to tape.</p>
+
+<p>Various programs and scripts use rsync to provide hardlinked backups. See, for example, Mike Rubel&#39;s site (<a href="http://www.mikerubel.org/computers/rsync_snapshots">http://www.mikerubel.org/computers/rsync_snapshots</a>), JW Schultz&#39;s dirvish (<a href="http://www.dirvish.org/">http://www.dirvish.org/</a>), Ben Escoto&#39;s rdiff-backup (<a href="http://www.nongnu.org/rdiff-backup">http://www.nongnu.org/rdiff-backup</a>), and John Bowman&#39;s rlbackup (<a href="http://www.math.ualberta.ca/imaging/rlbackup">http://www.math.ualberta.ca/imaging/rlbackup</a>).</p>
+
+<p>Unison is a utility that can do two-way, interactive, synchronization. See <a href="http://freshmeat.net/projects/unison">http://freshmeat.net/projects/unison</a>. An external wrapper around rsync that maintains transfer data to enable two-way synchronization is drsync; see <a href="http://freshmeat.net/projects/drsync">http://freshmeat.net/projects/drsync</a>.</p>
+
+<p>BackupPC provides many additional features, such as compressed storage, hardlinking any matching files (rather than just files with the same name), and storing special files without root privileges. But these other programs provide simple, effective and fast solutions and are definitely worthy of consideration.</p>
+
 </dd>
 </dl>
-<p>
-</p>
-<h2><a name="road_map">Road map</a></h2>
-<p>The new features planned for future releases of BackupPC
-are on the Wiki at <a href="http://backuppc.wiki.sourceforge.net">http://backuppc.wiki.sourceforge.net</a>.</p>
+
+<h2 id="Road-map">Road map</h2>
+
+<p>The new features planned for future releases of BackupPC are on the Wiki at <a href="http://backuppc.wiki.sourceforge.net">http://backuppc.wiki.sourceforge.net</a>.</p>
+
 <p>Comments and suggestions are welcome.</p>
-<p>
-</p>
-<h2><a name="you_can_help">You can help</a></h2>
-<p>BackupPC is free. I work on BackupPC because I enjoy doing it and I like
-to contribute to the open source community.</p>
-<p>BackupPC already has more than enough features for my own needs.  The
-main compensation for continuing to work on BackupPC is knowing that
-more and more people find it useful.  So feedback is certainly
-appreciated, both positive and negative.</p>
-<p>Beyond being a satisfied user and telling other people about it, everyone
-is encouraged to add links to <a href="http://backuppc.sourceforge.net">http://backuppc.sourceforge.net</a>
-(I'll see them via Google) or otherwise publicize BackupPC.  Unlike
-the commercial products in this space, I have a zero budget (in both
-time and money) for marketing, PR and advertising, so it's up to
-all of you!  Feel free to vote for BackupPC at
-<a href="http://freshmeat.net/projects/backuppc">http://freshmeat.net/projects/backuppc</a>.</p>
-<p>Also, everyone is encouraged to contribute patches, bug reports,
-feature and design suggestions, new code, Wiki additions (you can
-do those directly) and documentation corrections or improvements.
-Answering questions on the mailing list is a big help too.</p>
-<p>
-<a href="#__index__"><small>Back to Top</small></a>
-</p>
+
+<h2 id="You-can-help">You can help</h2>
+
+<p>BackupPC is free. I work on BackupPC because I enjoy doing it and I like to contribute to the open source community.</p>
+
+<p>BackupPC already has more than enough features for my own needs. The main compensation for continuing to work on BackupPC is knowing that more and more people find it useful. So feedback is certainly appreciated, both positive and negative.</p>
+
+<p>Beyond being a satisfied user and telling other people about it, everyone is encouraged to add links to <a href="http://backuppc.sourceforge.net">http://backuppc.sourceforge.net</a> (I&#39;ll see them via Google) or otherwise publicize BackupPC. Unlike the commercial products in this space, I have a zero budget (in both time and money) for marketing, PR and advertising, so it&#39;s up to all of you! Feel free to vote for BackupPC at <a href="http://freshmeat.net/projects/backuppc">http://freshmeat.net/projects/backuppc</a>.</p>
+
+<p>Also, everyone is encouraged to contribute patches, bug reports, feature and design suggestions, new code, Wiki additions (you can do those directly) and documentation corrections or improvements. Answering questions on the mailing list is a big help too.</p>
+
 <hr />
-<h1><a name="installing_backuppc">Installing BackupPC</a></h1>
-<p>
-</p>
-<h2><a name="requirements">Requirements</a></h2>
+<h1 id="Installing-BackupPC">Installing BackupPC</h1>
+
+<h2 id="Requirements">Requirements</h2>
+
 <p>BackupPC requires:</p>
+
 <ul>
-<li>
-<p>A linux, solaris, or unix based server with a substantial amount of free
-disk space (see the next section for what that means). The CPU and disk
-performance on this server will determine how many simultaneous backups
-you can run. You should be able to run 4-8 simultaneous backups on a
-moderately configured server.</p>
-<p>Several users have reported significantly better performance using
-reiserfs compared to ext3 for the BackupPC data file system.  It is
-also recommended you consider either an LVM or RAID setup (either
-in HW or SW; eg: 3Ware RAID10 or RAID5) so that you can expand the
-file system as necessary.</p>
-<p>When BackupPC starts with an empty pool, all the backup data will be
-written to the pool on disk. After more backups are done, a higher
-percentage of incoming files will already be in the pool. BackupPC is
-able to avoid writing to disk new files that are already in the pool.
-So over time disk writes will reduce significantly (by perhaps a factor
-of 20 or more), since eventually 95% or more of incoming backup files
-are typically in the pool. Disk reads from the pool are still needed to
-do file compares to verify files are an exact match. So, with a mature
-pool, if a relatively fast client generates data at say 1MB/sec, and you
-run 4 simultaneous backups, there will be an average server disk load of
-about 4MB/sec reads and 0.2MB/sec writes (assuming 95% of the incoming
-files are in the pool). These rates will be perhaps 40% lower if
-compression is on.</p>
-</li>
-<li>
-<p>Perl version 5.8.0 or later.  If you don't have perl, please
-see <a href="http://www.cpan.org">http://www.cpan.org</a>.</p>
-</li>
-<li>
-<p>Perl modules Compress::Zlib, Archive::Zip and File::RsyncP.  Try &quot;perldoc
-Compress::Zlib&quot; and &quot;perldoc Archive::Zip&quot; to see if you have these
-modules.  If not, fetch them from <a href="http://www.cpan.org">http://www.cpan.org</a> and see the
-instructions below for how to build and install them.</p>
-<p>The File::RsyncP module is available from <a href="http://perlrsync.sourceforge.net">http://perlrsync.sourceforge.net</a>
-or CPAN.  You'll need to install the File::RsyncP module if you want to use
-Rsync as a transport method.</p>
-</li>
-<li>
-<p>If you are using smb to backup WinXX machines you need smbclient and
-nmblookup from the samba package.  You will also need nmblookup if
-you are backing up linux/unix DHCP machines.  See <a href="http://www.samba.org">http://www.samba.org</a>.
-Samba versions 3.x are stable and now recommended instead of 2.x.</p>
-<p>See <a href="http://www.samba.org">http://www.samba.org</a> for source and binaries.  It's pretty easy to
-fetch and compile samba, and just grab smbclient and nmblookup, without
-doing the installation. Alternatively, <a href="http://www.samba.org">http://www.samba.org</a> has binary
-distributions for most platforms.</p>
-</li>
-<li>
-<p>If you are using tar to backup linux/unix machines, those machines should have
-version 1.13.7 at a minimum, with version 1.13.20 or higher recommended.  Use
-&quot;tar --version&quot; to check your version.  Various GNU mirrors have the newest
-versions of tar; see <a href="http://www.gnu.org/software/tar/">http://www.gnu.org/software/tar/</a>.</p>
-</li>
-<li>
-<p>If you are using rsync to backup linux/unix machines you should have
-version 2.6.3 or higher on each client machine.  See
-<a href="http://rsync.samba.org">http://rsync.samba.org</a>. Use &quot;rsync --version&quot; to check your version.</p>
-<p>For BackupPC to use Rsync you will also need to install the perl
-File::RsyncP module, which is available from
-<a href="http://perlrsync.sourceforge.net">http://perlrsync.sourceforge.net</a>.
-Version 0.68 or later is required.</p>
-</li>
-<li>
-<p>The Apache web server, see <a href="http://www.apache.org">http://www.apache.org</a>, preferably built
-with mod_perl support.</p>
+
+<li><p>A linux, solaris, or unix based server with a substantial amount of free disk space (see the next section for what that means). The CPU and disk performance on this server will determine how many simultaneous backups you can run. You should be able to run 4-8 simultaneous backups on a moderately configured server.</p>
+
+<p>Several users have reported significantly better performance using reiserfs compared to ext3 for the BackupPC data file system. It is also recommended you consider either an LVM or RAID setup (either in HW or SW; eg: 3Ware RAID10 or RAID5) so that you can expand the file system as necessary.</p>
+
+<p>When BackupPC starts with an empty pool, all the backup data will be written to the pool on disk. After more backups are done, a higher percentage of incoming files will already be in the pool. BackupPC is able to avoid writing to disk new files that are already in the pool. So over time disk writes will reduce significantly (by perhaps a factor of 20 or more), since eventually 95% or more of incoming backup files are typically in the pool. Disk reads from the pool are still needed to do file compares to verify files are an exact match. So, with a mature pool, if a relatively fast client generates data at say 1MB/sec, and you run 4 simultaneous backups, there will be an average server disk load of about 4MB/sec reads and 0.2MB/sec writes (assuming 95% of the incoming files are in the pool). These rates will be perhaps 40% lower if compression is on.</p>
+
+</li>
+<li><p>Perl version 5.8.0 or later. If you don&#39;t have perl, please see <a href="http://www.cpan.org">http://www.cpan.org</a>.</p>
+
+</li>
+<li><p>Perl modules Compress::Zlib, Archive::Zip and File::RsyncP. Try &quot;perldoc Compress::Zlib&quot; and &quot;perldoc Archive::Zip&quot; to see if you have these modules. If not, fetch them from <a href="http://www.cpan.org">http://www.cpan.org</a> and see the instructions below for how to build and install them.</p>
+
+<p>The File::RsyncP module is available from <a href="http://perlrsync.sourceforge.net">http://perlrsync.sourceforge.net</a> or CPAN. You&#39;ll need to install the File::RsyncP module if you want to use Rsync as a transport method.</p>
+
+</li>
+<li><p>If you are using smb to backup WinXX machines you need smbclient and nmblookup from the samba package. You will also need nmblookup if you are backing up linux/unix DHCP machines. See <a href="http://www.samba.org">http://www.samba.org</a>. Samba versions 3.x are stable and now recommended instead of 2.x.</p>
+
+<p>See <a href="http://www.samba.org">http://www.samba.org</a> for source and binaries. It&#39;s pretty easy to fetch and compile samba, and just grab smbclient and nmblookup, without doing the installation. Alternatively, <a href="http://www.samba.org">http://www.samba.org</a> has binary distributions for most platforms.</p>
+
+</li>
+<li><p>If you are using tar to backup linux/unix machines, those machines should have version 1.13.7 at a minimum, with version 1.13.20 or higher recommended. Use &quot;tar --version&quot; to check your version. Various GNU mirrors have the newest versions of tar; see <a href="http://www.gnu.org/software/tar/">http://www.gnu.org/software/tar/</a>.</p>
+
+</li>
+<li><p>If you are using rsync to backup linux/unix machines you should have version 2.6.3 or higher on each client machine. See <a href="http://rsync.samba.org">http://rsync.samba.org</a>. Use &quot;rsync --version&quot; to check your version.</p>
+
+<p>For BackupPC to use Rsync you will also need to install the perl File::RsyncP module, which is available from <a href="http://perlrsync.sourceforge.net">http://perlrsync.sourceforge.net</a>. Version 0.68 or later is required.</p>
+
+</li>
+<li><p>The Apache web server, see <a href="http://www.apache.org">http://www.apache.org</a>, preferably built with mod_perl support.</p>
+
 </li>
 </ul>
-<p>
-</p>
-<h2><a name="what_type_of_storage_space_do_i_need">What type of storage space do I need?</a></h2>
-<p>BackupPC uses hardlinks to pool files common to different backups.
-Therefore BackupPC's data store (__TOPDIR__) must point to a single
-file system that supports hardlinks.  You cannot split this file
-system with multiple mount points or using symbolic links to point a
-sub-directory to a different file system (it is ok to use a single
-symbolic link at the top-level directory (__TOPDIR__) to point the
-entire data store somewhere else).  You can of course use any kind of
-RAID system or logical volume manager that combines the capacity of
-multiple disks into a single, larger, file system. Such approaches
-have the advantage that the file system can be expanded without having
-to copy it.</p>
-<p>Any standard linux or unix file system supports hardlinks.  NFS mounted
-file systems work too (provided the underlying file system supports
-hardlinks).  But windows based FAT and NTFS file systems will not work.</p>
-<p>Starting with BackupPC 3.1.0, run-time checks are done at startup and
-at the start of each backup to ensure that the file system can support
-hardlinks, since this is a common area of configuration problems.</p>
-<p>
-</p>
-<h2><a name="how_much_disk_space_do_i_need">How much disk space do I need?</a></h2>
-<p>Here's one real example for an environment that is backing up 65 laptops
-with compression off. Each full backup averages 3.2GB. Each incremental
-backup averages about 0.2GB. Storing one full backup and two incremental
-backups per laptop is around 240GB of raw data. But because of the
-pooling of identical files, only 87GB is used.  This is without
-compression.</p>
-<p>Another example, with compression on: backing up 95 laptops, where
-each backup averages 3.6GB and each incremental averages about 0.3GB.
-Keeping three weekly full backups, and six incrementals is around
-1200GB of raw data.  Because of pooling and compression, only 150GB
-is needed.</p>
-<p>Here's a rule of thumb. Add up the disk usage of all the machines you
-want to backup (210GB in the first example above). This is a rough
-minimum space estimate that should allow a couple of full backups and at
-least half a dozen incremental backups per machine. If compression is on
-you can reduce the storage requirements by maybe 30-40%.  Add some margin
-in case you add more machines or decide to keep more old backups.</p>
-<p>Your actual mileage will depend upon the types of clients, operating
-systems and applications you have. The more uniform the clients and
-applications the bigger the benefit from pooling common files.</p>
-<p>For example, the Eudora email tool stores each mail folder in a separate
-file, and attachments are extracted as separate files. So in the sadly
-common case of a large attachment emailed to many recipients, Eudora
-will extract the attachment into a new file. When these machines are
-backed up, only one copy of the file will be stored on the server, even
-though the file appears in many different full or incremental backups. In
-this sense Eudora is a &quot;friendly&quot; application from the point of view of
-backup storage requirements.</p>
-<p>An example at the other end of the spectrum is Outlook. Everything
-(email bodies, attachments, calendar, contact lists) is stored in a
-single file, which often becomes huge. Any change to this file requires
-a separate copy of the file to be saved during backup. Outlook is even
-more troublesome, since it keeps this file locked all the time, so it
-cannot be read by smbclient whenever Outlook is running.  See the
-<a href="#limitations">Limitations</a> section for more discussion of this problem.</p>
-<p>In addition to total disk space, you should make sure you have
-plenty of inodes on your BackupPC data partition. Some users have
-reported running out of inodes on their BackupPC data partition.
-So even if you have plenty of disk space, BackupPC will report
-failures when the inodes are exhausted.  This is a particular
-problem with ext2/ext3 file systems that have a fixed number of
-inodes when the file system is built.  Use &quot;df -i&quot; to see your
-inode usage.</p>
-<p>
-</p>
-<h2><a name="step_1__getting_backuppc">Step 1: Getting BackupPC</a></h2>
-<p>Some linux distributions now include BackupPC.  The Debian
-distribution, supported by Ludovic Drolez, can be found at
-<a href="http://packages.debian.org/backuppc">http://packages.debian.org/backuppc</a> and is included
-in the current stable Debian release.  On Debian, BackupPC can
-be installed with the command:</p>
-<pre>
-    apt-get install backuppc</pre>
-<p>In the future there might be packages for Gentoo and other
-linux flavors.  If the packaged version is older than the
-released version then you may want to install the
-latest version as described below.</p>
-<p>Otherwise, manually fetching and installing BackupPC is easy.
-Start by downloading the latest version from
-<a href="http://backuppc.sourceforge.net">http://backuppc.sourceforge.net</a>.  Hit the &quot;Code&quot; button,
-then select the &quot;backuppc&quot; or &quot;backuppc-beta&quot; package and
-download the latest version.</p>
-<p>
-</p>
-<h2><a name="step_2__installing_the_distribution">Step 2: Installing the distribution</a></h2>
-<p>Note: most information in this step is only relevant if you build
-and install BackupPC yourself.  If you use a package provided by a
-distribution, the package management system should take of installing
-any needed dependencies.</p>
-<p>First off, there are five perl modules you should install.
-These are all optional, but highly recommended:</p>
+
+<h2 id="What-type-of-storage-space-do-I-need-">What type of storage space do I need?</h2>
+
+<p>BackupPC uses hardlinks to pool files common to different backups. Therefore BackupPC&#39;s data store (__TOPDIR__) must point to a single file system that supports hardlinks. You cannot split this file system with multiple mount points or using symbolic links to point a sub-directory to a different file system (it is ok to use a single symbolic link at the top-level directory (__TOPDIR__) to point the entire data store somewhere else). You can of course use any kind of RAID system or logical volume manager that combines the capacity of multiple disks into a single, larger, file system. Such approaches have the advantage that the file system can be expanded without having to copy it.</p>
+
+<p>Any standard linux or unix file system supports hardlinks. NFS mounted file systems work too (provided the underlying file system supports hardlinks). But windows based FAT and NTFS file systems will not work.</p>
+
+<p>Starting with BackupPC 3.1.0, run-time checks are done at startup and at the start of each backup to ensure that the file system can support hardlinks, since this is a common area of configuration problems.</p>
+
+<h2 id="How-much-disk-space-do-I-need-">How much disk space do I need?</h2>
+
+<p>Here&#39;s one real example for an environment that is backing up 65 laptops with compression off. Each full backup averages 3.2GB. Each incremental backup averages about 0.2GB. Storing one full backup and two incremental backups per laptop is around 240GB of raw data. But because of the pooling of identical files, only 87GB is used. This is without compression.</p>
+
+<p>Another example, with compression on: backing up 95 laptops, where each backup averages 3.6GB and each incremental averages about 0.3GB. Keeping three weekly full backups, and six incrementals is around 1200GB of raw data. Because of pooling and compression, only 150GB is needed.</p>
+
+<p>Here&#39;s a rule of thumb. Add up the disk usage of all the machines you want to backup (210GB in the first example above). This is a rough minimum space estimate that should allow a couple of full backups and at least half a dozen incremental backups per machine. If compression is on you can reduce the storage requirements by maybe 30-40%. Add some margin in case you add more machines or decide to keep more old backups.</p>
+
+<p>Your actual mileage will depend upon the types of clients, operating systems and applications you have. The more uniform the clients and applications the bigger the benefit from pooling common files.</p>
+
+<p>For example, the Eudora email tool stores each mail folder in a separate file, and attachments are extracted as separate files. So in the sadly common case of a large attachment emailed to many recipients, Eudora will extract the attachment into a new file. When these machines are backed up, only one copy of the file will be stored on the server, even though the file appears in many different full or incremental backups. In this sense Eudora is a &quot;friendly&quot; application from the point of view of backup storage requirements.</p>
+
+<p>An example at the other end of the spectrum is Outlook. Everything (email bodies, attachments, calendar, contact lists) is stored in a single file, which often becomes huge. Any change to this file requires a separate copy of the file to be saved during backup. Outlook is even more troublesome, since it keeps this file locked all the time, so it cannot be read by smbclient whenever Outlook is running. See the <a>Limitations</a> section for more discussion of this problem.</p>
+
+<p>In addition to total disk space, you should make sure you have plenty of inodes on your BackupPC data partition. Some users have reported running out of inodes on their BackupPC data partition. So even if you have plenty of disk space, BackupPC will report failures when the inodes are exhausted. This is a particular problem with ext2/ext3 file systems that have a fixed number of inodes when the file system is built. Use &quot;df -i&quot; to see your inode usage.</p>
+
+<h2 id="Step-1:-Getting-BackupPC">Step 1: Getting BackupPC</h2>
+
+<p>Some linux distributions now include BackupPC. The Debian distribution, supported by Ludovic Drolez, can be found at <a href="http://packages.debian.org/backuppc">http://packages.debian.org/backuppc</a> and is included in the current stable Debian release. On Debian, BackupPC can be installed with the command:</p>
+
+<pre><code>    apt-get install backuppc</code></pre>
+
+<p>In the future there might be packages for Gentoo and other linux flavors. If the packaged version is older than the released version then you may want to install the latest version as described below.</p>
+
+<p>Otherwise, manually fetching and installing BackupPC is easy. Start by downloading the latest version from <a href="http://backuppc.sourceforge.net">http://backuppc.sourceforge.net</a>. Hit the &quot;Code&quot; button, then select the &quot;backuppc&quot; or &quot;backuppc-beta&quot; package and download the latest version.</p>
+
+<h2 id="Step-2:-Installing-the-distribution">Step 2: Installing the distribution</h2>
+
+<p>Note: most information in this step is only relevant if you build and install BackupPC yourself. If you use a package provided by a distribution, the package management system should take of installing any needed dependencies.</p>
+
+<p>First off, there are five perl modules you should install. These are all optional, but highly recommended:</p>
+
 <dl>
-<dt><strong><a name="compress_zlib" class="item">Compress::Zlib</a></strong></dt>
-
-<dd>
-<p>To enable compression, you will need to install Compress::Zlib
-from <a href="http://www.cpan.org">http://www.cpan.org</a>.
-You can run &quot;perldoc Compress::Zlib&quot; to see if this module is installed.</p>
-</dd>
-<dt><strong><a name="archive_zip" class="item">Archive::Zip</a></strong></dt>
-
-<dd>
-<p>To support restore via Zip archives you will need to install
-Archive::Zip, also from <a href="http://www.cpan.org">http://www.cpan.org</a>.
-You can run &quot;perldoc Archive::Zip&quot; to see if this module is installed.</p>
-</dd>
-<dt><strong><a name="xml_rss" class="item">XML::RSS</a></strong></dt>
-
-<dd>
-<p>To support the RSS feature you will need to install XML::RSS, also from
-<a href="http://www.cpan.org">http://www.cpan.org</a>.  There is not need to install this module if you
-don't plan on using RSS. You can run &quot;perldoc XML::RSS&quot; to see if this
-module is installed.</p>
-</dd>
-<dt><strong><a name="file_rsyncp" class="item">File::RsyncP</a></strong></dt>
-
-<dd>
-<p>To use rsync and rsyncd with BackupPC you will need to install File::RsyncP.
-You can run &quot;perldoc File::RsyncP&quot; to see if this module is installed.
-File::RsyncP is available from <a href="http://perlrsync.sourceforge.net">http://perlrsync.sourceforge.net</a>.
-Version 0.68 or later is required.</p>
-</dd>
-<dt><strong><a name="file_listing_net_ftp_net_ftp_retrhandle_net_ftp_autoreconnect" class="item">File::Listing, Net::FTP, Net::FTP::RetrHandle, Net::FTP::AutoReconnect</a></strong></dt>
-
-<dd>
-<p>To use ftp with BackupPC you will need four libraries, but actually
-need to install only File::Listing from <a href="http://www.cpan.org">http://www.cpan.org</a>.
-You can run &quot;perldoc File::Listing&quot; to see if this module is installed.
-Net::FTP is a standard module. Net::FTP::RetrHandle and
-Net::FTP::AutoReconnect included in BackupPC distribution.</p>
+
+<dt id="Compress::Zlib">Compress::Zlib</dt>
+<dd>
+
+<p>To enable compression, you will need to install Compress::Zlib from <a href="http://www.cpan.org">http://www.cpan.org</a>. You can run &quot;perldoc Compress::Zlib&quot; to see if this module is installed.</p>
+
+</dd>
+<dt id="Archive::Zip">Archive::Zip</dt>
+<dd>
+
+<p>To support restore via Zip archives you will need to install Archive::Zip, also from <a href="http://www.cpan.org">http://www.cpan.org</a>. You can run &quot;perldoc Archive::Zip&quot; to see if this module is installed.</p>
+
+</dd>
+<dt id="XML::RSS">XML::RSS</dt>
+<dd>
+
+<p>To support the RSS feature you will need to install XML::RSS, also from <a href="http://www.cpan.org">http://www.cpan.org</a>. There is not need to install this module if you don&#39;t plan on using RSS. You can run &quot;perldoc XML::RSS&quot; to see if this module is installed.</p>
+
+</dd>
+<dt id="File::RsyncP">File::RsyncP</dt>
+<dd>
+
+<p>To use rsync and rsyncd with BackupPC you will need to install File::RsyncP. You can run &quot;perldoc File::RsyncP&quot; to see if this module is installed. File::RsyncP is available from <a href="http://perlrsync.sourceforge.net">http://perlrsync.sourceforge.net</a>. Version 0.68 or later is required.</p>
+
+</dd>
+<dt id="File::Listing-Net::FTP-Net::FTP::RetrHandle-Net::FTP::AutoReconnect">File::Listing, Net::FTP, Net::FTP::RetrHandle, Net::FTP::AutoReconnect</dt>
+<dd>
+
+<p>To use ftp with BackupPC you will need four libraries, but actually need to install only File::Listing from <a href="http://www.cpan.org">http://www.cpan.org</a>. You can run &quot;perldoc File::Listing&quot; to see if this module is installed. Net::FTP is a standard module. Net::FTP::RetrHandle and Net::FTP::AutoReconnect included in BackupPC distribution.</p>
+
 </dd>
 </dl>
-<p>To build and install these packages you should use the cpan program.
-Alternatively, you can fetch the tar.gz file from <a href="http://www.cpan.org">http://www.cpan.org</a>
-and then run these commands:</p>
-<pre>
-    tar zxvf Archive-Zip-1.26.tar.gz
+
+<p>To build and install these packages you should use the cpan program. Alternatively, you can fetch the tar.gz file from <a href="http://www.cpan.org">http://www.cpan.org</a> and then run these commands:</p>
+
+<pre><code>    tar zxvf Archive-Zip-1.26.tar.gz
     cd Archive-Zip-1.26
     perl Makefile.PL
     make
     make test
-    make install</pre>
+    make install</code></pre>
+
 <p>The same sequence of commands can be used for each module.</p>
-<p>Now let's move onto BackupPC itself.  After fetching
-BackupPC-3.2.1.tar.gz, run these commands as root:</p>
-<pre>
-    tar zxf BackupPC-3.2.1.tar.gz
-    cd BackupPC-3.2.1
-    perl configure.pl</pre>
-<p>In the future this release might also have patches available on the
-SourceForge site.  These patch files are text files, with a name of
-the form</p>
-<pre>
-    BackupPC-3.2.1plN.diff</pre>
-<p>where N is the patch level, eg: pl2 is patch-level 2.  These
-patch files are cumulative: you only need apply the last patch
-file, not all the earlier patch files.  If a patch file is
-available, eg: BackupPC-3.2.1pl2.diff, you should apply
-the patch after extracting the tar file:</p>
-<pre>
-     # fetch BackupPC-3.2.1.tar.gz
-     # fetch BackupPC-3.2.1pl2.diff
-     tar zxf BackupPC-3.2.1.tar.gz
-     cd BackupPC-3.2.1
-     patch -p0 &lt; ../BackupPC-3.2.1pl2.diff
-     perl configure.pl</pre>
-<p>A patch file includes comments that describe that bug fixes
-and changes.  Feel free to review it before you apply the patch.</p>
-<p>The configure.pl script also accepts command-line options if you
-wish to run it in a non-interactive manner.  It has self-contained
-documentation for all the command-line options, which you can
-read with perldoc:</p>
-<pre>
-    perldoc configure.pl</pre>
-<p>Starting with BackupPC 3.0.0, the configure.pl script by default
-complies with the file system hierarchy (FHS) conventions.  The
-major difference compared to earlier versions is that by default
-configuration files will be stored in /etc/BackupPC
-rather than below the data directory, __TOPDIR__/conf,
-and the log files will be stored in /var/log/BackupPC
-rather than below the data directory, __TOPDIR__/log.</p>
-<p>Note that distributions may choose to use different locations for
-BackupPC files than these defaults.</p>
-<p>If you are upgrading from an earlier version the configure.pl script
-will keep the configuration files and log files in their original
-location.</p>
-<p>When you run configure.pl you will be prompted for the full paths
-of various executables, and you will be prompted for the following
-information.</p>
+
+<p>Now let&#39;s move onto BackupPC itself. After fetching BackupPC-3.3.0.tar.gz, run these commands as root:</p>
+
+<pre><code>    tar zxf BackupPC-3.3.0.tar.gz
+    cd BackupPC-3.3.0
+    perl configure.pl</code></pre>
+
+<p>In the future this release might also have patches available on the SourceForge site. These patch files are text files, with a name of the form</p>
+
+<pre><code>    BackupPC-3.3.0plN.diff</code></pre>
+
+<p>where N is the patch level, eg: pl2 is patch-level 2. These patch files are cumulative: you only need apply the last patch file, not all the earlier patch files. If a patch file is available, eg: BackupPC-3.3.0pl2.diff, you should apply the patch after extracting the tar file:</p>
+
+<pre><code>     # fetch BackupPC-3.3.0.tar.gz
+     # fetch BackupPC-3.3.0pl2.diff
+     tar zxf BackupPC-3.3.0.tar.gz
+     cd BackupPC-3.3.0
+     patch -p0 &lt; ../BackupPC-3.3.0pl2.diff
+     perl configure.pl</code></pre>
+
+<p>A patch file includes comments that describe that bug fixes and changes. Feel free to review it before you apply the patch.</p>
+
+<p>The configure.pl script also accepts command-line options if you wish to run it in a non-interactive manner. It has self-contained documentation for all the command-line options, which you can read with perldoc:</p>
+
+<pre><code>    perldoc configure.pl</code></pre>
+
+<p>Starting with BackupPC 3.0.0, the configure.pl script by default complies with the file system hierarchy (FHS) conventions. The major difference compared to earlier versions is that by default configuration files will be stored in /etc/BackupPC rather than below the data directory, __TOPDIR__/conf, and the log files will be stored in /var/log/BackupPC rather than below the data directory, __TOPDIR__/log.</p>
+
+<p>Note that distributions may choose to use different locations for BackupPC files than these defaults.</p>
+
+<p>If you are upgrading from an earlier version the configure.pl script will keep the configuration files and log files in their original location.</p>
+
+<p>When you run configure.pl you will be prompted for the full paths of various executables, and you will be prompted for the following information.</p>
+
 <dl>
-<dt><strong><a name="backuppc_user" class="item">BackupPC User</a></strong></dt>
 
+<dt id="BackupPC-User">BackupPC User</dt>
 <dd>
-<p>It is best if BackupPC runs as a special user, eg backuppc, that has
-limited privileges. It is preferred that backuppc belongs to a system
-administrator group so that sys admin members can browse BackupPC files,
-edit the configuration files and so on. Although configurable, the
-default settings leave group read permission on pool files, so make
-sure the BackupPC user's group is chosen restrictively.</p>
+
+<p>It is best if BackupPC runs as a special user, eg backuppc, that has limited privileges. It is preferred that backuppc belongs to a system administrator group so that sys admin members can browse BackupPC files, edit the configuration files and so on. Although configurable, the default settings leave group read permission on pool files, so make sure the BackupPC user&#39;s group is chosen restrictively.</p>
+
 <p>On this installation, this is __BACKUPPCUSER__.</p>
-<p>For security purposes you might choose to configure the BackupPC
-user with the shell set to /bin/false.  Since you might need to
-run some BackupPC programs as the BackupPC user for testing
-purposes, you can use the -s option to su to explicitly run
-a shell, eg:</p>
-<pre>
-    su -s /bin/bash __BACKUPPCUSER__</pre>
+
+<p>For security purposes you might choose to configure the BackupPC user with the shell set to /bin/false. Since you might need to run some BackupPC programs as the BackupPC user for testing purposes, you can use the -s option to su to explicitly run a shell, eg:</p>
+
+<pre><code>    su -s /bin/bash __BACKUPPCUSER__</code></pre>
+
 <p>Depending upon your configuration you might also need the -l option.</p>
+
 </dd>
-<dt><strong><a name="data_directory" class="item">Data Directory</a></strong></dt>
-
+<dt id="Data-Directory">Data Directory</dt>
 <dd>
-<p>You need to decide where to put the data directory, below which
-all the BackupPC data is stored.  This needs to be a big file system.</p>
+
+<p>You need to decide where to put the data directory, below which all the BackupPC data is stored. This needs to be a big file system.</p>
+
 <p>On this installation, this is __TOPDIR__.</p>
+
 </dd>
-<dt><strong><a name="install_directory" class="item">Install Directory</a></strong></dt>
-
+<dt id="Install-Directory">Install Directory</dt>
 <dd>
-<p>You should decide where the BackupPC scripts, libraries and documentation
-should be installed, eg: /usr/local/BackupPC.</p>
+
+<p>You should decide where the BackupPC scripts, libraries and documentation should be installed, eg: /usr/local/BackupPC.</p>
+
 <p>On this installation, this is __INSTALLDIR__.</p>
+
 </dd>
-<dt><strong><a name="cgi_bin_directory" class="item">CGI bin Directory</a></strong></dt>
-
+<dt id="CGI-bin-Directory">CGI bin Directory</dt>
 <dd>
-<p>You should decide where the BackupPC CGI script resides.  This will
-usually be below Apache's cgi-bin directory.</p>
-<p>It is also possible to use a different directory and use Apache's
-``&lt;Directory&gt;'' directive to specifiy that location.  See the Apache
-HTTP Server documentation for additional information.</p>
+
+<p>You should decide where the BackupPC CGI script resides. This will usually be below Apache&#39;s cgi-bin directory.</p>
+
+<p>It is also possible to use a different directory and use Apache&#39;s ``&lt;Directory&gt;&#39;&#39; directive to specifiy that location. See the Apache HTTP Server documentation for additional information.</p>
+
 <p>On this installation, this is __CGIDIR__.</p>
-</dd>
-<dt><strong><a name="apache_image_directory" class="item">Apache image Directory</a></strong></dt>
-
-<dd>
-<p>A directory where BackupPC's images are stored so that Apache can
-serve them.  You should ensure this directory is readable by Apache and
-create a symlink to this directory from the BackupPC CGI bin Directory.</p>
-</dd>
-<dt><strong><a name="config_and_log_directories" class="item">Config and Log Directories</a></strong></dt>
-
-<dd>
-<p>In this installation the configuration and log directories are
-located in the following locations:</p>
-<pre>
-    __CONFDIR__/config.pl    main config file
+
+</dd>
+<dt id="Apache-image-Directory">Apache image Directory</dt>
+<dd>
+
+<p>A directory where BackupPC&#39;s images are stored so that Apache can serve them. You should ensure this directory is readable by Apache and create a symlink to this directory from the BackupPC CGI bin Directory.</p>
+
+</dd>
+<dt id="Config-and-Log-Directories">Config and Log Directories</dt>
+<dd>
+
+<p>In this installation the configuration and log directories are located in the following locations:</p>
+
+<pre><code>    __CONFDIR__/config.pl    main config file
     __CONFDIR__/hosts        hosts file
     __CONFDIR__/pc/HOST.pl   per-pc config file
-    __LOGDIR__/BackupPC      log files, pid, status</pre>
-<p>The configure.pl script doesn't prompt for these locations but
-they can be set for new installations using command-line options.</p>
+    __LOGDIR__/BackupPC      log files, pid, status</code></pre>
+
+<p>The configure.pl script doesn&#39;t prompt for these locations but they can be set for new installations using command-line options.</p>
+
 </dd>
 </dl>
-<p>
-</p>
-<h2><a name="step_3__setting_up_config_pl">Step 3: Setting up config.pl</a></h2>
-<p>After running configure.pl, browse through the config file,
-__CONFDIR__/config.pl, and make sure all the default settings are
-correct. In particular, you will need to decide whether to use
-smb, tar,or rsync or ftp transport (or whether to set it on a
-per-PC basis) and set the relevant parameters for that transport
-method. See the section <a href="#step_5__client_setup">Client Setup</a> for
-more details.</p>
-<p>
-</p>
-<h2><a name="step_4__setting_up_the_hosts_file">Step 4: Setting up the hosts file</a></h2>
-<p>The file __CONFDIR__/hosts contains the list of clients to backup.
-BackupPC reads this file in three cases:</p>
+
+<h2 id="Step-3:-Setting-up-config.pl">Step 3: Setting up config.pl</h2>
+
+<p>After running configure.pl, browse through the config file, __CONFDIR__/config.pl, and make sure all the default settings are correct. In particular, you will need to decide whether to use smb, tar,or rsync or ftp transport (or whether to set it on a per-PC basis) and set the relevant parameters for that transport method. See the section <a href="#Step-5:-Client-Setup">&quot;Step 5: Client Setup&quot;</a> for more details.</p>
+
+<h2 id="Step-4:-Setting-up-the-hosts-file">Step 4: Setting up the hosts file</h2>
+
+<p>The file __CONFDIR__/hosts contains the list of clients to backup. BackupPC reads this file in three cases:</p>
+
 <ul>
-<li>
-<p>Upon startup.</p>
-</li>
-<li>
-<p>When BackupPC is sent a HUP (-1) signal.  Assuming you installed the
-init.d script, you can also do this with &quot;/etc/init.d/backuppc reload&quot;.</p>
-</li>
-<li>
-<p>When the modification time of the hosts file changes.  BackupPC
-checks the modification time once during each regular wakeup.</p>
+
+<li><p>Upon startup.</p>
+
+</li>
+<li><p>When BackupPC is sent a HUP (-1) signal. Assuming you installed the init.d script, you can also do this with &quot;/etc/init.d/backuppc reload&quot;.</p>
+
+</li>
+<li><p>When the modification time of the hosts file changes. BackupPC checks the modification time once during each regular wakeup.</p>
+
 </li>
 </ul>
-<p>Whenever you change the hosts file (to add or remove a host) you can
-either do a kill -HUP BackupPC_pid or simply wait until the next regular
-wakeup period.</p>
-<p>Each line in the hosts file contains three fields, separated
-by white space:</p>
+
+<p>Whenever you change the hosts file (to add or remove a host) you can either do a kill -HUP BackupPC_pid or simply wait until the next regular wakeup period.</p>
+
+<p>Each line in the hosts file contains three fields, separated by white space:</p>
+
 <dl>
-<dt><strong><a name="host_name" class="item">Host name</a></strong></dt>
 
+<dt id="Host-name">Host name</dt>
 <dd>
-<p>This is typically the host name or NetBios name of the client machine
-and should be in lower case.  The host name can contain spaces (escape
-with a backslash), but it is not recommended.</p>
-<p>Please read the section <a href="#how_backuppc_finds_hosts">How BackupPC Finds Hosts</a>.</p>
-<p>In certain cases you might want several distinct clients to refer
-to the same physical machine.  For example, you might have a database
-you want to backup, and you want to bracket the backup of the database
-with shutdown/restart using <a href="#_conf_dumppreusercmd_">$Conf{DumpPreUserCmd}</a> and <a href="#_conf_dumppostusercmd_">$Conf{DumpPostUserCmd}</a>.
-But you also want to backup the rest of the machine while the database
-is still running.  In the case you can specify two different clients in
-the host file, using any mnemonic name (eg: myhost_mysql and myhost), and
-use <a href="#_conf_clientnamealias_">$Conf{ClientNameAlias}</a> in myhost_mysql's config.pl to specify the
-real host name of the machine.</p>
+
+<p>This is typically the host name or NetBios name of the client machine and should be in lower case. The host name can contain spaces (escape with a backslash), but it is not recommended.</p>
+
+<p>Please read the section <a href="#How-BackupPC-Finds-Hosts">&quot;How BackupPC Finds Hosts&quot;</a>.</p>
+
+<p>In certain cases you might want several distinct clients to refer to the same physical machine. For example, you might have a database you want to backup, and you want to bracket the backup of the database with shutdown/restart using <a href="#_conf_dumppreusercmd_">$Conf{DumpPreUserCmd}</a> and <a href="#_conf_dumppostusercmd_">$Conf{DumpPostUserCmd}</a>. But you also want to backup the rest of the machine while the database is still running. In the case you can specify two different clients in the host file, using any mnemonic name (eg: myhost_mysql and myhost), and use <a href="#_conf_clientnamealias_">$Conf{ClientNameAlias}</a> in myhost_mysql&#39;s config.pl to specify the real host name of the machine.</p>
+
 </dd>
-<dt><strong><a name="dhcp_flag" class="item">DHCP flag</a></strong></dt>
-
+<dt id="DHCP-flag">DHCP flag</dt>
 <dd>
-<p>Starting with v2.0.0 the way hosts are discovered has changed and now
-in most cases you should specify 0 for the DHCP flag, even if the host
-has a dynamically assigned IP address.
-Please read the section <a href="#how_backuppc_finds_hosts">How BackupPC Finds Hosts</a>
-to understand whether you need to set the DHCP flag.</p>
-<p>You only need to set DHCP to 1 if your client machine doesn't
-respond to the NetBios multicast request:</p>
-<pre>
-    nmblookup myHost</pre>
+
+<p>Starting with v2.0.0 the way hosts are discovered has changed and now in most cases you should specify 0 for the DHCP flag, even if the host has a dynamically assigned IP address. Please read the section <a href="#How-BackupPC-Finds-Hosts">&quot;How BackupPC Finds Hosts&quot;</a> to understand whether you need to set the DHCP flag.</p>
+
+<p>You only need to set DHCP to 1 if your client machine doesn&#39;t respond to the NetBios multicast request:</p>
+
+<pre><code>    nmblookup myHost</code></pre>
+
 <p>but does respond to a request directed to its IP address:</p>
-<pre>
-    nmblookup -A W.X.Y.Z</pre>
-<p>If you do set DHCP to 1 on any client you will need to specify the range of
-DHCP addresses to search is specified in <a href="#_conf_dhcpaddressranges_">$Conf{DHCPAddressRanges}</a>.</p>
-<p>Note also that the <a href="#_conf_clientnamealias_">$Conf{ClientNameAlias}</a> feature does not work for
-clients with DHCP set to 1.</p>
-</dd>
-<dt><strong><a name="user_name" class="item">User name</a></strong></dt>
-
-<dd>
-<p>This should be the unix login/email name of the user who &quot;owns&quot; or uses
-this machine. This is the user who will be sent email about this
-machine, and this user will have permission to stop/start/browse/restore
-backups for this host.  Leave this blank if no specific person should
-receive email or be allowed to stop/start/browse/restore backups
-for this host.  Administrators will still have full permissions.</p>
-</dd>
-<dt><strong><a name="more_users" class="item">More users</a></strong></dt>
-
-<dd>
-<p>Additional user names, separate by commas and with no white space,
-can be specified.  These users will also have full permission in
-the CGI interface to stop/start/browse/restore backups for this host.
-These users will not be sent email about this host.</p>
+
+<pre><code>    nmblookup -A W.X.Y.Z</code></pre>
+
+<p>If you do set DHCP to 1 on any client you will need to specify the range of DHCP addresses to search is specified in <a href="#_conf_dhcpaddressranges_">$Conf{DHCPAddressRanges}</a>.</p>
+
+<p>Note also that the <a href="#_conf_clientnamealias_">$Conf{ClientNameAlias}</a> feature does not work for clients with DHCP set to 1.</p>
+
+</dd>
+<dt id="User-name">User name</dt>
+<dd>
+
+<p>This should be the unix login/email name of the user who &quot;owns&quot; or uses this machine. This is the user who will be sent email about this machine, and this user will have permission to stop/start/browse/restore backups for this host. Leave this blank if no specific person should receive email or be allowed to stop/start/browse/restore backups for this host. Administrators will still have full permissions.</p>
+
+</dd>
+<dt id="More-users">More users</dt>
+<dd>
+
+<p>Additional user names, separate by commas and with no white space, can be specified. These users will also have full permission in the CGI interface to stop/start/browse/restore backups for this host. These users will not be sent email about this host.</p>
+
 </dd>
 </dl>
-<p>The first non-comment line of the hosts file is special: it contains
-the names of the columns and should not be edited.</p>
-<p>Here's a simple example of a hosts file:</p>
-<pre>
-    host        dhcp    user      moreUsers
+
+<p>The first non-comment line of the hosts file is special: it contains the names of the columns and should not be edited.</p>
+
+<p>Here&#39;s a simple example of a hosts file:</p>
+
+<pre><code>    host        dhcp    user      moreUsers
     farside     0       craig     jim,dave
-    larson      1       gary      andy</pre>
-<p>
-</p>
-<h2><a name="step_5__client_setup">Step 5: Client Setup</a></h2>
-<p>Four methods for getting backup data from a client are supported:
-smb, tar, rsync and ftp.  Smb or rsync are the preferred methods
-for WinXX clients and rsync or tar are the preferred methods for
-linux/unix/MacOSX clients.</p>
-<p>The transfer method is set using the <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> configuration
-setting. If you have a mixed environment (ie: you will use smb for some
-clients and tar for others), you will need to pick the most common
-choice for <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> for the main config.pl file, and then
-override it in the per-PC config file for those hosts that will use
-the other method.  (Or you could run two completely separate instances
-of BackupPC, with different data directories, one for WinXX and the
-other for linux/unix, but then common files between the different
-machine types will duplicated.)</p>
+    larson      1       gary      andy</code></pre>
+
+<h2 id="Step-5:-Client-Setup">Step 5: Client Setup</h2>
+
+<p>Four methods for getting backup data from a client are supported: smb, tar, rsync and ftp. Smb or rsync are the preferred methods for WinXX clients and rsync or tar are the preferred methods for linux/unix/MacOSX clients.</p>
+
+<p>The transfer method is set using the <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> configuration setting. If you have a mixed environment (ie: you will use smb for some clients and tar for others), you will need to pick the most common choice for <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> for the main config.pl file, and then override it in the per-PC config file for those hosts that will use the other method. (Or you could run two completely separate instances of BackupPC, with different data directories, one for WinXX and the other for linux/unix, but then common files between the different machine types will duplicated.)</p>
+
 <p>Here are some brief client setup notes:</p>
+
 <dl>
-<dt><strong><a name="winxx" class="item">WinXX</a></strong></dt>
 
+<dt id="WinXX">WinXX</dt>
 <dd>
-<p>One setup for WinXX clients is to set <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> to &quot;smb&quot;.
-Actually, rsyncd is the better method for WinXX if you are prepared to
-run rsync/cygwin on your WinXX client.</p>
-<p>If you want to use rsyncd for WinXX clients you can find a pre-packaged
-zip file on <a href="http://backuppc.sourceforge.net">http://backuppc.sourceforge.net</a>. The package is called
-cygwin-rsync. It contains rsync.exe, template setup files and the
-minimal set of cygwin libraries for everything to run.  The README file
-contains instructions for running rsync as a service, so it starts
-automatically everytime you boot your machine.  If you use rsync
-to backup WinXX machines, be sure to set <a href="#_conf_clientcharset_">$Conf{ClientCharset}</a>
-correctly (eg: 'cp1252') so that the WinXX file name encoding is
-correctly converted to utf8.</p>
-<p>Otherwise, to use SMB, you can either create shares for the data you want
-to backup or your can use the existing C$ share.  To create a new 
-share, open &quot;My Computer&quot;, right click on the drive (eg: C), and
-select &quot;Sharing...&quot; (or select &quot;Properties&quot; and select the &quot;Sharing&quot;
-tab). In this dialog box you can enable sharing, select the share name
-and permissions.</p>
-<p>All Windows NT based OS (NT, 2000, XP Pro), are configured by default 
-to share the entire C drive as C$.  This is a special share used for 
-various administration functions, one of which is to grant access to backup 
-operators. All you need to do is create a new domain user, specifically 
-for backup. Then add the new backup user to the built in &quot;Backup 
-Operators&quot; group. You now have backup capability for any directory on 
-any computer in the domain in one easy step. This avoids using 
-administrator accounts and only grants permission to do exactly what you 
-want for the given user, i.e.: backup.
-Also, for additional security, you may wish to deny the ability for this 
-user to logon to computers in the default domain policy.</p>
-<p>If this machine uses DHCP you will also need to make sure the
-NetBios name is set.  Go to Control Panel|System|Network Identification
-(on Win2K) or Control Panel|System|Computer Name (on WinXP).
-Also, you should go to Control Panel|Network Connections|Local Area
-Connection|Properties|Internet Protocol (TCP/IP)|Properties|Advanced|WINS
-and verify that NetBios is not disabled.</p>
-<p>The relevant configuration settings are <a href="#_conf_smbsharename_">$Conf{SmbShareName}</a>,
-<a href="#_conf_smbshareusername_">$Conf{SmbShareUserName}</a>, <a href="#_conf_smbsharepasswd_">$Conf{SmbSharePasswd}</a>, <a href="#_conf_smbclientpath_">$Conf{SmbClientPath}</a>,
-<a href="#_conf_smbclientfullcmd_">$Conf{SmbClientFullCmd}</a>, <a href="#_conf_smbclientincrcmd_">$Conf{SmbClientIncrCmd}</a> and
-<a href="#_conf_smbclientrestorecmd_">$Conf{SmbClientRestoreCmd}</a>.</p>
-<p>BackupPC needs to know the smb share user name and password for a
-client machine that uses smb.  The user name is specified in
-<a href="#_conf_smbshareusername_">$Conf{SmbShareUserName}</a>. There are four ways to tell BackupPC the
-smb share password:</p>
+
+<p>One setup for WinXX clients is to set <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> to &quot;smb&quot;. Actually, rsyncd is the better method for WinXX if you are prepared to run rsync/cygwin on your WinXX client.</p>
+
+<p>If you want to use rsyncd for WinXX clients you can find a pre-packaged zip file on <a href="http://backuppc.sourceforge.net">http://backuppc.sourceforge.net</a>. The package is called cygwin-rsync. It contains rsync.exe, template setup files and the minimal set of cygwin libraries for everything to run. The README file contains instructions for running rsync as a service, so it starts automatically everytime you boot your machine. If you use rsync to backup WinXX machines, be sure to set <a href="#_conf_clientcharset_">$Conf{ClientCharset}</a> correctly (eg: &#39;cp1252&#39;) so that the WinXX file name encoding is correctly converted to utf8.</p>
+
+<p>Otherwise, to use SMB, you can either create shares for the data you want to backup or your can use the existing C$ share. To create a new share, open &quot;My Computer&quot;, right click on the drive (eg: C), and select &quot;Sharing...&quot; (or select &quot;Properties&quot; and select the &quot;Sharing&quot; tab). In this dialog box you can enable sharing, select the share name and permissions.</p>
+
+<p>All Windows NT based OS (NT, 2000, XP Pro), are configured by default to share the entire C drive as C$. This is a special share used for various administration functions, one of which is to grant access to backup operators. All you need to do is create a new domain user, specifically for backup. Then add the new backup user to the built in &quot;Backup Operators&quot; group. You now have backup capability for any directory on any computer in the domain in one easy step. This avoids using administrator accounts and only grants permission to do exactly what you want for the given user, i.e.: backup. Also, for additional security, you may wish to deny the ability for this user to logon to computers in the default domain policy.</p>
+
+<p>If this machine uses DHCP you will also need to make sure the NetBios name is set. Go to Control Panel|System|Network Identification (on Win2K) or Control Panel|System|Computer Name (on WinXP). Also, you should go to Control Panel|Network Connections|Local Area Connection|Properties|Internet Protocol (TCP/IP)|Properties|Advanced|WINS and verify that NetBios is not disabled.</p>
+
+<p>The relevant configuration settings are <a href="#_conf_smbsharename_">$Conf{SmbShareName}</a>, <a href="#_conf_smbshareusername_">$Conf{SmbShareUserName}</a>, <a href="#_conf_smbsharepasswd_">$Conf{SmbSharePasswd}</a>, <a href="#_conf_smbclientpath_">$Conf{SmbClientPath}</a>, <a href="#_conf_smbclientfullcmd_">$Conf{SmbClientFullCmd}</a>, <a href="#_conf_smbclientincrcmd_">$Conf{SmbClientIncrCmd}</a> and <a href="#_conf_smbclientrestorecmd_">$Conf{SmbClientRestoreCmd}</a>.</p>
+
+<p>BackupPC needs to know the smb share user name and password for a client machine that uses smb. The user name is specified in <a href="#_conf_smbshareusername_">$Conf{SmbShareUserName}</a>. There are four ways to tell BackupPC the smb share password:</p>
+
 <ul>
-<li>
-<p>As an environment variable BPC_SMB_PASSWD set before BackupPC starts.
-If you start BackupPC manually the BPC_SMB_PASSWD variable must be set
-manually first.  For backward compatibility for v1.5.0 and prior, the
-environment variable PASSWD can be used if BPC_SMB_PASSWD is not set.
-Warning: on some systems it is possible to see environment variables of
-running processes.</p>
-</li>
-<li>
-<p>Alternatively the BPC_SMB_PASSWD setting can be included in
-/etc/init.d/backuppc, in which case you must make sure this file
-is not world (other) readable.</p>
-</li>
-<li>
-<p>As a configuration variable <a href="#_conf_smbsharepasswd_">$Conf{SmbSharePasswd}</a> in
-__CONFDIR__/config.pl.  If you put the password
-here you must make sure this file is not world (other) readable.</p>
-</li>
-<li>
-<p>As a configuration variable <a href="#_conf_smbsharepasswd_">$Conf{SmbSharePasswd}</a> in the per-PC
-configuration file (__CONFDIR__/pc/$host.pl or
-__TOPDIR__/pc/$host/config.pl in non-FHS versions of BackupPC).
-You will have to use this option if the smb share password is different
-for each host. If you put the password here you must make sure this file
-is not world (other) readable.</p>
+
+<li><p>As an environment variable BPC_SMB_PASSWD set before BackupPC starts. If you start BackupPC manually the BPC_SMB_PASSWD variable must be set manually first. For backward compatibility for v1.5.0 and prior, the environment variable PASSWD can be used if BPC_SMB_PASSWD is not set. Warning: on some systems it is possible to see environment variables of running processes.</p>
+
+</li>
+<li><p>Alternatively the BPC_SMB_PASSWD setting can be included in /etc/init.d/backuppc, in which case you must make sure this file is not world (other) readable.</p>
+
+</li>
+<li><p>As a configuration variable <a href="#_conf_smbsharepasswd_">$Conf{SmbSharePasswd}</a> in __CONFDIR__/config.pl. If you put the password here you must make sure this file is not world (other) readable.</p>
+
+</li>
+<li><p>As a configuration variable <a href="#_conf_smbsharepasswd_">$Conf{SmbSharePasswd}</a> in the per-PC configuration file (__CONFDIR__/pc/$host.pl or __TOPDIR__/pc/$host/config.pl in non-FHS versions of BackupPC). You will have to use this option if the smb share password is different for each host. If you put the password here you must make sure this file is not world (other) readable.</p>
+
 </li>
 </ul>
-<p>Placement and protection of the smb share password is a possible
-security risk, so please double-check the file and directory
-permissions.  In a future version there might be support for
-encryption of this password, but a private key will still have to
-be stored in a protected place.  Suggestions are welcome.</p>
-<p>As an alternative to setting <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> to &quot;smb&quot; (using
-smbclient) for WinXX clients, you can use an smb network filesystem (eg:
-ksmbfs or similar) on your linux/unix server to mount the share,
-and then set <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> to &quot;tar&quot; (use tar on the network
-mounted file system).</p>
-<p>Also, to make sure that file names with special characters are correctly
-transferred by smbclient you should make sure that the smb.conf file
-has (for samba 3.x):</p>
-<pre>
-    [global]
-        unix charset = UTF8</pre>
-<p>UTF8 is the default setting, so if the parameter is missing then it
-is ok.  With this setting <a href="#_conf_clientcharset_">$Conf{ClientCharset}</a> should be emtpy,
-since smbclient has already converted the file names to utf8.</p>
+
+<p>Placement and protection of the smb share password is a possible security risk, so please double-check the file and directory permissions. In a future version there might be support for encryption of this password, but a private key will still have to be stored in a protected place. Suggestions are welcome.</p>
+
+<p>As an alternative to setting <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> to &quot;smb&quot; (using smbclient) for WinXX clients, you can use an smb network filesystem (eg: ksmbfs or similar) on your linux/unix server to mount the share, and then set <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> to &quot;tar&quot; (use tar on the network mounted file system).</p>
+
+<p>Also, to make sure that file names with special characters are correctly transferred by smbclient you should make sure that the smb.conf file has (for samba 3.x):</p>
+
+<pre><code>    [global]
+        unix charset = UTF8</code></pre>
+
+<p>UTF8 is the default setting, so if the parameter is missing then it is ok. With this setting <a href="#_conf_clientcharset_">$Conf{ClientCharset}</a> should be emtpy, since smbclient has already converted the file names to utf8.</p>
+
 </dd>
-<dt><strong><a name="linux_unix" class="item">Linux/Unix</a></strong></dt>
-
+<dt id="Linux-Unix">Linux/Unix</dt>
 <dd>
-<p>The preferred setup for linux/unix clients is to set <a href="#_conf_xfermethod_">$Conf{XferMethod}</a>
-to &quot;rsync&quot;, &quot;rsyncd&quot; or &quot;tar&quot;.</p>
-<p>You can use either rsync, smb, or tar for linux/unix machines. Smb requires
-that the Samba server (smbd) be run to provide the shares. Since the smb
-protocol can't represent special files like symbolic links and fifos,
-tar and rsync are the better transport methods for linux/unix machines.
-(In fact, by default samba makes symbolic links look like the file or
-directory that they point to, so you could get an infinite loop if a
-symbolic link points to the current or parent directory. If you really
-need to use Samba shares for linux/unix backups you should turn off the
-&quot;follow symlinks&quot; samba config setting. See the smb.conf manual page.)</p>
+
+<p>The preferred setup for linux/unix clients is to set <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> to &quot;rsync&quot;, &quot;rsyncd&quot; or &quot;tar&quot;.</p>
+
+<p>You can use either rsync, smb, or tar for linux/unix machines. Smb requires that the Samba server (smbd) be run to provide the shares. Since the smb protocol can&#39;t represent special files like symbolic links and fifos, tar and rsync are the better transport methods for linux/unix machines. (In fact, by default samba makes symbolic links look like the file or directory that they point to, so you could get an infinite loop if a symbolic link points to the current or parent directory. If you really need to use Samba shares for linux/unix backups you should turn off the &quot;follow symlinks&quot; samba config setting. See the smb.conf manual page.)</p>
+
 <p>The requirements for each Xfer Method are:</p>
+
 <dl>
-<dt><strong><a name="tar" class="item">tar</a></strong></dt>
-
-<dd>
-<p>You must have GNU tar on the client machine.  Use &quot;tar --version&quot;
-or &quot;gtar --version&quot; to verify.  The version should be at least
-1.13.7, and 1.13.20 or greater is recommended.  Tar is run on
-the client machine via rsh or ssh.</p>
-<p>The relevant configuration settings are <a href="#_conf_tarclientpath_">$Conf{TarClientPath}</a>,
-<a href="#_conf_tarsharename_">$Conf{TarShareName}</a>, <a href="#_conf_tarclientcmd_">$Conf{TarClientCmd}</a>, <a href="#_conf_tarfullargs_">$Conf{TarFullArgs}</a>,
-<a href="#_conf_tarincrargs_">$Conf{TarIncrArgs}</a>, and <a href="#_conf_tarclientrestorecmd_">$Conf{TarClientRestoreCmd}</a>.</p>
-</dd>
-<dt><strong><a name="rsync" class="item">rsync</a></strong></dt>
-
-<dd>
-<p>You should have at least rsync 2.6.3, and the latest version is
-recommended.  Rsync is run on the remote client via rsh or ssh.</p>
-<p>The relevant configuration settings are <a href="#_conf_rsyncclientpath_">$Conf{RsyncClientPath}</a>,
-<a href="#_conf_rsyncclientcmd_">$Conf{RsyncClientCmd}</a>, <a href="#_conf_rsyncclientrestorecmd_">$Conf{RsyncClientRestoreCmd}</a>, <a href="#_conf_rsyncsharename_">$Conf{RsyncShareName}</a>,
-<a href="#_conf_rsyncargs_">$Conf{RsyncArgs}</a>, and <a href="#_conf_rsyncrestoreargs_">$Conf{RsyncRestoreArgs}</a>.</p>
-</dd>
-<dt><strong><a name="rsyncd" class="item">rsyncd</a></strong></dt>
-
-<dd>
-<p>You should have at least rsync 2.6.3, and the latest version is
-recommended.  In this case the rsync daemon should be running on
-the client machine and BackupPC connects directly to it.</p>
-<p>The relevant configuration settings are <a href="#_conf_rsyncdclientport_">$Conf{RsyncdClientPort}</a>,
-<a href="#_conf_rsyncdusername_">$Conf{RsyncdUserName}</a>, <a href="#_conf_rsyncdpasswd_">$Conf{RsyncdPasswd}</a>, <a href="#_conf_rsyncdauthrequired_">$Conf{RsyncdAuthRequired}</a>,
-<a href="#_conf_rsyncsharename_">$Conf{RsyncShareName}</a>, <a href="#_conf_rsyncargs_">$Conf{RsyncArgs}</a>, <a href="#_conf_rsyncargsextra_">$Conf{RsyncArgsExtra}</a>, and
-<a href="#_conf_rsyncrestoreargs_">$Conf{RsyncRestoreArgs}</a>. <a href="#_conf_rsyncsharename_">$Conf{RsyncShareName}</a> is the name of an rsync
-module (ie: the thing in square brackets in rsyncd's conf file -- see
-rsyncd.conf), not a file system path.</p>
-<p>Be aware that rsyncd will remove the leading '/' from path names in
-symbolic links if you specify &quot;use chroot = no&quot; in the rsynd.conf file.
-See the rsyncd.conf manual page for more information.</p>
-</dd>
-<dt><strong><a name="ftp" class="item">ftp</a></strong></dt>
-
-<dd>
-<p>You need to be running an ftp server on the client machine.
-The relevant configuration settings are <a href="#_conf_ftpsharename_">$Conf{FtpShareName}</a>,
-<a href="#_conf_ftpusername_">$Conf{FtpUserName}</a>, <a href="#_conf_ftppasswd_">$Conf{FtpPasswd}</a>, <a href="#_conf_ftpblocksize_">$Conf{FtpBlockSize}</a>,
-<a href="#_conf_ftpport_">$Conf{FtpPort}</a>, <a href="#_conf_ftptimeout_">$Conf{FtpTimeout}</a>, and <a href="#_conf_ftpfollowsymlinks_">$Conf{FtpFollowSymlinks}</a>.</p>
-</dd>
-</dl>
-<p>You need to set <a href="#_conf_clientcharset_">$Conf{ClientCharset}</a> to the client's charset so that
-file names are correctly converted to utf8.  Use &quot;locale charmap&quot;
-on the client to see its charset.</p>
-<p>For linux/unix machines you should not backup &quot;/proc&quot;.  This directory
-contains a variety of files that look like regular files but they are
-special files that don't need to be backed up (eg: /proc/kcore is a
-regular file that contains physical memory).  See <a href="#_conf_backupfilesexclude_">$Conf{BackupFilesExclude}</a>.
-It is safe to back up /dev since it contains mostly character-special
-and block-special files, which are correctly handed by BackupPC
-(eg: backing up /dev/hda5 just saves the block-special file information,
-not the contents of the disk).</p>
-<p>Alternatively, rather than backup all the file systems as a single
-share (&quot;/&quot;), it is easier to restore a single file system if you backup
-each file system separately.  To do this you should list each file system
-mount point in <a href="#_conf_tarsharename_">$Conf{TarShareName}</a> or <a href="#_conf_rsyncsharename_">$Conf{RsyncShareName}</a>, and add the
---one-file-system option to <a href="#_conf_tarclientcmd_">$Conf{TarClientCmd}</a> or <a href="#_conf_rsyncargs_">$Conf{RsyncArgs}</a>.
-In this case there is no need to exclude /proc explicitly since it looks
-like a different file system.</p>
-<p>Next you should decide whether to run tar over ssh, rsh or nfs. Ssh is
-the preferred method. Rsh is not secure and therefore not recommended.
-Nfs will work, but you need to make sure that the BackupPC user (running
-on the server) has sufficient permissions to read all the files below
-the nfs mount.</p>
-<p>Ssh allows BackupPC to run as a privileged user on the client (eg:
-root), since it needs sufficient permissions to read all the backup
-files. Ssh is setup so that BackupPC on the server (an otherwise low
-privileged user) can ssh as root on the client, without being prompted
-for a password. There are two common versions of ssh: v1 and v2. Here
-are some instructions for one way to setup ssh.  (Check which version
-of SSH you have by typing &quot;ssh&quot; or &quot;man ssh&quot;.)</p>
-</dd>
-<dt><strong><a name="macosx" class="item">MacOSX</a></strong></dt>
-
-<dd>
-<p>In general this should be similar to Linux/Unix machines.
-In versions 10.4 and later, the native MacOSX tar works,
-and also supports resource forks.  xtar is another option,
-and rsync works too (although the MacOSX-supplied rsync
-has an extension for extended attributes that is not
-compatible with standard rsync).</p>
-</dd>
-<dt><strong><a name="ssh_setup" class="item">SSH Setup</a></strong></dt>
-
-<dd>
-<p>SSH is a secure way to run tar or rsync on a backup client to extract
-the data.  SSH provides strong authentication and encryption of
-the network data.</p>
-<p>Note that if you run rsyncd (rsync daemon), ssh is not used.
-In this case, rsyncd provides its own authentication, but there
-is no encryption of network data.  If you want encryption of
-network data you can use ssh to create a tunnel, or use a
-program like stunnel.</p>
-<p>Setup instructions for ssh can be found at
-<a href="http://backuppc.sourceforge.net/faq/ssh.html">http://backuppc.sourceforge.net/faq/ssh.html</a> or on the Wiki.</p>
-</dd>
-<dt><strong><a name="clients_that_use_dhcp" class="item">Clients that use DHCP</a></strong></dt>
-
-<dd>
-<p>If a client machine uses DHCP BackupPC needs some way to find the
-IP address given the host name.  One alternative is to set dhcp
-to 1 in the hosts file, and BackupPC will search a pool of IP
-addresses looking for hosts.  More efficiently, it is better to
-set dhcp = 0 and provide a mechanism for BackupPC to find the
-IP address given the host name.</p>
-<p>For WinXX machines BackupPC uses the NetBios name server to determine
-the IP address given the host name.
-For unix machines you can run nmbd (the NetBios name server) from
-the Samba distribution so that the machine responds to a NetBios
-name request. See the manual page and Samba documentation for more
-information.</p>
-<p>Alternatively, you can set <a href="#_conf_nmblookupfindhostcmd_">$Conf{NmbLookupFindHostCmd}</a> to any command
-that returns the IP address given the host name.</p>
-<p>Please read the section <a href="#how_backuppc_finds_hosts">How BackupPC Finds Hosts</a>
-for more details.</p>
-</dd>
-</dl>
-<p>
-</p>
-<h2><a name="step_6__running_backuppc">Step 6: Running BackupPC</a></h2>
-<p>The installation contains an init.d backuppc script that can be copied
-to /etc/init.d so that BackupPC can auto-start on boot.
-See init.d/README for further instructions.</p>
-<p>BackupPC should be ready to start.  If you installed the init.d script,
-then you should be able to run BackupPC with:</p>
-<pre>
-    /etc/init.d/backuppc start</pre>
-<p>(This script can also be invoked with &quot;stop&quot; to stop BackupPC and &quot;reload&quot;
-to tell BackupPC to reload config.pl and the hosts file.)</p>
+
+<dt id="tar">tar</dt>
+<dd>
+
+<p>You must have GNU tar on the client machine. Use &quot;tar --version&quot; or &quot;gtar --version&quot; to verify. The version should be at least 1.13.7, and 1.13.20 or greater is recommended. Tar is run on the client machine via rsh or ssh.</p>
+
+<p>The relevant configuration settings are <a href="#_conf_tarclientpath_">$Conf{TarClientPath}</a>, <a href="#_conf_tarsharename_">$Conf{TarShareName}</a>, <a href="#_conf_tarclientcmd_">$Conf{TarClientCmd}</a>, <a href="#_conf_tarfullargs_">$Conf{TarFullArgs}</a>, <a href="#_conf_tarincrargs_">$Conf{TarIncrArgs}</a>, and <a href="#_conf_tarclientrestorecmd_">$Conf{TarClientRestoreCmd}</a>.</p>
+
+</dd>
+<dt id="rsync">rsync</dt>
+<dd>
+
+<p>You should have at least rsync 2.6.3, and the latest version is recommended. Rsync is run on the remote client via rsh or ssh.</p>
+
+<p>The relevant configuration settings are <a href="#_conf_rsyncclientpath_">$Conf{RsyncClientPath}</a>, <a href="#_conf_rsyncclientcmd_">$Conf{RsyncClientCmd}</a>, <a href="#_conf_rsyncclientrestorecmd_">$Conf{RsyncClientRestoreCmd}</a>, <a href="#_conf_rsyncsharename_">$Conf{RsyncShareName}</a>, <a href="#_conf_rsyncargs_">$Conf{RsyncArgs}</a>, and <a href="#_conf_rsyncrestoreargs_">$Conf{RsyncRestoreArgs}</a>.</p>
+
+</dd>
+<dt id="rsyncd">rsyncd</dt>
+<dd>
+
+<p>You should have at least rsync 2.6.3, and the latest version is recommended. In this case the rsync daemon should be running on the client machine and BackupPC connects directly to it.</p>
+
+<p>The relevant configuration settings are <a href="#_conf_rsyncdclientport_">$Conf{RsyncdClientPort}</a>, <a href="#_conf_rsyncdusername_">$Conf{RsyncdUserName}</a>, <a href="#_conf_rsyncdpasswd_">$Conf{RsyncdPasswd}</a>, <a href="#_conf_rsyncdauthrequired_">$Conf{RsyncdAuthRequired}</a>, <a href="#_conf_rsyncsharename_">$Conf{RsyncShareName}</a>, <a href="#_conf_rsyncargs_">$Conf{RsyncArgs}</a>, <a href="#_conf_rsyncargsextra_">$Conf{RsyncArgsExtra}</a>, and <a href="#_conf_rsyncrestoreargs_">$Conf{RsyncRestoreArgs}</a>. <a href="#_conf_rsyncsharename_">$Conf{RsyncShareName}</a> is the name of an rsync module (ie: the thing in square brackets in rsyncd&#39;s conf file -- see rsyncd.conf), not a file system path.</p>
+
+<p>Be aware that rsyncd will remove the leading &#39;/&#39; from path names in symbolic links if you specify &quot;use chroot = no&quot; in the rsynd.conf file. See the rsyncd.conf manual page for more information.</p>
+
+</dd>
+<dt id="ftp">ftp</dt>
+<dd>
+
+<p>You need to be running an ftp server on the client machine. The relevant configuration settings are <a href="#_conf_ftpsharename_">$Conf{FtpShareName}</a>, <a href="#_conf_ftpusername_">$Conf{FtpUserName}</a>, <a href="#_conf_ftppasswd_">$Conf{FtpPasswd}</a>, <a href="#_conf_ftpblocksize_">$Conf{FtpBlockSize}</a>, <a href="#_conf_ftpport_">$Conf{FtpPort}</a>, <a href="#_conf_ftptimeout_">$Conf{FtpTimeout}</a>, and <a href="#_conf_ftpfollowsymlinks_">$Conf{FtpFollowSymlinks}</a>.</p>
+
+</dd>
+</dl>
+
+<p>You need to set <a href="#_conf_clientcharset_">$Conf{ClientCharset}</a> to the client&#39;s charset so that file names are correctly converted to utf8. Use &quot;locale charmap&quot; on the client to see its charset.</p>
+
+<p>For linux/unix machines you should not backup &quot;/proc&quot;. This directory contains a variety of files that look like regular files but they are special files that don&#39;t need to be backed up (eg: /proc/kcore is a regular file that contains physical memory). See <a href="#_conf_backupfilesexclude_">$Conf{BackupFilesExclude}</a>. It is safe to back up /dev since it contains mostly character-special and block-special files, which are correctly handed by BackupPC (eg: backing up /dev/hda5 just saves the block-special file information, not the contents of the disk).</p>
+
+<p>Alternatively, rather than backup all the file systems as a single share (&quot;/&quot;), it is easier to restore a single file system if you backup each file system separately. To do this you should list each file system mount point in <a href="#_conf_tarsharename_">$Conf{TarShareName}</a> or <a href="#_conf_rsyncsharename_">$Conf{RsyncShareName}</a>, and add the --one-file-system option to <a href="#_conf_tarclientcmd_">$Conf{TarClientCmd}</a> or <a href="#_conf_rsyncargs_">$Conf{RsyncArgs}</a>. In this case there is no need to exclude /proc explicitly since it looks like a different file system.</p>
+
+<p>Next you should decide whether to run tar over ssh, rsh or nfs. Ssh is the preferred method. Rsh is not secure and therefore not recommended. Nfs will work, but you need to make sure that the BackupPC user (running on the server) has sufficient permissions to read all the files below the nfs mount.</p>
+
+<p>Ssh allows BackupPC to run as a privileged user on the client (eg: root), since it needs sufficient permissions to read all the backup files. Ssh is setup so that BackupPC on the server (an otherwise low privileged user) can ssh as root on the client, without being prompted for a password. There are two common versions of ssh: v1 and v2. Here are some instructions for one way to setup ssh. (Check which version of SSH you have by typing &quot;ssh&quot; or &quot;man ssh&quot;.)</p>
+
+</dd>
+<dt id="MacOSX">MacOSX</dt>
+<dd>
+
+<p>In general this should be similar to Linux/Unix machines. In versions 10.4 and later, the native MacOSX tar works, and also supports resource forks. xtar is another option, and rsync works too (although the MacOSX-supplied rsync has an extension for extended attributes that is not compatible with standard rsync).</p>
+
+</dd>
+<dt id="SSH-Setup">SSH Setup</dt>
+<dd>
+
+<p>SSH is a secure way to run tar or rsync on a backup client to extract the data. SSH provides strong authentication and encryption of the network data.</p>
+
+<p>Note that if you run rsyncd (rsync daemon), ssh is not used. In this case, rsyncd provides its own authentication, but there is no encryption of network data. If you want encryption of network data you can use ssh to create a tunnel, or use a program like stunnel.</p>
+
+<p>Setup instructions for ssh can be found at <a href="http://backuppc.sourceforge.net/faq/ssh.html">http://backuppc.sourceforge.net/faq/ssh.html</a> or on the Wiki.</p>
+
+</dd>
+<dt id="Clients-that-use-DHCP">Clients that use DHCP</dt>
+<dd>
+
+<p>If a client machine uses DHCP BackupPC needs some way to find the IP address given the host name. One alternative is to set dhcp to 1 in the hosts file, and BackupPC will search a pool of IP addresses looking for hosts. More efficiently, it is better to set dhcp = 0 and provide a mechanism for BackupPC to find the IP address given the host name.</p>
+
+<p>For WinXX machines BackupPC uses the NetBios name server to determine the IP address given the host name. For unix machines you can run nmbd (the NetBios name server) from the Samba distribution so that the machine responds to a NetBios name request. See the manual page and Samba documentation for more information.</p>
+
+<p>Alternatively, you can set <a href="#_conf_nmblookupfindhostcmd_">$Conf{NmbLookupFindHostCmd}</a> to any command that returns the IP address given the host name.</p>
+
+<p>Please read the section <a href="#How-BackupPC-Finds-Hosts">&quot;How BackupPC Finds Hosts&quot;</a> for more details.</p>
+
+</dd>
+</dl>
+
+<h2 id="Step-6:-Running-BackupPC">Step 6: Running BackupPC</h2>
+
+<p>The installation contains an init.d backuppc script that can be copied to /etc/init.d so that BackupPC can auto-start on boot. See init.d/README for further instructions.</p>
+
+<p>BackupPC should be ready to start. If you installed the init.d script, then you should be able to run BackupPC with:</p>
+
+<pre><code>    /etc/init.d/backuppc start</code></pre>
+
+<p>(This script can also be invoked with &quot;stop&quot; to stop BackupPC and &quot;reload&quot; to tell BackupPC to reload config.pl and the hosts file.)</p>
+
 <p>Otherwise, just run</p>
-<pre>
-     __INSTALLDIR__/bin/BackupPC -d</pre>
-<p>as user __BACKUPPCUSER__.  The -d option tells BackupPC to run as a daemon
-(ie: it does an additional fork).</p>
-<p>Any immediate errors will be printed to stderr and BackupPC will quit.
-Otherwise, look in __LOGDIR__/LOG and verify that BackupPC reports
-it has started and all is ok.</p>
-<p>
-</p>
-<h2><a name="step_7__talking_to_backuppc">Step 7: Talking to BackupPC</a></h2>
-<p>You should verify that BackupPC is running by using BackupPC_serverMesg.
-This sends a message to BackupPC via the unix (or TCP) socket and prints
-the response.  Like all BackupPC programs, BackupPC_serverMesg
-should be run as the BackupPC user (__BACKUPPCUSER__), so you
-should</p>
-<pre>
-    su __BACKUPPCUSER__</pre>
-<p>before running BackupPC_serverMesg.  If the BackupPC user is
-configured with /bin/false as the shell, you can use the -s
-option to su to explicitly run a shell, eg:</p>
-<pre>
-    su -s /bin/bash __BACKUPPCUSER__</pre>
-<p>Depending upon your configuration you might also need
-the -l option.</p>
-<p>You can request status information and start and stop backups using this
-interface. This socket interface is mainly provided for the CGI interface
-(and some of the BackupPC sub-programs use it too).  But right now we just
-want to make sure BackupPC is happy.  Each of these commands should
-produce some status output:</p>
-<pre>
-    __INSTALLDIR__/bin/BackupPC_serverMesg status info
+
+<pre><code>     __INSTALLDIR__/bin/BackupPC -d</code></pre>
+
+<p>as user __BACKUPPCUSER__. The -d option tells BackupPC to run as a daemon (ie: it does an additional fork).</p>
+
+<p>Any immediate errors will be printed to stderr and BackupPC will quit. Otherwise, look in __LOGDIR__/LOG and verify that BackupPC reports it has started and all is ok.</p>
+
+<h2 id="Step-7:-Talking-to-BackupPC">Step 7: Talking to BackupPC</h2>
+
+<p>You should verify that BackupPC is running by using BackupPC_serverMesg. This sends a message to BackupPC via the unix (or TCP) socket and prints the response. Like all BackupPC programs, BackupPC_serverMesg should be run as the BackupPC user (__BACKUPPCUSER__), so you should</p>
+
+<pre><code>    su __BACKUPPCUSER__</code></pre>
+
+<p>before running BackupPC_serverMesg. If the BackupPC user is configured with /bin/false as the shell, you can use the -s option to su to explicitly run a shell, eg:</p>
+
+<pre><code>    su -s /bin/bash __BACKUPPCUSER__</code></pre>
+
+<p>Depending upon your configuration you might also need the -l option.</p>
+
+<p>You can request status information and start and stop backups using this interface. This socket interface is mainly provided for the CGI interface (and some of the BackupPC sub-programs use it too). But right now we just want to make sure BackupPC is happy. Each of these commands should produce some status output:</p>
+
+<pre><code>    __INSTALLDIR__/bin/BackupPC_serverMesg status info
     __INSTALLDIR__/bin/BackupPC_serverMesg status jobs
-    __INSTALLDIR__/bin/BackupPC_serverMesg status hosts</pre>
-<p>The output should be some hashes printed with Data::Dumper.  If it
-looks cryptic and confusing, and doesn't look like an error message,
-then all is ok.</p>
-<p>The jobs status should initially show just BackupPC_trashClean.
-The hosts status should produce a list of every host you have listed
-in __CONFDIR__/hosts as part of a big cryptic output line.</p>
+    __INSTALLDIR__/bin/BackupPC_serverMesg status hosts</code></pre>
+
+<p>The output should be some hashes printed with Data::Dumper. If it looks cryptic and confusing, and doesn&#39;t look like an error message, then all is ok.</p>
+
+<p>The jobs status should initially show just BackupPC_trashClean. The hosts status should produce a list of every host you have listed in __CONFDIR__/hosts as part of a big cryptic output line.</p>
+
 <p>You can also request that all hosts be queued:</p>
-<pre>
-    __INSTALLDIR__/bin/BackupPC_serverMesg backup all</pre>
-<p>At this point you should make sure the CGI interface works since
-it will be much easier to see what is going on.  That's our
-next subject.</p>
-<p>
-</p>
-<h2><a name="step_8__checking_email_delivery">Step 8: Checking email delivery</a></h2>
-<p>The script BackupPC_sendEmail sends status and error emails to
-the administrator and users.  It is usually run each night
-by BackupPC_nightly.</p>
-<p>To verify that it can run sendmail and deliver email correctly
-you should ask it to send a test email to you:</p>
-<pre>
-    su __BACKUPPCUSER__
-    __INSTALLDIR__/bin/BackupPC_sendEmail -u [e-mail]</pre>
-<p>BackupPC_sendEmail also takes a -c option that checks if BackupPC
-is running, and it sends an email to <a href="#_conf_emailadminusername_">$Conf{EMailAdminUserName}</a>
-if it is not.  That can be used as a keep-alive check by adding</p>
-<pre>
-    __INSTALLDIR__/bin/BackupPC_sendEmail -c</pre>
-<p>to __BACKUPPCUSER__'s cron.</p>
-<p>The -t option to BackupPC_sendEmail causes it to print the email
-message instead of invoking sendmail to deliver the message.</p>
-<p>
-</p>
-<h2><a name="step_9__cgi_interface">Step 9: CGI interface</a></h2>
-<p>The CGI interface script, BackupPC_Admin, is a powerful and flexible
-way to see and control what BackupPC is doing.  It is written for an
-Apache server.  If you don't have Apache, see <a href="http://www.apache.org">http://www.apache.org</a>.</p>
-<p>There are two options for setting up the CGI interface: standard
-mode and using mod_perl.  Mod_perl provides much higher performance
-(around 15x) and is the best choice if your Apache was built with
-mod_perl support.  To see if your apache was built with mod_perl
-run this command:</p>
-<pre>
-    httpd -l | egrep mod_perl</pre>
+
+<pre><code>    __INSTALLDIR__/bin/BackupPC_serverMesg backup all</code></pre>
+
+<p>At this point you should make sure the CGI interface works since it will be much easier to see what is going on. That&#39;s our next subject.</p>
+
+<h2 id="Step-8:-Checking-email-delivery">Step 8: Checking email delivery</h2>
+
+<p>The script BackupPC_sendEmail sends status and error emails to the administrator and users. It is usually run each night by BackupPC_nightly.</p>
+
+<p>To verify that it can run sendmail and deliver email correctly you should ask it to send a test email to you:</p>
+
+<pre><code>    su __BACKUPPCUSER__
+    __INSTALLDIR__/bin/BackupPC_sendEmail -u [e-mail]</code></pre>
+
+<p>BackupPC_sendEmail also takes a -c option that checks if BackupPC is running, and it sends an email to <a href="#_conf_emailadminusername_">$Conf{EMailAdminUserName}</a> if it is not. That can be used as a keep-alive check by adding</p>
+
+<pre><code>    __INSTALLDIR__/bin/BackupPC_sendEmail -c</code></pre>
+
+<p>to __BACKUPPCUSER__&#39;s cron.</p>
+
+<p>The -t option to BackupPC_sendEmail causes it to print the email message instead of invoking sendmail to deliver the message.</p>
+
+<h2 id="Step-9:-CGI-interface">Step 9: CGI interface</h2>
+
+<p>The CGI interface script, BackupPC_Admin, is a powerful and flexible way to see and control what BackupPC is doing. It is written for an Apache server. If you don&#39;t have Apache, see <a href="http://www.apache.org">http://www.apache.org</a>.</p>
+
+<p>There are two options for setting up the CGI interface: standard mode and using mod_perl. Mod_perl provides much higher performance (around 15x) and is the best choice if your Apache was built with mod_perl support. To see if your apache was built with mod_perl run this command:</p>
+
+<pre><code>    httpd -l | egrep mod_perl</code></pre>
+
 <p>If this prints mod_perl.c then your Apache supports mod_perl.</p>
-<p>Note: on some distributions (like Debian) the command is not ``httpd'',
-but ``apache'' or ``apache2''. Those distributions will generally also
-use ``apache'' for the Apache user account and configuration files.</p>
-<p>Using mod_perl with BackupPC_Admin requires a dedicated Apache
-to be run as the BackupPC user (__BACKUPPCUSER__).  This is
-because BackupPC_Admin needs permission to access various files
-in BackupPC's data directories.  In contrast, the standard
-installation (without mod_perl) solves this problem by having
-BackupPC_Admin installed as setuid to the BackupPC user, so that
-BackupPC_Admin runs as the BackupPC user.</p>
+
+<p>Note: on some distributions (like Debian) the command is not ``httpd&#39;&#39;, but ``apache&#39;&#39; or ``apache2&#39;&#39;. Those distributions will generally also use ``apache&#39;&#39; for the Apache user account and configuration files.</p>
+
+<p>Using mod_perl with BackupPC_Admin requires a dedicated Apache to be run as the BackupPC user (__BACKUPPCUSER__). This is because BackupPC_Admin needs permission to access various files in BackupPC&#39;s data directories. In contrast, the standard installation (without mod_perl) solves this problem by having BackupPC_Admin installed as setuid to the BackupPC user, so that BackupPC_Admin runs as the BackupPC user.</p>
+
 <p>Here are some specifics for each setup:</p>
+
 <dl>
-<dt><strong><a name="standard_setup" class="item">Standard Setup</a></strong></dt>
 
+<dt id="Standard-Setup">Standard Setup</dt>
 <dd>
-<p>The CGI interface should have been installed by the configure.pl script
-in __CGIDIR__/BackupPC_Admin.  BackupPC_Admin should have been installed
-as setuid to the BackupPC user (__BACKUPPCUSER__), in addition to user
-and group execute permission.</p>
-<p>You should be very careful about permissions on BackupPC_Admin and
-the directory __CGIDIR__: it is important that normal users cannot
-directly execute or change BackupPC_Admin, otherwise they can access
-backup files for any PC. You might need to change the group ownership
-of BackupPC_Admin to a group that Apache belongs to so that Apache
-can execute it (don't add &quot;other&quot; execute permission!).
-The permissions should look like this:</p>
-<pre>
-    ls -l __CGIDIR__/BackupPC_Admin
-    -swxr-x---    1 __BACKUPPCUSER__   web      82406 Jun 17 22:58 __CGIDIR__/BackupPC_Admin</pre>
-<p>The setuid script won't work unless perl on your machine was installed
-with setuid emulation.  This is likely the problem if you get an error
-saying such as &quot;Wrong user: my userid is 25, instead of 150&quot;, meaning
-the script is running as the httpd user, not the BackupPC user.
-This is because setuid scripts are disabled by the kernel in most
-flavors of unix and linux.</p>
-<p>To see if your perl has setuid emulation, see if there is a program
-called sperl5.8.0 (or sperl5.8.2 etc, based on your perl version)
-in the place where perl is installed. If you can't find this program,
-then you have two options: rebuild and reinstall perl with the setuid
-emulation turned on (answer &quot;y&quot; to the question &quot;Do you want to do
-setuid/setgid emulation?&quot; when you run perl's configure script), or
-switch to the mod_perl alternative for the CGI script (which doesn't
-need setuid to work).</p>
+
+<p>The CGI interface should have been installed by the configure.pl script in __CGIDIR__/BackupPC_Admin. BackupPC_Admin should have been installed as setuid to the BackupPC user (__BACKUPPCUSER__), in addition to user and group execute permission.</p>
+
+<p>You should be very careful about permissions on BackupPC_Admin and the directory __CGIDIR__: it is important that normal users cannot directly execute or change BackupPC_Admin, otherwise they can access backup files for any PC. You might need to change the group ownership of BackupPC_Admin to a group that Apache belongs to so that Apache can execute it (don&#39;t add &quot;other&quot; execute permission!). The permissions should look like this:</p>
+
+<pre><code>    ls -l __CGIDIR__/BackupPC_Admin
+    -swxr-x---    1 __BACKUPPCUSER__   web      82406 Jun 17 22:58 __CGIDIR__/BackupPC_Admin</code></pre>
+
+<p>The setuid script won&#39;t work unless perl on your machine was installed with setuid emulation. This is likely the problem if you get an error saying such as &quot;Wrong user: my userid is 25, instead of 150&quot;, meaning the script is running as the httpd user, not the BackupPC user. This is because setuid scripts are disabled by the kernel in most flavors of unix and linux.</p>
+
+<p>To see if your perl has setuid emulation, see if there is a program called sperl5.8.0 (or sperl5.8.2 etc, based on your perl version) in the place where perl is installed. If you can&#39;t find this program, then you have two options: rebuild and reinstall perl with the setuid emulation turned on (answer &quot;y&quot; to the question &quot;Do you want to do setuid/setgid emulation?&quot; when you run perl&#39;s configure script), or switch to the mod_perl alternative for the CGI script (which doesn&#39;t need setuid to work).</p>
+
 </dd>
-<dt><strong><a name="mod_perl_setup" class="item">Mod_perl Setup</a></strong></dt>
-
+<dt id="Mod_perl-Setup">Mod_perl Setup</dt>
 <dd>
-<p>The advantage of the mod_perl setup is that no setuid script is needed,
-and there is a huge performance advantage.  Not only does all the perl
-code need to be parsed just once, the config.pl and hosts files, plus
-the connection to the BackupPC server are cached between requests.  The
-typical speedup is around 15 times.</p>
-<p>To use mod_perl you need to run Apache as user __BACKUPPCUSER__.
-If you need to run multiple Apache's for different services then
-you need to create multiple top-level Apache directories, each
-with their own config file.  You can make copies of /etc/init.d/httpd
-and use the -d option to httpd to point each http to a different
-top-level directory.  Or you can use the -f option to explicitly
-point to the config file.  Multiple Apache's will run on different
-Ports (eg: 80 is standard, 8080 is a typical alternative port accessed
-via <a href="http://yourhost.com:8080).">http://yourhost.com:8080).</a></p>
-<p>Inside BackupPC's Apache http.conf file you should check the
-settings for ServerRoot, DocumentRoot, User, Group, and Port.  See 
-<a href="http://httpd.apache.org/docs/server-wide.html">http://httpd.apache.org/docs/server-wide.html</a> for more details.</p>
-<p>For mod_perl, BackupPC_Admin should not have setuid permission, so
-you should turn it off:</p>
-<pre>
-    chmod u-s __CGIDIR__/BackupPC_Admin</pre>
-<p>To tell Apache to use mod_perl to execute BackupPC_Admin, add this
-to Apache's 1.x httpd.conf file:</p>
-<pre>
-    &lt;IfModule mod_perl.c&gt;
+
+<p>The advantage of the mod_perl setup is that no setuid script is needed, and there is a huge performance advantage. Not only does all the perl code need to be parsed just once, the config.pl and hosts files, plus the connection to the BackupPC server are cached between requests. The typical speedup is around 15 times.</p>
+
+<p>To use mod_perl you need to run Apache as user __BACKUPPCUSER__. If you need to run multiple Apache&#39;s for different services then you need to create multiple top-level Apache directories, each with their own config file. You can make copies of /etc/init.d/httpd and use the -d option to httpd to point each http to a different top-level directory. Or you can use the -f option to explicitly point to the config file. Multiple Apache&#39;s will run on different Ports (eg: 80 is standard, 8080 is a typical alternative port accessed via http://yourhost.com:8080).</p>
+
+<p>Inside BackupPC&#39;s Apache http.conf file you should check the settings for ServerRoot, DocumentRoot, User, Group, and Port. See <a href="http://httpd.apache.org/docs/server-wide.html">http://httpd.apache.org/docs/server-wide.html</a> for more details.</p>
+
+<p>For mod_perl, BackupPC_Admin should not have setuid permission, so you should turn it off:</p>
+
+<pre><code>    chmod u-s __CGIDIR__/BackupPC_Admin</code></pre>
+
+<p>To tell Apache to use mod_perl to execute BackupPC_Admin, add this to Apache&#39;s 1.x httpd.conf file:</p>
+
+<pre><code>    &lt;IfModule mod_perl.c&gt;
         PerlModule Apache::Registry
         PerlTaintCheck On
         &lt;Location /cgi-bin/BackupPC/BackupPC_Admin&gt;   # &lt;--- change path as needed
@@ -1273,13 +860,13 @@
            Options ExecCGI
            PerlSendHeader On
         &lt;/Location&gt;
-    &lt;/IfModule&gt;</pre>
-<p>Apache 2.0.44 with Perl 5.8.0 on RedHat 7.1, Don Silvia reports that
-this works (with tweaks from Michael Tuzi):</p>
-<pre>
-    LoadModule perl_module modules/mod_perl.so
-    PerlModule Apache2</pre>
-<pre>
+    &lt;/IfModule&gt;</code></pre>
+
+<p>Apache 2.0.44 with Perl 5.8.0 on RedHat 7.1, Don Silvia reports that this works (with tweaks from Michael Tuzi):</p>
+
+<pre><code>    LoadModule perl_module modules/mod_perl.so
+    PerlModule Apache2
+
     &lt;Directory /path/to/cgi/&gt;
         SetHandler perl-script
         PerlResponseHandler ModPerl::Registry
@@ -1292,34 +879,28 @@
         AuthType Basic
         AuthUserFile /path/to/user_file
         Require valid-user
-    &lt;/Directory&gt;</pre>
-<p>There are other optimizations and options with mod_perl.  For
-example, you can tell mod_perl to preload various perl modules,
-which saves memory compared to loading separate copies in every
-Apache process after they are forked.  See Stas's definitive
-mod_perl guide at <a href="http://perl.apache.org/guide">http://perl.apache.org/guide</a>.</p>
+    &lt;/Directory&gt;</code></pre>
+
+<p>There are other optimizations and options with mod_perl. For example, you can tell mod_perl to preload various perl modules, which saves memory compared to loading separate copies in every Apache process after they are forked. See Stas&#39;s definitive mod_perl guide at <a href="http://perl.apache.org/guide">http://perl.apache.org/guide</a>.</p>
+
 </dd>
 </dl>
-<p>BackupPC_Admin requires that users are authenticated by Apache.
-Specifically, it expects that Apache sets the REMOTE_USER environment
-variable when it runs.  There are several ways to do this.  One way
-is to create a .htaccess file in the cgi-bin directory that looks like:</p>
-<pre>
-    AuthGroupFile /etc/httpd/conf/group    # &lt;--- change path as needed
+
+<p>BackupPC_Admin requires that users are authenticated by Apache. Specifically, it expects that Apache sets the REMOTE_USER environment variable when it runs. There are several ways to do this. One way is to create a .htaccess file in the cgi-bin directory that looks like:</p>
+
+<pre><code>    AuthGroupFile /etc/httpd/conf/group    # &lt;--- change path as needed
     AuthUserFile /etc/http/conf/passwd     # &lt;--- change path as needed
     AuthType basic
     AuthName &quot;access&quot;
-    require valid-user</pre>
-<p>You will also need &quot;AllowOverride Indexes AuthConfig&quot; in the Apache
-httpd.conf file to enable the .htaccess file. Alternatively, everything
-can go in the Apache httpd.conf file inside a Location directive. The
-list of users and password file above can be extracted from the NIS
-passwd file.</p>
-<p>One alternative is to use LDAP.  In Apache's http.conf add these lines:</p>
-<pre>
-    LoadModule auth_ldap_module   modules/auth_ldap.so
-    AddModule auth_ldap.c</pre>
-<pre>
+    require valid-user</code></pre>
+
+<p>You will also need &quot;AllowOverride Indexes AuthConfig&quot; in the Apache httpd.conf file to enable the .htaccess file. Alternatively, everything can go in the Apache httpd.conf file inside a Location directive. The list of users and password file above can be extracted from the NIS passwd file.</p>
+
+<p>One alternative is to use LDAP. In Apache&#39;s http.conf add these lines:</p>
+
+<pre><code>    LoadModule auth_ldap_module   modules/auth_ldap.so
+    AddModule auth_ldap.c
+
     # cgi-bin - auth via LDAP (for BackupPC)
     &lt;Location /cgi-binBackupPC/BackupPC_Admin&gt;    # &lt;--- change path as needed
       AuthType Basic
@@ -1327,297 +908,220 @@
       # replace MYDOMAIN, PORT, ORG and CO as needed
       AuthLDAPURL ldap://ldap.MYDOMAIN.com:PORT/o=ORG,c=CO?uid?sub?(objectClass=*)
       require valid-user
-    &lt;/Location&gt;</pre>
-<p>If you want to disable the user authentication you can set
-<a href="#_conf_cgiadminusers_">$Conf{CgiAdminUsers}</a> to '*', which allows any user to have
-full access to all hosts and backups.  In this case the REMOTE_USER
-environment variable does not have to be set by Apache.</p>
-<p>Alternatively, you can force a particular user name by getting Apache
-to set REMOTE_USER, eg, to hardcode the user to www you could add
-this to Apache's httpd.conf:</p>
-<pre>
-    &lt;Location /cgi-bin/BackupPC/BackupPC_Admin&gt;   # &lt;--- change path as needed
+    &lt;/Location&gt;</code></pre>
+
+<p>If you want to disable the user authentication you can set <a href="#_conf_cgiadminusers_">$Conf{CgiAdminUsers}</a> to &#39;*&#39;, which allows any user to have full access to all hosts and backups. In this case the REMOTE_USER environment variable does not have to be set by Apache.</p>
+
+<p>Alternatively, you can force a particular user name by getting Apache to set REMOTE_USER, eg, to hardcode the user to www you could add this to Apache&#39;s httpd.conf:</p>
+
+<pre><code>    &lt;Location /cgi-bin/BackupPC/BackupPC_Admin&gt;   # &lt;--- change path as needed
         Setenv REMOTE_USER www
-    &lt;/Location&gt;</pre>
-<p>Finally, you should also edit the config.pl file and adjust, as necessary,
-the CGI-specific settings.  They're near the end of the config file. In
-particular, you should specify which users or groups have administrator
-(privileged) access: see the config settings <a href="#_conf_cgiadminusergroup_">$Conf{CgiAdminUserGroup}</a>
-and <a href="#_conf_cgiadminusers_">$Conf{CgiAdminUsers}</a>.  Also, the configure.pl script placed various
-images into <a href="#_conf_cgiimagedir_">$Conf{CgiImageDir}</a> that BackupPC_Admin needs to serve
-up.  You should make sure that <a href="#_conf_cgiimagedirurl_">$Conf{CgiImageDirURL}</a> is the correct
-URL for the image directory.</p>
-<p>See the section <a href="#fixing_installation_problems">Fixing installation problems</a> for suggestions on debugging the Apache authentication setup.</p>
-<p>
-</p>
-<h2><a name="how_backuppc_finds_hosts">How BackupPC Finds Hosts</a></h2>
-<p>Starting with v2.0.0 the way hosts are discovered has changed.  In most
-cases you should specify 0 for the DHCP flag in the conf/hosts file,
-even if the host has a dynamically assigned IP address.</p>
+    &lt;/Location&gt;</code></pre>
+
+<p>Finally, you should also edit the config.pl file and adjust, as necessary, the CGI-specific settings. They&#39;re near the end of the config file. In particular, you should specify which users or groups have administrator (privileged) access: see the config settings <a href="#_conf_cgiadminusergroup_">$Conf{CgiAdminUserGroup}</a> and <a href="#_conf_cgiadminusers_">$Conf{CgiAdminUsers}</a>. Also, the configure.pl script placed various images into <a href="#_conf_cgiimagedir_">$Conf{CgiImageDir}</a> that BackupPC_Admin needs to serve up. You should make sure that <a href="#_conf_cgiimagedirurl_">$Conf{CgiImageDirURL}</a> is the correct URL for the image directory.</p>
+
+<p>See the section <a href="#Fixing-installation-problems">&quot;Fixing installation problems&quot;</a> for suggestions on debugging the Apache authentication setup.</p>
+
+<h2 id="How-BackupPC-Finds-Hosts">How BackupPC Finds Hosts</h2>
+
+<p>Starting with v2.0.0 the way hosts are discovered has changed. In most cases you should specify 0 for the DHCP flag in the conf/hosts file, even if the host has a dynamically assigned IP address.</p>
+
 <p>BackupPC (starting with v2.0.0) looks up hosts with DHCP = 0 in this manner:</p>
+
 <ul>
-<li>
-<p>First DNS is used to lookup the IP address given the client's name
-using perl's <code>gethostbyname()</code> function.  This should succeed for machines
-that have fixed IP addresses that are known via DNS.  You can manually
-see whether a given host have a DNS entry according to perl's
-gethostbyname function with this command:</p>
-<pre>
-    perl -e 'print(gethostbyname(&quot;myhost&quot;) ? &quot;ok\n&quot; : &quot;not found\n&quot;);'</pre>
+
+<li><p>First DNS is used to lookup the IP address given the client&#39;s name using perl&#39;s gethostbyname() function. This should succeed for machines that have fixed IP addresses that are known via DNS. You can manually see whether a given host have a DNS entry according to perl&#39;s gethostbyname function with this command:</p>
+
+<pre><code>    perl -e &#39;print(gethostbyname(&quot;myhost&quot;) ? &quot;ok\n&quot; : &quot;not found\n&quot;);&#39;</code></pre>
+
 </li>
-<li>
-<p>If <code>gethostbyname()</code> fails, BackupPC then attempts a NetBios multicast to
-find the host.  Provided your client machine is configured properly,
-it should respond to this NetBios multicast request.  Specifically,
-BackupPC runs a command of this form:</p>
-<pre>
-    nmblookup myhost</pre>
+<li><p>If gethostbyname() fails, BackupPC then attempts a NetBios multicast to find the host. Provided your client machine is configured properly, it should respond to this NetBios multicast request. Specifically, BackupPC runs a command of this form:</p>
+
+<pre><code>    nmblookup myhost</code></pre>
+
 <p>If this fails you will see output like:</p>
-<pre>
-    querying myhost on 10.10.255.255
-    name_query failed to find name myhost</pre>
+
+<pre><code>    querying myhost on 10.10.255.255
+    name_query failed to find name myhost</code></pre>
+
 <p>If it is successful you will see output like:</p>
-<pre>
-    querying myhost on 10.10.255.255
-    10.10.1.73 myhost&lt;00&gt;</pre>
-<p>Depending on your netmask you might need to specify the -B option to
-nmblookup.  For example:</p>
-<pre>
-    nmblookup -B 10.10.1.255 myhost</pre>
-<p>If necessary, experiment with the nmblookup command which will return the
-IP address of the client given its name.  Then update
-<a href="#_conf_nmblookupfindhostcmd_">$Conf{NmbLookupFindHostCmd}</a> with any necessary options to nmblookup.</p>
+
+<pre><code>    querying myhost on 10.10.255.255
+    10.10.1.73 myhost&lt;00&gt;</code></pre>
+
+<p>Depending on your netmask you might need to specify the -B option to nmblookup. For example:</p>
+
+<pre><code>    nmblookup -B 10.10.1.255 myhost</code></pre>
+
+<p>If necessary, experiment with the nmblookup command which will return the IP address of the client given its name. Then update <a href="#_conf_nmblookupfindhostcmd_">$Conf{NmbLookupFindHostCmd}</a> with any necessary options to nmblookup.</p>
+
 </li>
 </ul>
-<p>For hosts that have the DHCP flag set to 1, these machines are
-discovered as follows:</p>
+
+<p>For hosts that have the DHCP flag set to 1, these machines are discovered as follows:</p>
+
 <ul>
-<li>
-<p>A DHCP address pool (<a href="#_conf_dhcpaddressranges_">$Conf{DHCPAddressRanges}</a>) needs to be specified.
-BackupPC will check the NetBIOS name of each machine in the range using
-a command of the form:</p>
-<pre>
-    nmblookup -A W.X.Y.Z</pre>
-<p>where W.X.Y.Z is each candidate address from <a href="#_conf_dhcpaddressranges_">$Conf{DHCPAddressRanges}</a>.
-Any host that has a valid NetBIOS name returned by this command (ie:
-matching an entry in the hosts file) will be backed up.  You can
-modify the specific nmblookup command if necessary via <a href="#_conf_nmblookupcmd_">$Conf{NmbLookupCmd}</a>.</p>
+
+<li><p>A DHCP address pool (<a href="#_conf_dhcpaddressranges_">$Conf{DHCPAddressRanges}</a>) needs to be specified. BackupPC will check the NetBIOS name of each machine in the range using a command of the form:</p>
+
+<pre><code>    nmblookup -A W.X.Y.Z</code></pre>
+
+<p>where W.X.Y.Z is each candidate address from <a href="#_conf_dhcpaddressranges_">$Conf{DHCPAddressRanges}</a>. Any host that has a valid NetBIOS name returned by this command (ie: matching an entry in the hosts file) will be backed up. You can modify the specific nmblookup command if necessary via <a href="#_conf_nmblookupcmd_">$Conf{NmbLookupCmd}</a>.</p>
+
 </li>
-<li>
-<p>You only need to use this DHCP feature if your client machine doesn't
-respond to the NetBios multicast request:</p>
-<pre>
-    nmblookup myHost</pre>
+<li><p>You only need to use this DHCP feature if your client machine doesn&#39;t respond to the NetBios multicast request:</p>
+
+<pre><code>    nmblookup myHost</code></pre>
+
 <p>but does respond to a request directed to its IP address:</p>
-<pre>
-    nmblookup -A W.X.Y.Z</pre>
+
+<pre><code>    nmblookup -A W.X.Y.Z</code></pre>
+
 </li>
 </ul>
-<p>
-</p>
-<h2><a name="other_installation_topics">Other installation topics</a></h2>
+
+<h2 id="Other-installation-topics">Other installation topics</h2>
+
 <dl>
-<dt><strong><a name="removing_a_client" class="item">Removing a client</a></strong></dt>
 
+<dt id="Removing-a-client">Removing a client</dt>
 <dd>
-<p>If there is a machine that no longer needs to be backed up (eg: a retired
-machine) you have two choices.  First, you can keep the backups accessible
-and browsable, but disable all new backups.  Alternatively, you can
-completely remove the client and all its backups.</p>
-<p>To disable backups for a client <a href="#_conf_backupsdisable_">$Conf{BackupsDisable}</a> can be
-set to two different values in that client's per-PC config.pl file:</p>
+
+<p>If there is a machine that no longer needs to be backed up (eg: a retired machine) you have two choices. First, you can keep the backups accessible and browsable, but disable all new backups. Alternatively, you can completely remove the client and all its backups.</p>
+
+<p>To disable backups for a client <a href="#_conf_backupsdisable_">$Conf{BackupsDisable}</a> can be set to two different values in that client&#39;s per-PC config.pl file:</p>
+
 <ol>
-<li>
-<p>Don't do any regular backups on this machine.  Manually
-requested backups (via the CGI interface) will still occur.</p>
+
+<li><p>Don&#39;t do any regular backups on this machine. Manually requested backups (via the CGI interface) will still occur.</p>
+
 </li>
-<li>
-<p>Don't do any backups on this machine.  Manually requested
-backups (via the CGI interface) will be ignored.</p>
+<li><p>Don&#39;t do any backups on this machine. Manually requested backups (via the CGI interface) will be ignored.</p>
+
 </li>
 </ol>
-<p>This will still allow the client's old backups to be browsable
-and restorable.</p>
-<p>To completely remove a client and all its backups, you should remove its
-entry in the conf/hosts file, and then delete the __TOPDIR__/pc/$host
-directory.  Whenever you change the hosts file, you should send
-BackupPC a HUP (-1) signal so that it re-reads the hosts file.
-If you don't do this, BackupPC will automatically re-read the
-hosts file at the next regular wakeup.</p>
-<p>Note that when you remove a client's backups you won't initially
-recover much disk space.  That's because the client's files are
-still in the pool.  Overnight, when BackupPC_nightly next runs,
-all the unused pool files will be deleted and this will recover
-the disk space used by the client's backups.</p>
+
+<p>This will still allow the client&#39;s old backups to be browsable and restorable.</p>
+
+<p>To completely remove a client and all its backups, you should remove its entry in the conf/hosts file, and then delete the __TOPDIR__/pc/$host directory. Whenever you change the hosts file, you should send BackupPC a HUP (-1) signal so that it re-reads the hosts file. If you don&#39;t do this, BackupPC will automatically re-read the hosts file at the next regular wakeup.</p>
+
+<p>Note that when you remove a client&#39;s backups you won&#39;t initially recover much disk space. That&#39;s because the client&#39;s files are still in the pool. Overnight, when BackupPC_nightly next runs, all the unused pool files will be deleted and this will recover the disk space used by the client&#39;s backups.</p>
+
 </dd>
-<dt><strong><a name="copying_the_pool" class="item">Copying the pool</a></strong></dt>
-
+<dt id="Copying-the-pool">Copying the pool</dt>
 <dd>
-<p>If the pool disk requirements grow you might need to copy the entire
-data directory to a new (bigger) file system.  Hopefully you are lucky
-enough to avoid this by having the data directory on a RAID file system
-or LVM that allows the capacity to be grown in place by adding disks.</p>
-<p>The backup data directories contain large numbers of hardlinks.  If
-you try to copy the pool the target directory will occupy a lot more
-space if the hardlinks aren't re-established.</p>
-<p>The best way to copy a pool file system, if possible, is by copying
-the raw device at the block level (eg: using dd).  Application level
-programs that understand hardlinks include the GNU cp program with
-the -a option and rsync -H.  However, the large number of hardlinks
-in the pool will make the memory usage large and the copy very slow.
-Don't forget to stop BackupPC while the copy runs.</p>
-<p>Starting in 3.0.0 a new script bin/BackupPC_tarPCCopy can be
-used to assist the copy process.  Given one or more pc paths
-(eg: TOPDIR/pc/HOST or TOPDIR/pc/HOST/nnn), BackupPC_tarPCCopy 
-creates a tar archive with all the hardlinks pointing to ../cpool/....
-Any files not hardlinked (eg: backups, LOG etc) are included
-verbatim.</p>
-<p>You will need to specify the -P option to tar when you extract
-the archive generated by BackupPC_tarPCCopy since the hardlink
-targets are outside of the directory being extracted.</p>
-<p>To copy a complete store (ie: __TOPDIR__) using BackupPC_tarPCCopy
-you should:</p>
+
+<p>If the pool disk requirements grow you might need to copy the entire data directory to a new (bigger) file system. Hopefully you are lucky enough to avoid this by having the data directory on a RAID file system or LVM that allows the capacity to be grown in place by adding disks.</p>
+
+<p>The backup data directories contain large numbers of hardlinks. If you try to copy the pool the target directory will occupy a lot more space if the hardlinks aren&#39;t re-established.</p>
+
+<p>The best way to copy a pool file system, if possible, is by copying the raw device at the block level (eg: using dd). Application level programs that understand hardlinks include the GNU cp program with the -a option and rsync -H. However, the large number of hardlinks in the pool will make the memory usage large and the copy very slow. Don&#39;t forget to stop BackupPC while the copy runs.</p>
+
+<p>Starting in 3.0.0 a new script bin/BackupPC_tarPCCopy can be used to assist the copy process. Given one or more pc paths (eg: TOPDIR/pc/HOST or TOPDIR/pc/HOST/nnn), BackupPC_tarPCCopy creates a tar archive with all the hardlinks pointing to ../cpool/.... Any files not hardlinked (eg: backups, LOG etc) are included verbatim.</p>
+
+<p>You will need to specify the -P option to tar when you extract the archive generated by BackupPC_tarPCCopy since the hardlink targets are outside of the directory being extracted.</p>
+
+<p>To copy a complete store (ie: __TOPDIR__) using BackupPC_tarPCCopy you should:</p>
+
 <ul>
-<li>
-<p>stop BackupPC so that the store is static.</p>
-</li>
-<li>
-<p>copy the cpool, conf and log directory trees using any technique
-(like cp, rsync or tar) without the need to preserve hardlinks.</p>
-</li>
-<li>
-<p>copy the pc directory using BackupPC_tarPCCopy:</p>
-<pre>
-    su __BACKUPPCUSER__
+
+<li><p>stop BackupPC so that the store is static.</p>
+
+</li>
+<li><p>copy the cpool, conf and log directory trees using any technique (like cp, rsync or tar) without the need to preserve hardlinks.</p>
+
+</li>
+<li><p>copy the pc directory using BackupPC_tarPCCopy:</p>
+
+<pre><code>    su __BACKUPPCUSER__
     cd NEW_TOPDIR
     mkdir pc
     cd pc
-    __INSTALLDIR__/bin/BackupPC_tarPCCopy __TOPDIR__/pc | tar xvPf -</pre>
+    __INSTALLDIR__/bin/BackupPC_tarPCCopy __TOPDIR__/pc | tar xvPf -</code></pre>
+
 </li>
 </ul>
+
 </dd>
 </dl>
-<p>
-</p>
-<h2><a name="fixing_installation_problems">Fixing installation problems</a></h2>
-<p>Please see the Wiki at <a href="http://backuppc.wiki.sourceforge.net">http://backuppc.wiki.sourceforge.net</a> for
-debugging suggestions.  If you find a solution to your problem that
-could help other users please add it to the Wiki!</p>
-<p>
-<a href="#__index__"><small>Back to Top</small></a>
-</p>
+
+<h2 id="Fixing-installation-problems">Fixing installation problems</h2>
+
+<p>Please see the Wiki at <a href="http://backuppc.wiki.sourceforge.net">http://backuppc.wiki.sourceforge.net</a> for debugging suggestions. If you find a solution to your problem that could help other users please add it to the Wiki!</p>
+
 <hr />
-<h1><a name="restore_functions">Restore functions</a></h1>
-<p>BackupPC supports several different methods for restoring files. The
-most convenient restore options are provided via the CGI interface.
-Alternatively, backup files can be restored using manual commands.</p>
-<p>
-</p>
-<h2><a name="cgi_restore_options">CGI restore options</a></h2>
-<p>By selecting a host in the CGI interface, a list of all the backups
-for that machine will be displayed.  By selecting the backup number
-you can navigate the shares and directory tree for that backup.</p>
-<p>BackupPC's CGI interface automatically fills incremental backups
-with the corresponding full backup, which means each backup has
-a filled appearance.  Therefore, there is no need to do multiple
-restores from the incremental and full backups: BackupPC does all
-the hard work for you.  You simply select the files and directories
-you want from the correct backup vintage in one step.</p>
-<p>You can download a single backup file at any time simply by selecting
-it.  Your browser should prompt you with the file name and ask you
-whether to open the file or save it to disk.</p>
-<p>Alternatively, you can select one or more files or directories in
-the currently selected directory and select &quot;Restore selected files&quot;.
-(If you need to restore selected files and directories from several
-different parent directories you will need to do that in multiple
-steps.)</p>
-<p>If you select all the files in a directory, BackupPC will replace
-the list of files with the parent directory.  You will be presented
-with a screen that has three options:</p>
+<h1 id="Restore-functions">Restore functions</h1>
+
+<p>BackupPC supports several different methods for restoring files. The most convenient restore options are provided via the CGI interface. Alternatively, backup files can be restored using manual commands.</p>
+
+<h2 id="CGI-restore-options">CGI restore options</h2>
+
+<p>By selecting a host in the CGI interface, a list of all the backups for that machine will be displayed. By selecting the backup number you can navigate the shares and directory tree for that backup.</p>
+
+<p>BackupPC&#39;s CGI interface automatically fills incremental backups with the corresponding full backup, which means each backup has a filled appearance. Therefore, there is no need to do multiple restores from the incremental and full backups: BackupPC does all the hard work for you. You simply select the files and directories you want from the correct backup vintage in one step.</p>
+
+<p>You can download a single backup file at any time simply by selecting it. Your browser should prompt you with the file name and ask you whether to open the file or save it to disk.</p>
+
+<p>Alternatively, you can select one or more files or directories in the currently selected directory and select &quot;Restore selected files&quot;. (If you need to restore selected files and directories from several different parent directories you will need to do that in multiple steps.)</p>
+
+<p>If you select all the files in a directory, BackupPC will replace the list of files with the parent directory. You will be presented with a screen that has three options:</p>
+
 <dl>
-<dt><strong><a name="option_1_direct_restore" class="item">Option 1: Direct Restore</a></strong></dt>
-
-<dd>
-<p>With this option the selected files and directories are restored
-directly back onto the host, by default in their original location.
-Any old files with the same name will be overwritten, so use caution.
-You can optionally change the target host name, target share name,
-and target path prefix for the restore, allowing you to restore the
-files to a different location.</p>
-<p>Once you select &quot;Start Restore&quot; you will be prompted one last time
-with a summary of the exact source and target files and directories
-before you commit.  When you give the final go ahead the restore
-operation will be queued like a normal backup job, meaning that it
-will be deferred if there is a backup currently running for that host.
-When the restore job is run, smbclient, tar, rsync or rsyncd is used
-(depending upon <a href="#_conf_xfermethod_">$Conf{XferMethod}</a>) to actually restore the files.
-Sorry, there is currently no option to cancel a restore that has been
-started.  Currently ftp restores are not fully implemented.</p>
-<p>A record of the restore request, including the result and list of
-files and directories, is kept.  It can be browsed from the host's
-home page.  <a href="#_conf_restoreinfokeepcnt_">$Conf{RestoreInfoKeepCnt}</a> specifies how many old restore
-status files to keep.</p>
-<p>Note that for direct restore to work, the <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> must
-be able to write to the client.  For example, that means an SMB
-share for smbclient needs to be writable, and the rsyncd module
-needs &quot;read only&quot; set to &quot;false&quot;.  This creates additional security
-risks.  If you only create read-only SMB shares (which is a good
-idea), then the direct restore will fail.  You can disable the
-direct restore option by setting <a href="#_conf_smbclientrestorecmd_">$Conf{SmbClientRestoreCmd}</a>,
-<a href="#_conf_tarclientrestorecmd_">$Conf{TarClientRestoreCmd}</a> and <a href="#_conf_rsyncrestoreargs_">$Conf{RsyncRestoreArgs}</a> to undef.</p>
-</dd>
-<dt><strong><a name="option_2_download_zip_archive" class="item">Option 2: Download Zip archive</a></strong></dt>
-
-<dd>
-<p>With this option a zip file containing the selected files and directories
-is downloaded.  The zip file can then be unpacked or individual files
-extracted as necessary on the host machine. The compression level can be
-specified.  A value of 0 turns off compression.</p>
-<p>When you select &quot;Download Zip File&quot; you should be prompted where to
-save the restore.zip file.</p>
-<p>BackupPC does not consider downloading a zip file as an actual
-restore operation, so the details are not saved for later browsing
-as in the first case.  However, a mention that a zip file was
-downloaded by a particular user, and a list of the files, does
-appear in BackupPC's log file.</p>
-</dd>
-<dt><strong><a name="option_3_download_tar_archive" class="item">Option 3: Download Tar archive</a></strong></dt>
-
-<dd>
-<p>This is identical to the previous option, except a tar file is downloaded
-rather than a zip file (and there is currently no compression option).</p>
+
+<dt id="Option-1:-Direct-Restore">Option 1: Direct Restore</dt>
+<dd>
+
+<p>With this option the selected files and directories are restored directly back onto the host, by default in their original location. Any old files with the same name will be overwritten, so use caution. You can optionally change the target host name, target share name, and target path prefix for the restore, allowing you to restore the files to a different location.</p>
+
+<p>Once you select &quot;Start Restore&quot; you will be prompted one last time with a summary of the exact source and target files and directories before you commit. When you give the final go ahead the restore operation will be queued like a normal backup job, meaning that it will be deferred if there is a backup currently running for that host. When the restore job is run, smbclient, tar, rsync or rsyncd is used (depending upon <a href="#_conf_xfermethod_">$Conf{XferMethod}</a>) to actually restore the files. Sorry, there is currently no option to cancel a restore that has been started. Currently ftp restores are not fully implemented.</p>
+
+<p>A record of the restore request, including the result and list of files and directories, is kept. It can be browsed from the host&#39;s home page. <a href="#_conf_restoreinfokeepcnt_">$Conf{RestoreInfoKeepCnt}</a> specifies how many old restore status files to keep.</p>
+
+<p>Note that for direct restore to work, the <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> must be able to write to the client. For example, that means an SMB share for smbclient needs to be writable, and the rsyncd module needs &quot;read only&quot; set to &quot;false&quot;. This creates additional security risks. If you only create read-only SMB shares (which is a good idea), then the direct restore will fail. You can disable the direct restore option by setting <a href="#_conf_smbclientrestorecmd_">$Conf{SmbClientRestoreCmd}</a>, <a href="#_conf_tarclientrestorecmd_">$Conf{TarClientRestoreCmd}</a> and <a href="#_conf_rsyncrestoreargs_">$Conf{RsyncRestoreArgs}</a> to undef.</p>
+
+</dd>
+<dt id="Option-2:-Download-Zip-archive">Option 2: Download Zip archive</dt>
+<dd>
+
+<p>With this option a zip file containing the selected files and directories is downloaded. The zip file can then be unpacked or individual files extracted as necessary on the host machine. The compression level can be specified. A value of 0 turns off compression.</p>
+
+<p>When you select &quot;Download Zip File&quot; you should be prompted where to save the restore.zip file.</p>
+
+<p>BackupPC does not consider downloading a zip file as an actual restore operation, so the details are not saved for later browsing as in the first case. However, a mention that a zip file was downloaded by a particular user, and a list of the files, does appear in BackupPC&#39;s log file.</p>
+
+</dd>
+<dt id="Option-3:-Download-Tar-archive">Option 3: Download Tar archive</dt>
+<dd>
+
+<p>This is identical to the previous option, except a tar file is downloaded rather than a zip file (and there is currently no compression option).</p>
+
 </dd>
 </dl>
-<p>
-</p>
-<h2><a name="command_line_restore_options">Command-line restore options</a></h2>
-<p>Apart from the CGI interface, BackupPC allows you to restore files
-and directories from the command line.  The following programs can
-be used:</p>
+
+<h2 id="Command-line-restore-options">Command-line restore options</h2>
+
+<p>Apart from the CGI interface, BackupPC allows you to restore files and directories from the command line. The following programs can be used:</p>
+
 <dl>
-<dt><strong><a name="backuppc_zcat" class="item">BackupPC_zcat</a></strong></dt>
 
+<dt id="BackupPC_zcat">BackupPC_zcat</dt>
 <dd>
-<p>For each file name argument it inflates (uncompresses) the file and
-writes it to stdout.  To use BackupPC_zcat you could give it the
-full file name, eg:</p>
-<pre>
-    __INSTALLDIR__/bin/BackupPC_zcat __TOPDIR__/pc/host/5/fc/fcraig/fexample.txt &gt; example.txt</pre>
-<p>It's your responsibility to make sure the file is really compressed:
-BackupPC_zcat doesn't check which backup the requested file is from.
-BackupPC_zcat returns a non-zero status if it fails to uncompress
-a file.</p>
+
+<p>For each file name argument it inflates (uncompresses) the file and writes it to stdout. To use BackupPC_zcat you could give it the full file name, eg:</p>
+
+<pre><code>    __INSTALLDIR__/bin/BackupPC_zcat __TOPDIR__/pc/host/5/fc/fcraig/fexample.txt &gt; example.txt</code></pre>
+
+<p>It&#39;s your responsibility to make sure the file is really compressed: BackupPC_zcat doesn&#39;t check which backup the requested file is from. BackupPC_zcat returns a non-zero status if it fails to uncompress a file.</p>
+
 </dd>
-<dt><strong><a name="backuppc_tarcreate" class="item">BackupPC_tarCreate</a></strong></dt>
-
+<dt id="BackupPC_tarCreate">BackupPC_tarCreate</dt>
 <dd>
-<p>BackupPC_tarCreate creates a tar file for any files or directories in
-a particular backup.  Merging of incrementals is done automatically,
-so you don't need to worry about whether certain files appear in the
-incremental or full backup.</p>
+
+<p>BackupPC_tarCreate creates a tar file for any files or directories in a particular backup. Merging of incrementals is done automatically, so you don&#39;t need to worry about whether certain files appear in the incremental or full backup.</p>
+
 <p>The usage is:</p>
-<pre>
-    BackupPC_tarCreate [options] files/directories...
+
+<pre><code>    BackupPC_tarCreate [options] files/directories...
     Required options:
        -h host         host from which the tar archive is created
        -n dumpNum      dump number from which the tar archive is created
@@ -1633,25 +1137,22 @@
        -w writeBufSz   write buffer size (default 1048576 = 1MB)
        -e charset      charset for encoding file names (default: value of
                        <a href="#_conf_clientcharset_">$Conf{ClientCharset}</a> when backup was done)
-       -l              just print a file listing; don't generate an archive
-       -L              just print a detailed file listing; don't generate an archive</pre>
-<p>The command-line files and directories are relative to the specified
-shareName.  The tar file is written to stdout.</p>
-<p>The -h, -n and -s options specify which dump is used to generate
-the tar archive.  The -r and -p options can be used to relocate
-the paths in the tar archive so extracted files can be placed
-in a location different from their original location.</p>
+       -l              just print a file listing; don&#39;t generate an archive
+       -L              just print a detailed file listing; don&#39;t generate an archive</code></pre>
+
+<p>The command-line files and directories are relative to the specified shareName. The tar file is written to stdout.</p>
+
+<p>The -h, -n and -s options specify which dump is used to generate the tar archive. The -r and -p options can be used to relocate the paths in the tar archive so extracted files can be placed in a location different from their original location.</p>
+
 </dd>
-<dt><strong><a name="backuppc_zipcreate" class="item">BackupPC_zipCreate</a></strong></dt>
-
+<dt id="BackupPC_zipCreate">BackupPC_zipCreate</dt>
 <dd>
-<p>BackupPC_zipCreate creates a zip file for any files or directories in
-a particular backup.  Merging of incrementals is done automatically,
-so you don't need to worry about whether certain files appear in the
-incremental or full backup.</p>
+
+<p>BackupPC_zipCreate creates a zip file for any files or directories in a particular backup. Merging of incrementals is done automatically, so you don&#39;t need to worry about whether certain files appear in the incremental or full backup.</p>
+
 <p>The usage is:</p>
-<pre>
-    BackupPC_zipCreate [options] files/directories...
+
+<pre><code>    BackupPC_zipCreate [options] files/directories...
     Required options:
        -h host         host from which the zip archive is created
        -n dumpNum      dump number from which the tar archive is created
@@ -1664,1239 +1165,967 @@
        -r pathRemove   path prefix that will be replaced with pathAdd
        -p pathAdd      new path prefix
        -c level        compression level (default is 0, no compression)
-       -e charset      charset for encoding file names (default: cp1252)</pre>
-<p>The command-line files and directories are relative to the specified
-shareName.  The zip file is written to stdout. The -h, -n and -s
-options specify which dump is used to generate the zip archive.  The
--r and -p options can be used to relocate the paths in the zip archive
-so extracted files can be placed in a location different from their
-original location.</p>
+       -e charset      charset for encoding file names (default: utf8)</code></pre>
+
+<p>The command-line files and directories are relative to the specified shareName. The zip file is written to stdout. The -h, -n and -s options specify which dump is used to generate the zip archive. The -r and -p options can be used to relocate the paths in the zip archive so extracted files can be placed in a location different from their original location.</p>
+
 </dd>
 </dl>
+
 <p>Each of these programs reside in __INSTALLDIR__/bin.</p>
-<p>
-<a href="#__index__"><small>Back to Top</small></a>
-</p>
+
 <hr />
-<h1><a name="archive_functions">Archive functions</a></h1>
-<p>BackupPC supports archiving to removable media. For users that require
-offsite backups, BackupPC can create archives that stream to tape
-devices, or create files of specified sizes to fit onto cd or dvd media.</p>
-<p>Each archive type is specified by a BackupPC host with its XferMethod
-set to 'archive'. This allows for multiple configurations at sites where
-there might be a combination of tape and cd/dvd backups being made.</p>
-<p>BackupPC provides a menu that allows one or more hosts to be archived.
-The most recent backup of each host is archived using BackupPC_tarCreate,
-and the output is optionally compressed and split into fixed-sized
-files (eg: 650MB).</p>
-<p>The archive for each host is done by default using
-__INSTALLDIR__/bin/BackupPC_archiveHost.  This script can be copied
-and customized as needed.</p>
-<p>
-</p>
-<h2><a name="configuring_an_archive_host">Configuring an Archive Host</a></h2>
-<p>To create an Archive Host, add it to the hosts file just as any other host
-and call it a name that best describes the type of archive, e.g. ArchiveDLT</p>
-<p>To tell BackupPC that the Host is for Archives, create a config.pl file in 
-the Archive Hosts's pc directory, adding the following line:</p>
-<p><a href="#_conf_xfermethod_">$Conf{XferMethod}</a> = 'archive';</p>
-<p>To further customise the archive's parameters you can adding the changed
-parameters in the host's config.pl file. The parameters are explained in
-the config.pl file.  Parameters may be fixed or the user can be allowed 
-to change them (eg: output device).</p>
-<p>The per-host archive command is <a href="#_conf_archiveclientcmd_">$Conf{ArchiveClientCmd}</a>.  By default
-this invokes</p>
-<pre>
-     __INSTALLDIR__/bin/BackupPC_archiveHost</pre>
+<h1 id="Archive-functions">Archive functions</h1>
+
+<p>BackupPC supports archiving to removable media. For users that require offsite backups, BackupPC can create archives that stream to tape devices, or create files of specified sizes to fit onto cd or dvd media.</p>
+
+<p>Each archive type is specified by a BackupPC host with its XferMethod set to &#39;archive&#39;. This allows for multiple configurations at sites where there might be a combination of tape and cd/dvd backups being made.</p>
+
+<p>BackupPC provides a menu that allows one or more hosts to be archived. The most recent backup of each host is archived using BackupPC_tarCreate, and the output is optionally compressed and split into fixed-sized files (eg: 650MB).</p>
+
+<p>The archive for each host is done by default using __INSTALLDIR__/bin/BackupPC_archiveHost. This script can be copied and customized as needed.</p>
+
+<h2 id="Configuring-an-Archive-Host">Configuring an Archive Host</h2>
+
+<p>To create an Archive Host, add it to the hosts file just as any other host and call it a name that best describes the type of archive, e.g. ArchiveDLT</p>
+
+<p>To tell BackupPC that the Host is for Archives, create a config.pl file in the Archive Hosts&#39;s pc directory, adding the following line:</p>
+
+<p><a href="#_conf_xfermethod_">$Conf{XferMethod}</a> = &#39;archive&#39;;</p>
+
+<p>To further customise the archive&#39;s parameters you can adding the changed parameters in the host&#39;s config.pl file. The parameters are explained in the config.pl file. Parameters may be fixed or the user can be allowed to change them (eg: output device).</p>
+
+<p>The per-host archive command is <a href="#_conf_archiveclientcmd_">$Conf{ArchiveClientCmd}</a>. By default this invokes</p>
+
+<pre><code>     __INSTALLDIR__/bin/BackupPC_archiveHost</code></pre>
+
 <p>which you can copy and customize as necessary.</p>
-<p>
-</p>
-<h2><a name="starting_an_archive">Starting an Archive</a></h2>
-<p>In the web interface, click on the Archive Host you wish to use. You will see a
-list of previous archives and a summary on each. By clicking the &quot;Start Archive&quot;
-button you are presented with the list of hosts and the approximate backup size
-(note this is raw size, not projected compressed size) Select the hosts you wish
-to archive and press the &quot;Archive Selected Hosts&quot; button.</p>
-<p>The next screen allows you to adjust the parameters for this archive run.
-Press the &quot;Start the Archive&quot; to start archiving the selected hosts with the
-parameters displayed.</p>
-<p>
-</p>
-<h2><a name="starting_an_archive_from_the_command_line">Starting an Archive from the command line</a></h2>
-<p>The script BackupPC_archiveStart can be used to start an archive from
-the command line (or cron etc).  The usage is:</p>
-<pre>
-    BackupPC_archiveStart archiveHost userName hosts...</pre>
-<p>This creates an archive of the most recent backup of each of
-the specified hosts.  The first two arguments are the archive
-host and the user name making the request.</p>
-<p>
-<a href="#__index__"><small>Back to Top</small></a>
-</p>
-<hr />
-<h1><a name="other_cgi_functions">Other CGI Functions</a></h1>
-<p>
-</p>
-<h2><a name="configuration_and_host_editor">Configuration and Host Editor</a></h2>
-<p>The CGI interface has a complete configuration and host editor.
-Only the administrator can edit the main configuration settings
-and hosts.  The edit links are in the left navigation bar.</p>
-<p>When changes are made to any parameter a &quot;Save&quot; button appears
-at the top of the page.  If you are editing a text box you will
-need to click outside of the text box to make the Save button
-appear.  If you don't select Save then the changes won't be saved.</p>
-<p>The host-specific configuration can be edited from the host
-summary page using the link in the left navigation bar.
-The administrator can edit any of the host-specific
-configuration settings.</p>
-<p>When editing the host-specific configuration, each parameter has
-an &quot;override&quot; setting that denotes the value is host-specific,
-meaning that it overrides the setting in the main configuration.
-If you unselect &quot;override&quot; then the setting is removed from
-the host-specific configuration, and the main configuration
-file is displayed.</p>
-<p>User's can edit their host-specific configuration if enabled
-via <a href="#_conf_cgiuserconfigeditenable_">$Conf{CgiUserConfigEditEnable}</a>.  The specific subset
-of configuration settings that a user can edit is specified
-with <a href="#_conf_cgiuserconfigedit_">$Conf{CgiUserConfigEdit}</a>.  It is recommended to make this
-list short as possible (you probably don't want your users saving
-dozens of backups) and it is essential that they can't edit any
-of the Cmd configuration settings, otherwise they can specify
-an arbitrary command that will be executed as the BackupPC
-user.</p>
-<p>
-</p>
-<h2><a name="rss">RSS</a></h2>
-<p>BackupPC supports a very basic RSS feed.  Provided you have the
-XML::RSS perl module installed, a URL similar to this will
-provide RSS information:</p>
-<pre>
-    <a href="http://localhost/cgi-bin/BackupPC/BackupPC_Admin?action=rss">http://localhost/cgi-bin/BackupPC/BackupPC_Admin?action=rss</a></pre>
-<p>This feature is experimental.  The information included will
-probably change.</p>
-<p>
-<a href="#__index__"><small>Back to Top</small></a>
-</p>
-<hr />
-<h1><a name="backuppc_design">BackupPC Design</a></h1>
-<p>
-</p>
-<h2><a name="some_design_issues">Some design issues</a></h2>
+
+<h2 id="Starting-an-Archive">Starting an Archive</h2>
+
+<p>In the web interface, click on the Archive Host you wish to use. You will see a list of previous archives and a summary on each. By clicking the &quot;Start Archive&quot; button you are presented with the list of hosts and the approximate backup size (note this is raw size, not projected compressed size) Select the hosts you wish to archive and press the &quot;Archive Selected Hosts&quot; button.</p>
+
+<p>The next screen allows you to adjust the parameters for this archive run. Press the &quot;Start the Archive&quot; to start archiving the selected hosts with the parameters displayed.</p>
+
+<h2 id="Starting-an-Archive-from-the-command-line">Starting an Archive from the command line</h2>
+
+<p>The script BackupPC_archiveStart can be used to start an archive from the command line (or cron etc). The usage is:</p>
+
+<pre><code>    BackupPC_archiveStart archiveHost userName hosts...</code></pre>
+
+<p>This creates an archive of the most recent backup of each of the specified hosts. The first two arguments are the archive host and the user name making the request.</p>
+
+<hr />
+<h1 id="Other-CGI-Functions">Other CGI Functions</h1>
+
+<h2 id="Configuration-and-Host-Editor">Configuration and Host Editor</h2>
+
+<p>The CGI interface has a complete configuration and host editor. Only the administrator can edit the main configuration settings and hosts. The edit links are in the left navigation bar.</p>
+
+<p>When changes are made to any parameter a &quot;Save&quot; button appears at the top of the page. If you are editing a text box you will need to click outside of the text box to make the Save button appear. If you don&#39;t select Save then the changes won&#39;t be saved.</p>
+
+<p>The host-specific configuration can be edited from the host summary page using the link in the left navigation bar. The administrator can edit any of the host-specific configuration settings.</p>
+
+<p>When editing the host-specific configuration, each parameter has an &quot;override&quot; setting that denotes the value is host-specific, meaning that it overrides the setting in the main configuration. If you unselect &quot;override&quot; then the setting is removed from the host-specific configuration, and the main configuration file is displayed.</p>
+
+<p>User&#39;s can edit their host-specific configuration if enabled via <a href="#_conf_cgiuserconfigeditenable_">$Conf{CgiUserConfigEditEnable}</a>. The specific subset of configuration settings that a user can edit is specified with <a href="#_conf_cgiuserconfigedit_">$Conf{CgiUserConfigEdit}</a>. It is recommended to make this list short as possible (you probably don&#39;t want your users saving dozens of backups) and it is essential that they can&#39;t edit any of the Cmd configuration settings, otherwise they can specify an arbitrary command that will be executed as the BackupPC user.</p>
+
+<h2 id="RSS">RSS</h2>
+
+<p>BackupPC supports a very basic RSS feed. Provided you have the XML::RSS perl module installed, a URL similar to this will provide RSS information:</p>
+
+<pre><code>    http://localhost/cgi-bin/BackupPC/BackupPC_Admin?action=rss</code></pre>
+
+<p>This feature is experimental. The information included will probably change.</p>
+
+<hr />
+<h1 id="BackupPC-Design">BackupPC Design</h1>
+
+<h2 id="Some-design-issues">Some design issues</h2>
+
 <dl>
-<dt><strong><a name="pooling_common_files" class="item">Pooling common files</a></strong></dt>
-
-<dd>
-<p>To quickly see if a file is already in the pool, an MD5 digest of the
-file length and contents is used as the file name in the pool. This
-can't guarantee a file is identical: it just reduces the search to
-often a single file or handful of files. A complete file comparison
-is always done to verify if two files are really the same.</p>
-<p>Identical files on multiples backups are represented by hard links.
-Hardlinks are used so that identical files all refer to the same
-physical file on the server's disk. Also, hard links maintain
-reference counts so that BackupPC knows when to delete unused files
-from the pool.</p>
-<p>For the computer-science majors among you, you can think of the pooling
-system used by BackupPC as just a chained hash table stored on a (big)
-file system.</p>
-</dd>
-<dt><strong><a name="the_hashing_function" class="item">The hashing function</a></strong></dt>
-
-<dd>
-<p>There is a tradeoff between how much of file is used for the MD5 digest
-and the time taken comparing all the files that have the same hash.</p>
-<p>Using the file length and just the first 4096 bytes of the file for the
-MD5 digest produces some repetitions.  One example: with 900,000 unique
-files in the pool, this hash gives about 7,000 repeated files, and in
-the worst case 500 files have the same hash.  That's not bad: we only
-have to do a single file compare 99.2% of the time.  But in the worst
-case we have to compare as many as 500 files checking for a match.</p>
-<p>With a modest increase in CPU time, if we use the file length and the
-first 256K of the file we now only have 500 repeated files and in the
-worst case around 20 files have the same hash. Furthermore, if we
-instead use the first and last 128K of the file (more specifically, the
-first and eighth 128K chunks for files larger than 1MB) we get only 300
-repeated files and in the worst case around 20 files have the same hash.</p>
-<p>Based on this experimentation, this is the hash function used by BackupPC.
-It is important that you don't change the hash function after files
-are already in the pool.  Otherwise your pool will grow to twice the
-size until all the old backups (and all the old files with old hashes)
-eventually expire.</p>
-</dd>
-<dt><strong><a name="compression" class="item">Compression</a></strong></dt>
-
-<dd>
-<p>BackupPC supports compression. It uses the deflate and inflate methods
-in the Compress::Zlib module, which is based on the zlib compression
-library (see <a href="http://www.gzip.org/zlib/">http://www.gzip.org/zlib/</a>).</p>
-<p>The <a href="#_conf_compresslevel_">$Conf{CompressLevel}</a> setting specifies the compression level to use.
-Zero (0) means no compression. Compression levels can be from 1 (least
-cpu time, slightly worse compression) to 9 (most cpu time, slightly
-better compression). The recommended value is 3. Changing it to 5, for
-example, will take maybe 20% more cpu time and will get another 2-3%
-additional compression. Diminishing returns set in above 5.  See the zlib
-documentation for more information about compression levels.</p>
-<p>BackupPC implements compression with minimal CPU load. Rather than
-compressing every incoming backup file and then trying to match it
-against the pool, BackupPC computes the MD5 digest based on the
-uncompressed file, and matches against the candidate pool files by
-comparing each uncompressed pool file against the incoming backup file.
-Since inflating a file takes roughly a factor of 10 less CPU time than
-deflating there is a big saving in CPU time.</p>
-<p>The combination of pooling common files and compression can yield
-a factor of 8 or more overall saving in backup storage.</p>
+
+<dt id="Pooling-common-files">Pooling common files</dt>
+<dd>
+
+<p>To quickly see if a file is already in the pool, an MD5 digest of the file length and contents is used as the file name in the pool. This can&#39;t guarantee a file is identical: it just reduces the search to often a single file or handful of files. A complete file comparison is always done to verify if two files are really the same.</p>
+
+<p>Identical files on multiples backups are represented by hard links. Hardlinks are used so that identical files all refer to the same physical file on the server&#39;s disk. Also, hard links maintain reference counts so that BackupPC knows when to delete unused files from the pool.</p>
+
+<p>For the computer-science majors among you, you can think of the pooling system used by BackupPC as just a chained hash table stored on a (big) file system.</p>
+
+</dd>
+<dt id="The-hashing-function">The hashing function</dt>
+<dd>
+
+<p>There is a tradeoff between how much of file is used for the MD5 digest and the time taken comparing all the files that have the same hash.</p>
+
+<p>Using the file length and just the first 4096 bytes of the file for the MD5 digest produces some repetitions. One example: with 900,000 unique files in the pool, this hash gives about 7,000 repeated files, and in the worst case 500 files have the same hash. That&#39;s not bad: we only have to do a single file compare 99.2% of the time. But in the worst case we have to compare as many as 500 files checking for a match.</p>
+
+<p>With a modest increase in CPU time, if we use the file length and the first 256K of the file we now only have 500 repeated files and in the worst case around 20 files have the same hash. Furthermore, if we instead use the first and last 128K of the file (more specifically, the first and eighth 128K chunks for files larger than 1MB) we get only 300 repeated files and in the worst case around 20 files have the same hash.</p>
+
+<p>Based on this experimentation, this is the hash function used by BackupPC. It is important that you don&#39;t change the hash function after files are already in the pool. Otherwise your pool will grow to twice the size until all the old backups (and all the old files with old hashes) eventually expire.</p>
+
+</dd>
+<dt id="Compression">Compression</dt>
+<dd>
+
+<p>BackupPC supports compression. It uses the deflate and inflate methods in the Compress::Zlib module, which is based on the zlib compression library (see <a href="http://www.gzip.org/zlib/">http://www.gzip.org/zlib/</a>).</p>
+
+<p>The <a href="#_conf_compresslevel_">$Conf{CompressLevel}</a> setting specifies the compression level to use. Zero (0) means no compression. Compression levels can be from 1 (least cpu time, slightly worse compression) to 9 (most cpu time, slightly better compression). The recommended value is 3. Changing it to 5, for example, will take maybe 20% more cpu time and will get another 2-3% additional compression. Diminishing returns set in above 5. See the zlib documentation for more information about compression levels.</p>
+
+<p>BackupPC implements compression with minimal CPU load. Rather than compressing every incoming backup file and then trying to match it against the pool, BackupPC computes the MD5 digest based on the uncompressed file, and matches against the candidate pool files by comparing each uncompressed pool file against the incoming backup file. Since inflating a file takes roughly a factor of 10 less CPU time than deflating there is a big saving in CPU time.</p>
+
+<p>The combination of pooling common files and compression can yield a factor of 8 or more overall saving in backup storage.</p>
+
 </dd>
 </dl>
-<p>
-</p>
-<h2><a name="backuppc_operation">BackupPC operation</a></h2>
-<p>BackupPC reads the configuration information from
-__CONFDIR__/config.pl. It then runs and manages all the backup
-activity. It maintains queues of pending backup requests, user backup
-requests and administrative commands. Based on the configuration various
-requests will be executed simultaneously.</p>
-<p>As specified by <a href="#_conf_wakeupschedule_">$Conf{WakeupSchedule}</a>, BackupPC wakes up periodically
-to queue backups on all the PCs.  This is a four step process:</p>
+
+<h2 id="BackupPC-operation">BackupPC operation</h2>
+
+<p>BackupPC reads the configuration information from __CONFDIR__/config.pl. It then runs and manages all the backup activity. It maintains queues of pending backup requests, user backup requests and administrative commands. Based on the configuration various requests will be executed simultaneously.</p>
+
+<p>As specified by <a href="#_conf_wakeupschedule_">$Conf{WakeupSchedule}</a>, BackupPC wakes up periodically to queue backups on all the PCs. This is a four step process:</p>
+
 <ol>
-<li>
-<p>For each host and DHCP address backup requests are queued on the
-background command queue.</p>
+
+<li><p>For each host and DHCP address backup requests are queued on the background command queue.</p>
+
 </li>
-<li>
-<p>For each PC, BackupPC_dump is forked. Several of these may be run in
-parallel, based on the configuration. First a ping is done to see if
-the machine is alive. If this is a DHCP address, nmblookup is run to
-get the netbios name, which is used as the host name. If DNS lookup
-fails, <a href="#_conf_nmblookupfindhostcmd_">$Conf{NmbLookupFindHostCmd}</a> is run to find the IP address from
-the host name.  The file __TOPDIR__/pc/$host/backups is read to decide
-whether a full or incremental backup needs to be run. If no backup is
-scheduled, or the ping to $host fails, then BackupPC_dump exits.</p>
-<p>The backup is done using the specified XferMethod.  Either samba's smbclient
-or tar over ssh/rsh/nfs piped into BackupPC_tarExtract, or rsync over ssh/rsh
-is run, or rsyncd is connected to, with the incoming data
-extracted to __TOPDIR__/pc/$host/new.  The XferMethod output is put
-into __TOPDIR__/pc/$host/XferLOG.</p>
-<p>The letter in the XferLOG file shows the type of object, similar to the
-first letter of the modes displayed by ls -l:</p>
-<pre>
-    d -&gt; directory
+<li><p>For each PC, BackupPC_dump is forked. Several of these may be run in parallel, based on the configuration. First a ping is done to see if the machine is alive. If this is a DHCP address, nmblookup is run to get the netbios name, which is used as the host name. If DNS lookup fails, <a href="#_conf_nmblookupfindhostcmd_">$Conf{NmbLookupFindHostCmd}</a> is run to find the IP address from the host name. The file __TOPDIR__/pc/$host/backups is read to decide whether a full or incremental backup needs to be run. If no backup is scheduled, or the ping to $host fails, then BackupPC_dump exits.</p>
+
+<p>The backup is done using the specified XferMethod. Either samba&#39;s smbclient or tar over ssh/rsh/nfs piped into BackupPC_tarExtract, or rsync over ssh/rsh is run, or rsyncd is connected to, with the incoming data extracted to __TOPDIR__/pc/$host/new. The XferMethod output is put into __TOPDIR__/pc/$host/XferLOG.</p>
+
+<p>The letter in the XferLOG file shows the type of object, similar to the first letter of the modes displayed by ls -l:</p>
+
+<pre><code>    d -&gt; directory
     l -&gt; symbolic link
     b -&gt; block special file
     c -&gt; character special file
     p -&gt; pipe file (fifo)
-    nothing -&gt; regular file</pre>
+    nothing -&gt; regular file</code></pre>
+
 <p>The words mean:</p>
+
 <dl>
-<dt><strong><a name="create" class="item">create</a></strong></dt>
 
+<dt id="create">create</dt>
 <dd>
+
 <p>new for this backup (ie: directory or file not in pool)</p>
+
 </dd>
-<dt><strong><a name="pool" class="item">pool</a></strong></dt>
-
+<dt id="pool">pool</dt>
 <dd>
+
 <p>found a match in the pool</p>
-</dd>
-<dt><strong><a name="same" class="item">same</a></strong></dt>
-
-<dd>
-<p>file is identical to previous backup (contents were
-checksummed and verified during full dump).</p>
-</dd>
-<dt><strong><a name="skip" class="item">skip</a></strong></dt>
-
-<dd>
-<p>file skipped in incremental because attributes are the
-same (only displayed if <a href="#_conf_xferloglevel_">$Conf{XferLogLevel}</a> &gt;= 2).</p>
+
+</dd>
+<dt id="same">same</dt>
+<dd>
+
+<p>file is identical to previous backup (contents were checksummed and verified during full dump).</p>
+
+</dd>
+<dt id="skip">skip</dt>
+<dd>
+
+<p>file skipped in incremental because attributes are the same (only displayed if <a href="#_conf_xferloglevel_">$Conf{XferLogLevel}</a> &gt;= 2).</p>
+
 </dd>
 </dl>
-<p>As BackupPC_tarExtract extracts the files from smbclient or tar, or as
-rsync or ftp runs, it checks each file in the backup to see if it is
-identical to an existing file from any previous backup of any PC. It
-does this without needed to write the file to disk. If the file matches
-an existing file, a hardlink is created to the existing file in the
-pool. If the file does not match any existing files, the file is written
-to disk and the file name is saved in __TOPDIR__/pc/$host/NewFileList
-for later processing by BackupPC_link.  BackupPC_tarExtract and rsync
-can handle arbitrarily large files and multiple candidate matching files
-without needing to write the file to disk in the case of a match.  This
-significantly reduces disk writes (and also reads, since the pool file
-comparison is done disk to memory, rather than disk to disk).</p>
-<p>Based on the configuration settings, BackupPC_dump checks each
-old backup to see if any should be removed.  Any expired backups
-are moved to __TOPDIR__/trash for later removal by BackupPC_trashClean.</p>
-</li>
-<li>
-<p>For each complete, good, backup, BackupPC_link is run.
-To avoid race conditions as new files are linked into the
-pool area, only a single BackupPC_link program runs
-at a time and the rest are queued.</p>
-<p>BackupPC_link reads the NewFileList written by BackupPC_dump and
-inspects each new file in the backup. It re-checks if there is a
-matching file in the pool (another BackupPC_link
-could have added the file since BackupPC_dump checked). If so, the file
-is removed and replaced by a hard link to the existing file. If the file
-is new, a hard link to the file is made in the pool area, so that this
-file is available for checking against each new file and new backup.</p>
-<p>Then, if <a href="#_conf_incrfill_">$Conf{IncrFill}</a> is set (note that the default setting is
-off), for each incremental backup, hard links are made in the new
-backup to all files that were not extracted during the incremental
-backups.  The means the incremental backup looks like a complete
-image of the PC (with the exception that files that were removed on
-the PC since the last full backup will still appear in the backup
-directory tree).</p>
-<p>The CGI interface knows how to merge unfilled incremental backups will
-the most recent prior filled (full) backup, giving the incremental
-backups a filled appearance.  The default for <a href="#_conf_incrfill_">$Conf{IncrFill}</a> is off,
-since there is no need to fill incremental backups.  This saves
-some level of disk activity, since lots of extra hardlinks are no
-longer needed (and don't have to be deleted when the backup expires).</p>
-</li>
-<li>
-<p>BackupPC_trashClean is always run in the background to remove any
-expired backups. Every 5 minutes it wakes up and removes all the files
-in __TOPDIR__/trash.</p>
-<p>Also, once each night, BackupPC_nightly is run to complete some
-additional administrative tasks, such as cleaning the pool.  This
-involves removing any files in the pool that only have a single
-hard link (meaning no backups are using that file).  Again, to
-avoid race conditions, BackupPC_nightly is only run when there
-are no BackupPC_link processes running.  When BackupPC_nightly is
-run no new BackupPC_link jobs are started.  If BackupPC_nightly
-takes too long to run, the settings <a href="#_conf_maxbackuppcnightlyjobs_">$Conf{MaxBackupPCNightlyJobs}</a>
-and <a href="#_conf_backuppcnightlyperiod_">$Conf{BackupPCNightlyPeriod}</a> can be used to run several
-BackupPC_nightly processes in parallel, and to split its job over
-several nights.</p>
+
+<p>As BackupPC_tarExtract extracts the files from smbclient or tar, or as rsync or ftp runs, it checks each file in the backup to see if it is identical to an existing file from any previous backup of any PC. It does this without needed to write the file to disk. If the file matches an existing file, a hardlink is created to the existing file in the pool. If the file does not match any existing files, the file is written to disk and the file name is saved in __TOPDIR__/pc/$host/NewFileList for later processing by BackupPC_link. BackupPC_tarExtract and rsync can handle arbitrarily large files and multiple candidate matching files without needing to write the file to disk in the case of a match. This significantly reduces disk writes (and also reads, since the pool file comparison is done disk to memory, rather than disk to disk).</p>
+
+<p>Based on the configuration settings, BackupPC_dump checks each old backup to see if any should be removed. Any expired backups are moved to __TOPDIR__/trash for later removal by BackupPC_trashClean.</p>
+
+</li>
+<li><p>For each complete, good, backup, BackupPC_link is run. To avoid race conditions as new files are linked into the pool area, only a single BackupPC_link program runs at a time and the rest are queued.</p>
+
+<p>BackupPC_link reads the NewFileList written by BackupPC_dump and inspects each new file in the backup. It re-checks if there is a matching file in the pool (another BackupPC_link could have added the file since BackupPC_dump checked). If so, the file is removed and replaced by a hard link to the existing file. If the file is new, a hard link to the file is made in the pool area, so that this file is available for checking against each new file and new backup.</p>
+
+<p>Then, if <a href="#_conf_incrfill_">$Conf{IncrFill}</a> is set (note that the default setting is off), for each incremental backup, hard links are made in the new backup to all files that were not extracted during the incremental backups. The means the incremental backup looks like a complete image of the PC (with the exception that files that were removed on the PC since the last full backup will still appear in the backup directory tree).</p>
+
+<p>The CGI interface knows how to merge unfilled incremental backups will the most recent prior filled (full) backup, giving the incremental backups a filled appearance. The default for <a href="#_conf_incrfill_">$Conf{IncrFill}</a> is off, since there is no need to fill incremental backups. This saves some level of disk activity, since lots of extra hardlinks are no longer needed (and don&#39;t have to be deleted when the backup expires).</p>
+
+</li>
+<li><p>BackupPC_trashClean is always run in the background to remove any expired backups. Every 5 minutes it wakes up and removes all the files in __TOPDIR__/trash.</p>
+
+<p>Also, once each night, BackupPC_nightly is run to complete some additional administrative tasks, such as cleaning the pool. This involves removing any files in the pool that only have a single hard link (meaning no backups are using that file). Again, to avoid race conditions, BackupPC_nightly is only run when there are no BackupPC_link processes running. When BackupPC_nightly is run no new BackupPC_link jobs are started. If BackupPC_nightly takes too long to run, the settings <a href="#_conf_maxbackuppcnightlyjobs_">$Conf{MaxBackupPCNightlyJobs}</a> and <a href="#_conf_backuppcnightlyperiod_">$Conf{BackupPCNightlyPeriod}</a> can be used to run several BackupPC_nightly processes in parallel, and to split its job over several nights.</p>
+
 </li>
 </ol>
-<p>BackupPC also listens for TCP connections on <a href="#_conf_serverport_">$Conf{ServerPort}</a>, which
-is used by the CGI script BackupPC_Admin for status reporting and
-user-initiated backup or backup cancel requests.</p>
-<p>
-</p>
-<h2><a name="storage_layout">Storage layout</a></h2>
+
+<p>BackupPC also listens for TCP connections on <a href="#_conf_serverport_">$Conf{ServerPort}</a>, which is used by the CGI script BackupPC_Admin for status reporting and user-initiated backup or backup cancel requests.</p>
+
+<h2 id="Storage-layout">Storage layout</h2>
+
 <p>BackupPC resides in several directories:</p>
+
 <dl>
-<dt><strong><a name="installdir" class="item">__INSTALLDIR__</a></strong></dt>
 
+<dt id="INSTALLDIR__">__INSTALLDIR__</dt>
 <dd>
-<p>Perl scripts comprising BackupPC reside in __INSTALLDIR__/bin,
-libraries are in __INSTALLDIR__/lib and documentation
-is in __INSTALLDIR__/doc.</p>
+
+<p>Perl scripts comprising BackupPC reside in __INSTALLDIR__/bin, libraries are in __INSTALLDIR__/lib and documentation is in __INSTALLDIR__/doc.</p>
+
 </dd>
-<dt><strong><a name="cgidir" class="item">__CGIDIR__</a></strong></dt>
+<dt id="CGIDIR__">__CGIDIR__</dt>
+<dd>
 
-<dd>
 <p>The CGI script BackupPC_Admin resides in this cgi binary directory.</p>
+
 </dd>
-<dt><strong><a name="confdir" class="item">__CONFDIR__</a></strong></dt>
-
+<dt id="CONFDIR__">__CONFDIR__</dt>
 <dd>
-<p>All the configuration information resides below __CONFDIR__.
-This directory contains:</p>
+
+<p>All the configuration information resides below __CONFDIR__. This directory contains:</p>
+
 <p>The directory __CONFDIR__ contains:</p>
+
 <dl>
-<dt><strong><a name="config_pl" class="item">config.pl</a></strong></dt>
 
+<dt id="config.pl">config.pl</dt>
 <dd>
-<p>Configuration file. See <a href="#configuration_file">Configuration file</a>
-below for more details.</p>
+
+<p>Configuration file. See <a href="#Configuration-File">&quot;Configuration File&quot;</a> below for more details.</p>
+
 </dd>
-<dt><strong><a name="hosts" class="item">hosts</a></strong></dt>
+<dt id="hosts">hosts</dt>
+<dd>
 
-<dd>
 <p>Hosts file, which lists all the PCs to backup.</p>
+
 </dd>
-<dt><strong><a name="pc" class="item">pc</a></strong></dt>
-
+<dt id="pc">pc</dt>
 <dd>
-<p>The directory __CONFDIR__/pc contains per-client configuration files
-that override settings in the main configuration file.  Each file
-is named __CONFDIR__/pc/HOST.pl, where HOST is the host name.</p>
-<p>In pre-FHS versions of BackupPC these files were located in
-__TOPDIR__/pc/HOST/config.pl.</p>
+
+<p>The directory __CONFDIR__/pc contains per-client configuration files that override settings in the main configuration file. Each file is named __CONFDIR__/pc/HOST.pl, where HOST is the host name.</p>
+
+<p>In pre-FHS versions of BackupPC these files were located in __TOPDIR__/pc/HOST/config.pl.</p>
+
 </dd>
 </dl>
+
 </dd>
-<dt><strong><a name="logdir" class="item">__LOGDIR__</a></strong></dt>
-
+<dt id="LOGDIR__">__LOGDIR__</dt>
 <dd>
-<p>The directory __LOGDIR__ (__TOPDIR__/log on pre-FHS versions
-of BackupPC) contains:</p>
+
+<p>The directory __LOGDIR__ (__TOPDIR__/log on pre-FHS versions of BackupPC) contains:</p>
+
 <dl>
-<dt><strong><a name="log" class="item">LOG</a></strong></dt>
-
-<dd>
-<p>Current (today's) log file output from BackupPC.</p>
-</dd>
-<dt><strong><a name="log_0_or_log_0_z" class="item">LOG.0 or LOG.0.z</a></strong></dt>
-
-<dd>
-<p>Yesterday's log file output.  Log files are aged daily and compressed
-(if compression is enabled), and old LOG files are deleted.</p>
-</dd>
-<dt><strong><a name="backuppc_pid" class="item">BackupPC.pid</a></strong></dt>
-
-<dd>
-<p>Contains BackupPC's process id.</p>
-</dd>
-<dt><strong><a name="status_pl" class="item">status.pl</a></strong></dt>
-
-<dd>
-<p>A summary of BackupPC's status written periodically by BackupPC so
-that certain state information can be maintained if BackupPC is
-restarted.  Should not be edited.</p>
-</dd>
-<dt><strong><a name="useremailinfo_pl" class="item">UserEmailInfo.pl</a></strong></dt>
-
-<dd>
-<p>A summary of what email was last sent to each user, and when the
-last email was sent.  Should not be edited.</p>
+
+<dt id="LOG">LOG</dt>
+<dd>
+
+<p>Current (today&#39;s) log file output from BackupPC.</p>
+
+</dd>
+<dt id="LOG.0-or-LOG.0.z">LOG.0 or LOG.0.z</dt>
+<dd>
+
+<p>Yesterday&#39;s log file output. Log files are aged daily and compressed (if compression is enabled), and old LOG files are deleted.</p>
+
+</dd>
+<dt id="BackupPC.pid">BackupPC.pid</dt>
+<dd>
+
+<p>Contains BackupPC&#39;s process id.</p>
+
+</dd>
+<dt id="status.pl">status.pl</dt>
+<dd>
+
+<p>A summary of BackupPC&#39;s status written periodically by BackupPC so that certain state information can be maintained if BackupPC is restarted. Should not be edited.</p>
+
+</dd>
+<dt id="UserEmailInfo.pl">UserEmailInfo.pl</dt>
+<dd>
+
+<p>A summary of what email was last sent to each user, and when the last email was sent. Should not be edited.</p>
+
 </dd>
 </dl>
+
 </dd>
-<dt><strong><a name="topdir" class="item">__TOPDIR__</a></strong></dt>
-
+<dt id="TOPDIR__">__TOPDIR__</dt>
 <dd>
-<p>All of BackupPC's data (PC backup images, logs, configuration information)
-is stored below this directory.</p>
+
+<p>All of BackupPC&#39;s data (PC backup images, logs, configuration information) is stored below this directory.</p>
+
 <p>Below __TOPDIR__ are several directories:</p>
+
 <dl>
-<dt><strong><a name="topdir_trash" class="item">__TOPDIR__/trash</a></strong></dt>
 
+<dt id="TOPDIR__-trash">__TOPDIR__/trash</dt>
 <dd>
-<p>Any directories and files below this directory are periodically deleted
-whenever BackupPC_trashClean checks. When a backup is aborted or when an
-old backup expires, BackupPC_dump simply moves the directory to
-__TOPDIR__/trash for later removal by BackupPC_trashClean.</p>
+
+<p>Any directories and files below this directory are periodically deleted whenever BackupPC_trashClean checks. When a backup is aborted or when an old backup expires, BackupPC_dump simply moves the directory to __TOPDIR__/trash for later removal by BackupPC_trashClean.</p>
+
 </dd>
-<dt><strong><a name="topdir_pool" class="item">__TOPDIR__/pool</a></strong></dt>
-
+<dt id="TOPDIR__-pool">__TOPDIR__/pool</dt>
 <dd>
-<p>All uncompressed files from PC backups are stored below __TOPDIR__/pool.
-Each file's name is based on the MD5 hex digest of the file contents.
-Specifically, for files less than 256K, the file length and the entire
-file is used. For files up to 1MB, the file length and the first and
-last 128K are used. Finally, for files longer than 1MB, the file length,
-and the first and eighth 128K chunks for the file are used.</p>
-<p>Each file is stored in a subdirectory X/Y/Z, where X, Y, Z are the
-first 3 hex digits of the MD5 digest.</p>
-<p>For example, if a file has an MD5 digest of 123456789abcdef0,
-the file is stored in __TOPDIR__/pool/1/2/3/123456789abcdef0.</p>
-<p>The MD5 digest might not be unique (especially since not all the file's
-contents are used for files bigger than 256K). Different files that have
-the same MD5 digest are stored with a trailing suffix &quot;_n&quot; where n is
-an incrementing number starting at 0. So, for example, if two additional
-files were identical to the first, except the last byte was different,
-and assuming the file was larger than 1MB (so the MD5 digests are the
-same but the files are actually different), the three files would be
-stored as:</p>
-<pre>
-        __TOPDIR__/pool/1/2/3/123456789abcdef0
+
+<p>All uncompressed files from PC backups are stored below __TOPDIR__/pool. Each file&#39;s name is based on the MD5 hex digest of the file contents. Specifically, for files less than 256K, the file length and the entire file is used. For files up to 1MB, the file length and the first and last 128K are used. Finally, for files longer than 1MB, the file length, and the first and eighth 128K chunks for the file are used.</p>
+
+<p>Each file is stored in a subdirectory X/Y/Z, where X, Y, Z are the first 3 hex digits of the MD5 digest.</p>
+
+<p>For example, if a file has an MD5 digest of 123456789abcdef0, the file is stored in __TOPDIR__/pool/1/2/3/123456789abcdef0.</p>
+
+<p>The MD5 digest might not be unique (especially since not all the file&#39;s contents are used for files bigger than 256K). Different files that have the same MD5 digest are stored with a trailing suffix &quot;_n&quot; where n is an incrementing number starting at 0. So, for example, if two additional files were identical to the first, except the last byte was different, and assuming the file was larger than 1MB (so the MD5 digests are the same but the files are actually different), the three files would be stored as:</p>
+
+<pre><code>        __TOPDIR__/pool/1/2/3/123456789abcdef0
         __TOPDIR__/pool/1/2/3/123456789abcdef0_0
-        __TOPDIR__/pool/1/2/3/123456789abcdef0_1</pre>
-<p>Both BackupPC_dump (actually, BackupPC_tarExtract) and BackupPC_link are
-responsible for checking newly backed up files against the pool. For
-each file, the MD5 digest is used to generate a file name in the pool
-directory. If the file exists in the pool, the contents are compared.
-If there is no match, additional files ending in &quot;_n&quot; are checked.
-(Actually, BackupPC_tarExtract compares multiple candidate files in
-parallel.)  If the file contents exactly match, the file is created by
-simply making a hard link to the pool file (this is done by
-BackupPC_tarExtract as the backup proceeds). Otherwise,
-BackupPC_tarExtract writes the new file to disk and a new hard link is
-made in the pool to the file (this is done later by BackupPC_link).</p>
-<p>Therefore, every file in the pool will have at least 2 hard links
-(one for the pool file and one for the backup file below __TOPDIR__/pc).
-Identical files from different backups or PCs will all be linked to
-the same file.  When old backups are deleted, some files in the pool
-might only have one link.  BackupPC_nightly checks the entire pool
-and removes all files that have only a single link, thereby recovering
-the storage for that file.</p>
-<p>One other issue: zero length files are not pooled, since there are a lot
-of these files and on most file systems it doesn't save any disk space
-to turn these files into hard links.</p>
-</dd>
-<dt><strong><a name="topdir_cpool" class="item">__TOPDIR__/cpool</a></strong></dt>
-
-<dd>
-<p>All compressed files from PC backups are stored below __TOPDIR__/cpool.
-Its layout is the same as __TOPDIR__/pool, and the hashing function
-is the same (and, importantly, based on the uncompressed file, not
-the compressed file).</p>
-</dd>
-<dt><strong><a name="topdir_pc_host" class="item">__TOPDIR__/pc/$host</a></strong></dt>
-
-<dd>
-<p>For each PC $host, all the backups for that PC are stored below
-the directory __TOPDIR__/pc/$host.  This directory contains the
-following files:</p>
+        __TOPDIR__/pool/1/2/3/123456789abcdef0_1</code></pre>
+
+<p>Both BackupPC_dump (actually, BackupPC_tarExtract) and BackupPC_link are responsible for checking newly backed up files against the pool. For each file, the MD5 digest is used to generate a file name in the pool directory. If the file exists in the pool, the contents are compared. If there is no match, additional files ending in &quot;_n&quot; are checked. (Actually, BackupPC_tarExtract compares multiple candidate files in parallel.) If the file contents exactly match, the file is created by simply making a hard link to the pool file (this is done by BackupPC_tarExtract as the backup proceeds). Otherwise, BackupPC_tarExtract writes the new file to disk and a new hard link is made in the pool to the file (this is done later by BackupPC_link).</p>
+
+<p>Therefore, every file in the pool will have at least 2 hard links (one for the pool file and one for the backup file below __TOPDIR__/pc). Identical files from different backups or PCs will all be linked to the same file. When old backups are deleted, some files in the pool might only have one link. BackupPC_nightly checks the entire pool and removes all files that have only a single link, thereby recovering the storage for that file.</p>
+
+<p>One other issue: zero length files are not pooled, since there are a lot of these files and on most file systems it doesn&#39;t save any disk space to turn these files into hard links.</p>
+
+</dd>
+<dt id="TOPDIR__-cpool">__TOPDIR__/cpool</dt>
+<dd>
+
+<p>All compressed files from PC backups are stored below __TOPDIR__/cpool. Its layout is the same as __TOPDIR__/pool, and the hashing function is the same (and, importantly, based on the uncompressed file, not the compressed file).</p>
+
+</dd>
+<dt id="TOPDIR__-pc-host">__TOPDIR__/pc/$host</dt>
+<dd>
+
+<p>For each PC $host, all the backups for that PC are stored below the directory __TOPDIR__/pc/$host. This directory contains the following files:</p>
+
 <dl>
-<dt><strong><a name="log2" class="item">LOG</a></strong></dt>
 
+<dt id="LOG1">LOG</dt>
 <dd>
+
 <p>Current log file for this PC from BackupPC_dump.</p>
-</dd>
-<dt><strong><a name="log_ddmmyyyy_or_log_ddmmyyyy_z" class="item">LOG.DDMMYYYY or LOG.DDMMYYYY.z</a></strong></dt>
-
-<dd>
-<p>Last month's log file.  Log files are aged monthly and compressed
-(if compression is enabled), and old LOG files are deleted.
-In earlier versions of BackupPC these files used to have
-a suffix of 0, 1, ....</p>
-</dd>
-<dt><strong><a name="xfererr_or_xfererr_z" class="item">XferERR or XferERR.z</a></strong></dt>
-
-<dd>
-<p>Output from the transport program (ie: smbclient, tar, rsync or ftp)
-for the most recent failed backup.</p>
-</dd>
-<dt><strong><a name="new" class="item">new</a></strong></dt>
-
-<dd>
-<p>Subdirectory in which the current backup is stored.  This
-directory is renamed if the backup succeeds.</p>
-</dd>
-<dt><strong><a name="xferlog_or_xferlog_z" class="item">XferLOG or XferLOG.z</a></strong></dt>
-
-<dd>
-<p>Output from the transport program (ie: smbclient, tar, rsync or ftp)
-for the current backup.</p>
-</dd>
-<dt><strong><a name="nnn" class="item">nnn (an integer)</a></strong></dt>
-
-<dd>
+
+</dd>
+<dt id="LOG.DDMMYYYY-or-LOG.DDMMYYYY.z">LOG.DDMMYYYY or LOG.DDMMYYYY.z</dt>
+<dd>
+
+<p>Last month&#39;s log file. Log files are aged monthly and compressed (if compression is enabled), and old LOG files are deleted. In earlier versions of BackupPC these files used to have a suffix of 0, 1, ....</p>
+
+</dd>
+<dt id="XferERR-or-XferERR.z">XferERR or XferERR.z</dt>
+<dd>
+
+<p>Output from the transport program (ie: smbclient, tar, rsync or ftp) for the most recent failed backup.</p>
+
+</dd>
+<dt id="new">new</dt>
+<dd>
+
+<p>Subdirectory in which the current backup is stored. This directory is renamed if the backup succeeds.</p>
+
+</dd>
+<dt id="XferLOG-or-XferLOG.z">XferLOG or XferLOG.z</dt>
+<dd>
+
+<p>Output from the transport program (ie: smbclient, tar, rsync or ftp) for the current backup.</p>
+
+</dd>
+<dt id="nnn-an-integer-">nnn (an integer)</dt>
+<dd>
+
 <p>Successful backups are in directories numbered sequentially starting at 0.</p>
-</dd>
-<dt><strong><a name="xferlog_nnn_or_xferlog_nnn_z" class="item">XferLOG.nnn or XferLOG.nnn.z</a></strong></dt>
-
-<dd>
-<p>Output from the transport program (ie: smbclient, tar, rsync or ftp)
-corresponding to backup number nnn.</p>
-</dd>
-<dt><strong><a name="restoreinfo_nnn" class="item">RestoreInfo.nnn</a></strong></dt>
-
-<dd>
-<p>Information about restore request #nnn including who, what, when, and
-why. This file is in Data::Dumper format.  (Note that the restore
-numbers are not related to the backup number.)</p>
-</dd>
-<dt><strong><a name="restorelog_nnn_z" class="item">RestoreLOG.nnn.z</a></strong></dt>
-
-<dd>
-<p>Output from smbclient, tar or rsync during restore #nnn.  (Note that the restore
-numbers are not related to the backup number.)</p>
-</dd>
-<dt><strong><a name="archiveinfo_nnn" class="item">ArchiveInfo.nnn</a></strong></dt>
-
-<dd>
-<p>Information about archive request #nnn including who, what, when, and
-why. This file is in Data::Dumper format.  (Note that the archive
-numbers are not related to the restore or backup number.)</p>
-</dd>
-<dt><strong><a name="archivelog_nnn_z" class="item">ArchiveLOG.nnn.z</a></strong></dt>
-
-<dd>
-<p>Output from archive #nnn.  (Note that the archive numbers are not related
-to the backup or restore number.)</p>
-</dd>
-<dt><strong><a name="config_pl2" class="item">config.pl</a></strong></dt>
-
-<dd>
-<p>Old location of optional configuration settings specific to this host.
-Settings in this file override the main configuration file.
-In new versions of BackupPC the per-host configuration files are
-stored in __CONFDIR__/pc/HOST.pl.</p>
-</dd>
-<dt><strong><a name="backups" class="item">backups</a></strong></dt>
-
-<dd>
-<p>A tab-delimited ascii table listing information about each successful
-backup, one per row.  The columns are:</p>
+
+</dd>
+<dt id="XferLOG.nnn-or-XferLOG.nnn.z">XferLOG.nnn or XferLOG.nnn.z</dt>
+<dd>
+
+<p>Output from the transport program (ie: smbclient, tar, rsync or ftp) corresponding to backup number nnn.</p>
+
+</dd>
+<dt id="RestoreInfo.nnn">RestoreInfo.nnn</dt>
+<dd>
+
+<p>Information about restore request #nnn including who, what, when, and why. This file is in Data::Dumper format. (Note that the restore numbers are not related to the backup number.)</p>
+
+</dd>
+<dt id="RestoreLOG.nnn.z">RestoreLOG.nnn.z</dt>
+<dd>
+
+<p>Output from smbclient, tar or rsync during restore #nnn. (Note that the restore numbers are not related to the backup number.)</p>
+
+</dd>
+<dt id="ArchiveInfo.nnn">ArchiveInfo.nnn</dt>
+<dd>
+
+<p>Information about archive request #nnn including who, what, when, and why. This file is in Data::Dumper format. (Note that the archive numbers are not related to the restore or backup number.)</p>
+
+</dd>
+<dt id="ArchiveLOG.nnn.z">ArchiveLOG.nnn.z</dt>
+<dd>
+
+<p>Output from archive #nnn. (Note that the archive numbers are not related to the backup or restore number.)</p>
+
+</dd>
+<dt id="config.pl1">config.pl</dt>
+<dd>
+
+<p>Old location of optional configuration settings specific to this host. Settings in this file override the main configuration file. In new versions of BackupPC the per-host configuration files are stored in __CONFDIR__/pc/HOST.pl.</p>
+
+</dd>
+<dt id="backups">backups</dt>
+<dd>
+
+<p>A tab-delimited ascii table listing information about each successful backup, one per row. The columns are:</p>
+
 <dl>
-<dt><strong><a name="num" class="item">num</a></strong></dt>
 
+<dt id="num">num</dt>
 <dd>
-<p>The backup number, an integer that starts at 0 and increments
-for each successive backup.  The corresponding backup is stored
-in the directory num (eg: if this field is 5, then the backup is
-stored in __TOPDIR__/pc/$host/5).</p>
+
+<p>The backup number, an integer that starts at 0 and increments for each successive backup. The corresponding backup is stored in the directory num (eg: if this field is 5, then the backup is stored in __TOPDIR__/pc/$host/5).</p>
+
 </dd>
-<dt><strong><a name="type" class="item">type</a></strong></dt>
+<dt id="type">type</dt>
+<dd>
 
-<dd>
 <p>Set to &quot;full&quot; or &quot;incr&quot; for full or incremental backup.</p>
+
 </dd>
-<dt><strong><a name="starttime" class="item">startTime</a></strong></dt>
-
+<dt id="startTime">startTime</dt>
 <dd>
+
 <p>Start time of the backup in unix seconds.</p>
+
 </dd>
-<dt><strong><a name="endtime" class="item">endTime</a></strong></dt>
-
+<dt id="endTime">endTime</dt>
 <dd>
+
 <p>Stop time of the backup in unix seconds.</p>
+
 </dd>
-<dt><strong><a name="nfiles" class="item">nFiles</a></strong></dt>
-
+<dt id="nFiles">nFiles</dt>
 <dd>
+
 <p>Number of files backed up (as reported by smbclient, tar, rsync or ftp).</p>
+
 </dd>
-<dt><strong><a name="size" class="item">size</a></strong></dt>
-
+<dt id="size">size</dt>
 <dd>
+
 <p>Total file size backed up (as reported by smbclient, tar, rsync or ftp).</p>
-</dd>
-<dt><strong><a name="nfilesexist" class="item">nFilesExist</a></strong></dt>
-
-<dd>
-<p>Number of files that were already in the pool
-(as determined by BackupPC_dump and BackupPC_link).</p>
-</dd>
-<dt><strong><a name="sizeexist" class="item">sizeExist</a></strong></dt>
-
-<dd>
-<p>Total size of files that were already in the pool
-(as determined by BackupPC_dump and BackupPC_link).</p>
-</dd>
-<dt><strong><a name="nfilesnew" class="item">nFilesNew</a></strong></dt>
-
-<dd>
-<p>Number of files that were not in the pool
-(as determined by BackupPC_link).</p>
-</dd>
-<dt><strong><a name="sizenew" class="item">sizeNew</a></strong></dt>
-
-<dd>
-<p>Total size of files that were not in the pool
-(as determined by BackupPC_link).</p>
-</dd>
-<dt><strong><a name="xfererrs" class="item">xferErrs</a></strong></dt>
-
-<dd>
+
+</dd>
+<dt id="nFilesExist">nFilesExist</dt>
+<dd>
+
+<p>Number of files that were already in the pool (as determined by BackupPC_dump and BackupPC_link).</p>
+
+</dd>
+<dt id="sizeExist">sizeExist</dt>
+<dd>
+
+<p>Total size of files that were already in the pool (as determined by BackupPC_dump and BackupPC_link).</p>
+
+</dd>
+<dt id="nFilesNew">nFilesNew</dt>
+<dd>
+
+<p>Number of files that were not in the pool (as determined by BackupPC_link).</p>
+
+</dd>
+<dt id="sizeNew">sizeNew</dt>
+<dd>
+
+<p>Total size of files that were not in the pool (as determined by BackupPC_link).</p>
+
+</dd>
+<dt id="xferErrs">xferErrs</dt>
+<dd>
+
 <p>Number of errors or warnings from smbclient, tar, rsync or ftp.</p>
+
 </dd>
-<dt><strong><a name="xferbadfile" class="item">xferBadFile</a></strong></dt>
-
+<dt id="xferBadFile">xferBadFile</dt>
 <dd>
+
 <p>Number of errors from smbclient that were bad file errors (zero otherwise).</p>
+
 </dd>
-<dt><strong><a name="xferbadshare" class="item">xferBadShare</a></strong></dt>
-
+<dt id="xferBadShare">xferBadShare</dt>
 <dd>
+
 <p>Number of errors from smbclient that were bad share errors (zero otherwise).</p>
+
 </dd>
-<dt><strong><a name="tarerrs" class="item">tarErrs</a></strong></dt>
-
+<dt id="tarErrs">tarErrs</dt>
 <dd>
+
 <p>Number of errors from BackupPC_tarExtract.</p>
-</dd>
-<dt><strong><a name="compress" class="item">compress</a></strong></dt>
-
-<dd>
-<p>The compression level used on this backup.  Zero or empty means no
-compression.</p>
-</dd>
-<dt><strong><a name="sizeexistcomp" class="item">sizeExistComp</a></strong></dt>
-
-<dd>
-<p>Total compressed size of files that were already in the pool
-(as determined by BackupPC_dump and BackupPC_link).</p>
-</dd>
-<dt><strong><a name="sizenewcomp" class="item">sizeNewComp</a></strong></dt>
-
-<dd>
-<p>Total compressed size of files that were not in the pool
-(as determined by BackupPC_link).</p>
-</dd>
-<dt><strong><a name="nofill" class="item">noFill</a></strong></dt>
-
-<dd>
-<p>Set if this backup has not been filled in with the most recent
-previous filled or full backup.  See <a href="#_conf_incrfill_">$Conf{IncrFill}</a>.</p>
-</dd>
-<dt><strong><a name="fillfromnum" class="item">fillFromNum</a></strong></dt>
-
-<dd>
-<p>If this backup was filled (ie: noFill is 0) then this is the
-number of the backup that it was filled from</p>
-</dd>
-<dt><strong><a name="mangle" class="item">mangle</a></strong></dt>
-
-<dd>
-<p>Set if this backup has mangled file names and attributes.  Always
-true for backups in v1.4.0 and above.  False for all backups prior
-to v1.4.0.</p>
-</dd>
-<dt><strong><a name="xfermethod" class="item">xferMethod</a></strong></dt>
-
-<dd>
+
+</dd>
+<dt id="compress">compress</dt>
+<dd>
+
+<p>The compression level used on this backup. Zero or empty means no compression.</p>
+
+</dd>
+<dt id="sizeExistComp">sizeExistComp</dt>
+<dd>
+
+<p>Total compressed size of files that were already in the pool (as determined by BackupPC_dump and BackupPC_link).</p>
+
+</dd>
+<dt id="sizeNewComp">sizeNewComp</dt>
+<dd>
+
+<p>Total compressed size of files that were not in the pool (as determined by BackupPC_link).</p>
+
+</dd>
+<dt id="noFill">noFill</dt>
+<dd>
+
+<p>Set if this backup has not been filled in with the most recent previous filled or full backup. See <a href="#_conf_incrfill_">$Conf{IncrFill}</a>.</p>
+
+</dd>
+<dt id="fillFromNum">fillFromNum</dt>
+<dd>
+
+<p>If this backup was filled (ie: noFill is 0) then this is the number of the backup that it was filled from</p>
+
+</dd>
+<dt id="mangle">mangle</dt>
+<dd>
+
+<p>Set if this backup has mangled file names and attributes. Always true for backups in v1.4.0 and above. False for all backups prior to v1.4.0.</p>
+
+</dd>
+<dt id="xferMethod">xferMethod</dt>
+<dd>
+
 <p>Set to the value of <a href="#_conf_xfermethod_">$Conf{XferMethod}</a> when this dump was done.</p>
+
 </dd>
-<dt><strong><a name="level" class="item">level</a></strong></dt>
-
+<dt id="level">level</dt>
 <dd>
-<p>The level of this dump.  A full dump is level 0.  Currently incrementals
-are 1.  But when multi-level incrementals are supported this will reflect
-each dump's incremental level.</p>
+
+<p>The level of this dump. A full dump is level 0. Currently incrementals are 1. But when multi-level incrementals are supported this will reflect each dump&#39;s incremental level.</p>
+
 </dd>
 </dl>
+
 </dd>
-<dt><strong><a name="restores" class="item">restores</a></strong></dt>
-
+<dt id="restores">restores</dt>
 <dd>
-<p>A tab-delimited ascii table listing information about each requested
-restore, one per row.  The columns are:</p>
+
+<p>A tab-delimited ascii table listing information about each requested restore, one per row. The columns are:</p>
+
 <dl>
-<dt><strong>num</strong></dt>
 
+<dt id="num1">num</dt>
 <dd>
-<p>Restore number (matches the suffix of the RestoreInfo.nnn and
-RestoreLOG.nnn.z file), unrelated to the backup number.</p>
+
+<p>Restore number (matches the suffix of the RestoreInfo.nnn and RestoreLOG.nnn.z file), unrelated to the backup number.</p>
+
 </dd>
-<dt><strong><a name="starttime2" class="item">startTime</a></strong></dt>
+<dt id="startTime1">startTime</dt>
+<dd>
 
-<dd>
 <p>Start time of the restore in unix seconds.</p>
+
 </dd>
-<dt><strong><a name="endtime2" class="item">endTime</a></strong></dt>
-
+<dt id="endTime1">endTime</dt>
 <dd>
+
 <p>End time of the restore in unix seconds.</p>
+
 </dd>
-<dt><strong><a name="result" class="item">result</a></strong></dt>
-
+<dt id="result">result</dt>
 <dd>
+
 <p>Result (ok or failed).</p>
+
 </dd>
-<dt><strong><a name="errormsg" class="item">errorMsg</a></strong></dt>
-
+<dt id="errorMsg">errorMsg</dt>
 <dd>
+
 <p>Error message if restore failed.</p>
+
 </dd>
-<dt><strong><a name="nfiles2" class="item">nFiles</a></strong></dt>
-
+<dt id="nFiles1">nFiles</dt>
 <dd>
+
 <p>Number of files restored.</p>
+
 </dd>
-<dt><strong>size</strong></dt>
-
+<dt id="size1">size</dt>
 <dd>
+
 <p>Size in bytes of the restored files.</p>
+
 </dd>
-<dt><strong><a name="tarcreateerrs" class="item">tarCreateErrs</a></strong></dt>
-
+<dt id="tarCreateErrs">tarCreateErrs</dt>
 <dd>
+
 <p>Number of errors from BackupPC_tarCreate during restore.</p>
+
 </dd>
-<dt><strong><a name="xfererrs2" class="item">xferErrs</a></strong></dt>
-
+<dt id="xferErrs1">xferErrs</dt>
 <dd>
+
 <p>Number of errors from smbclient, tar, rsync or ftp during restore.</p>
+
 </dd>
 </dl>
+
 </dd>
-<dt><strong><a name="archives" class="item">archives</a></strong></dt>
-
+<dt id="archives">archives</dt>
 <dd>
-<p>A tab-delimited ascii table listing information about each requested
-archive, one per row.  The columns are:</p>
+
+<p>A tab-delimited ascii table listing information about each requested archive, one per row. The columns are:</p>
+
 <dl>
-<dt><strong>num</strong></dt>
 
+<dt id="num2">num</dt>
 <dd>
-<p>Archive number (matches the suffix of the ArchiveInfo.nnn and
-ArchiveLOG.nnn.z file), unrelated to the backup or restore number.</p>
+
+<p>Archive number (matches the suffix of the ArchiveInfo.nnn and ArchiveLOG.nnn.z file), unrelated to the backup or restore number.</p>
+
 </dd>
-<dt><strong><a name="starttime3" class="item">startTime</a></strong></dt>
+<dt id="startTime2">startTime</dt>
+<dd>
 
-<dd>
 <p>Start time of the restore in unix seconds.</p>
+
 </dd>
-<dt><strong><a name="endtime3" class="item">endTime</a></strong></dt>
-
+<dt id="endTime2">endTime</dt>
 <dd>
+
 <p>End time of the restore in unix seconds.</p>
+
 </dd>
-<dt><strong>result</strong></dt>
-
+<dt id="result1">result</dt>
 <dd>
+
 <p>Result (ok or failed).</p>
+
 </dd>
-<dt><strong><a name="errormsg2" class="item">errorMsg</a></strong></dt>
-
+<dt id="errorMsg1">errorMsg</dt>
 <dd>
+
 <p>Error message if archive failed.</p>
-</dd>
-</dl>
-</dd>
-</dl>
-</dd>
-</dl>
-</dd>
-</dl>
-<p>
-</p>
-<h2><a name="compressed_file_format">Compressed file format</a></h2>
-<p>The compressed file format is as generated by Compress::Zlib::deflate
-with one minor, but important, tweak. Since Compress::Zlib::inflate
-fully inflates its argument in memory, it could take large amounts of
-memory if it was inflating a highly compressed file. For example, a
-200MB file of 0x0 bytes compresses to around 200K bytes. If
-Compress::Zlib::inflate was called with this single 200K buffer, it
-would need to allocate 200MB of memory to return the result.</p>
-<p>BackupPC watches how efficiently a file is compressing. If a big file
-has very high compression (meaning it will use too much memory when it
-is inflated), BackupPC calls the <code>flush()</code> method, which gracefully
-completes the current compression.  BackupPC then starts another
-deflate and simply appends the output file.  So the BackupPC compressed
-file format is one or more concatenated deflations/flushes.  The specific
-ratios that BackupPC uses is that if a 6MB chunk compresses to less
-than 64K then a flush will be done.</p>
-<p>Back to the example of the 200MB file of 0x0 bytes.  Adding flushes
-every 6MB adds only 200 or so bytes to the 200K output.  So the
-storage cost of flushing is negligible.</p>
-<p>To easily decompress a BackupPC compressed file, the script
-BackupPC_zcat can be found in __INSTALLDIR__/bin.  For each
-file name argument it inflates the file and writes it to stdout.</p>
-<p>
-</p>
-<h2><a name="rsync_checksum_caching">Rsync checksum caching</a></h2>
-<p>An incremental backup with rsync compares attributes on the client
-with the last full backup.  Any files with identical attributes
-are skipped.  A full backup with rsync sets the --ignore-times
-option, which causes every file to be examined independent of
-attributes.</p>
-<p>Each file is examined by generating block checksums (default 2K
-blocks) on the receiving side (that's the BackupPC side), sending
-those checksums to the client, where the remote rsync matches those
-checksums with the corresponding file.  The matching blocks and new
-data is sent back, allowing the client file to be reassembled.
-A checksum for the entire file is sent to as an extra check the
-the reconstructed file is correct.</p>
-<p>This results in significant disk IO and computation for BackupPC:
-every file in a full backup, or any file with non-matching attributes
-in an incremental backup, needs to be uncompressed, block checksums
-computed and sent.  Then the receiving side reassembles the file and
-has to verify the whole-file checksum.  Even if the file is identical,
-prior to 2.1.0, BackupPC had to read and uncompress the file twice,
-once to compute the block checksums and later to verify the whole-file
-checksum.</p>
-<p>Starting in 2.1.0, BackupPC supports optional checksum caching,
-which means the block and file checksums only need to be computed
-once for each file.  This results in a significant performance
-improvement.  This only works for compressed pool files.
-It is enabled by adding</p>
-<pre>
-        '--checksum-seed=32761',</pre>
+
+</dd>
+</dl>
+
+</dd>
+</dl>
+
+</dd>
+</dl>
+
+</dd>
+</dl>
+
+<h2 id="Compressed-file-format">Compressed file format</h2>
+
+<p>The compressed file format is as generated by Compress::Zlib::deflate with one minor, but important, tweak. Since Compress::Zlib::inflate fully inflates its argument in memory, it could take large amounts of memory if it was inflating a highly compressed file. For example, a 200MB file of 0x0 bytes compresses to around 200K bytes. If Compress::Zlib::inflate was called with this single 200K buffer, it would need to allocate 200MB of memory to return the result.</p>
+
+<p>BackupPC watches how efficiently a file is compressing. If a big file has very high compression (meaning it will use too much memory when it is inflated), BackupPC calls the flush() method, which gracefully completes the current compression. BackupPC then starts another deflate and simply appends the output file. So the BackupPC compressed file format is one or more concatenated deflations/flushes. The specific ratios that BackupPC uses is that if a 6MB chunk compresses to less than 64K then a flush will be done.</p>
+
+<p>Back to the example of the 200MB file of 0x0 bytes. Adding flushes every 6MB adds only 200 or so bytes to the 200K output. So the storage cost of flushing is negligible.</p>
+
+<p>To easily decompress a BackupPC compressed file, the script BackupPC_zcat can be found in __INSTALLDIR__/bin. For each file name argument it inflates the file and writes it to stdout.</p>
+
+<h2 id="Rsync-checksum-caching">Rsync checksum caching</h2>
+
+<p>An incremental backup with rsync compares attributes on the client with the last full backup. Any files with identical attributes are skipped. A full backup with rsync sets the --ignore-times option, which causes every file to be examined independent of attributes.</p>
+
+<p>Each file is examined by generating block checksums (default 2K blocks) on the receiving side (that&#39;s the BackupPC side), sending those checksums to the client, where the remote rsync matches those checksums with the corresponding file. The matching blocks and new data is sent back, allowing the client file to be reassembled. A checksum for the entire file is sent to as an extra check the the reconstructed file is correct.</p>
+