For SMB and tar, BackupPC uses the modification time (mtime) to
determine which files have changed since the last lower-level
-backup. That mean SMB and tar incrementals are not able to detect
+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.
This page has links to the current releases of BackupPC.
-=item BackupPC FAQ
+=item BackupPC Wiki
-BackupPC has a FAQ at L<http://backuppc.sourceforge.net/faq>.
+BackupPC has a Wiki at L<http://backuppc.wiki.sourceforge.net>.
+Everyone is encouraged to contribute to the Wiki. Anyone with
+a SourceForge account can edit the Wiki.
-=item Mail lists
+The old FAQ is at L<http://backuppc.sourceforge.net/faq>, but
+is deprecated in favor of the Wiki.
+
+=item Mailing lists
Three BackupPC mailing lists exist for announcements (backuppc-announce),
developers (backuppc-devel), and a general user list for support, asking
all of you! Feel free to vote for BackupPC at
L<http://freshmeat.net/projects/backuppc>.
-Also, everyone is encouraged to contribute patches, bug reports, feature
-and design suggestions, new code, FAQs, and documentation corrections or
-improvements. Answering questions on the mail list is a big help too.
+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.
=head1 Installing BackupPC
moderately configured server.
Several users have reported significantly better performance using
-reiser compared to ext3 for the BackupPC data file system. It is
-also recommended you consider either an LVM or raid setup (either
+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 RAID5) so that you can expand the
file system as necessary.
cannot be read by smbclient whenever Outlook is running. See the
L<Limitations|limitations> section for more discussion of this problem.
-In addition to total disk space, you shold make sure you have
+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
=head2 Step 1: Getting BackupPC
Some linux distributions now include BackupPC. The Debian
-distribution, supprted by Ludovic Drolez, can be found at
-L<http://packages.debian.org/backuppc>; it should be included
-in the next stable Debian release. On Debian, BackupPC can
+distribution, supported by Ludovic Drolez, can be found at
+L<http://packages.debian.org/backuppc> and is included
+in the current stable Debian release. On Debian, BackupPC can
be installed with the command:
apt-get install backuppc
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 will probably want to install the
+released version then you may want to install the
latest version as described below.
Otherwise, manually fetching and installing BackupPC is easy.
=head2 Step 2: Installing the distribution
+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.
+
First off, there are three perl modules you should install.
These are all optional, but highly recommended:
perldoc configure.pl
Starting with BackupPC 3.0.0, the configure.pl script by default
-complies with the file system hierarchy conventions. The major
-difference compared to earlier versions is that 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.
+and the log files will be stored in /var/log/BackupPC
rather than below the data directory, __TOPDIR__/log.
+Note that distributions may choose to use different locations for
+BackupPC files than these defaults.
+
If you are upgrading from an earlier version the configure.pl script
will keep the configuration files and log files in their original
location.
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,
+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.
You should decide where the BackupPC CGI script resides. This will
usually be below Apache's cgi-bin directory.
+It is also possible to use a different directory and use Apache's
+``<Directory>'' directive to specifiy that location. See the Apache
+HTTP Server documentation for additional information.
+
On this installation, this is __CGIDIR__.
-=item Apache image directory
+=item Apache image Directory
A directory where BackupPC's images are stored so that Apache can
-serve them. This should be somewhere under Apache's DocumentRoot
-directory.
+serve them. You should ensure this directory is readable by Apache and
+create a symlink to this directory from the BackupPC CGI bin Directory.
-=item Config and Log directories
+=item Config and Log Directories
In this installation the configuration and log directories are
located in the following locations:
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. If someone submits instructions I
+program like stunnel.
-Setup instructions for ssh are at
+Setup instructions for ssh can be found at
L<http://backuppc.sourceforge.net/faq/ssh.html>.
=item Clients that use DHCP
If this prints mod_perl.c then your Apache supports mod_perl.
+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.
+
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 BackuPC user.
+BackupPC_Admin runs as the BackupPC user.
Here are some specifics for each setup:
First DNS is used to lookup the IP address given the client's name
using perl'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 perls'
+see whether a given host have a DNS entry according to perl's
gethostbyname function with this command:
perl -e 'print(gethostbyname("myhost") ? "ok\n" : "not found\n");'
querying myhost on 10.10.255.255
name_query failed to find name myhost
-If this success you will see output like:
+If it is successful you will see output like:
querying myhost on 10.10.255.255
10.10.1.73 myhost<00>
nmblookup -B 10.10.1.255 myhost
-If necessary, experiment on the nmblookup command that will return the
+If necessary, experiment with the nmblookup command which will return the
IP address of the client given its name. Then update
$Conf{NmbLookupFindHostCmd} with any necessary options to nmblookup.
=back
-This will still allow that client's old backups to be browsable
+This will still allow the client's old backups to be browsable
and restorable.
To completely remove a client and all its backups, you should remove its
=item *
copy the cpool, conf and log directory trees using any technique
-(like cp, rsync or tar) wihtout the need to preserve hardlinks.
+(like cp, rsync or tar) without the need to preserve hardlinks.
=item *
=head2 Fixing installation problems
-Please see the FAQ at L<http://backuppc.sourceforge.net/faq> for
-debugging suggestions.
+Please see the Wiki at L<http://backuppc.wiki.sourceforge.net> for
+debugging suggestions. If you find a solution to your problem that
+could help other users please add it to the Wiki!
=head1 Restore functions
=head2 RSS
BackupPC supports a very basic RSS feed. Provided you have the
-XML::RSS perl module installed, a URL simular to this will
+XML::RSS perl module installed, a URL similar to this will
provide RSS information:
http://localhost/cgi-bin/BackupPC/BackupPC_Admin?action=rss
All of BackupPC's data (PC backup images, logs, configuration information)
is stored below this directory.
-=back
-
Below __TOPDIR__ are several directories:
=over 4
=back
+=back
+
=head2 Compressed file format
The compressed file format is as generated by Compress::Zlib::deflate
BackupPC mostly does reads from disk, maintaining the access time of
files generates a lot of unnecessary disk writes. So, provided
BackupPC has a dedicated data disk, you should consider mounting
-BackupPC's data directory with the noatime attribute (see mount(1)).
+BackupPC's data directory with the noatime (or, with Linux kernels
+>=2.6.20, relatime) attribute (see mount(1)).
=head2 Limitations
Youlin Feng provided the Chinese translation for 3.1.0.
+Karol 'Semper' Stelmaczonek provided the Polish translation for 3.1.0.
+
Jeremy Tietsort provided the host summary table sorting feature for 3.1.0.
Many people have reported bugs, made useful suggestions and helped
-with testing; see the ChangeLog and the mail lists.
+with testing; see the ChangeLog and the mailing lists.
Your name could appear here in the next version!
projects / BackupPC.git / blobdiff