Do we need a message board?
I'd be happy to set one up and host it -- provided Craig (and others)
moderated it.
Thoughts? Craig??
-----Original Message-----
From: backuppc-users-request < at > lists.sourceforge.net
[mailto:backuppc-users-request < at > lists.sourceforge.net]
Sent: Tuesday, June 08, 2004 9:55 AM
To: backuppc-users < at > lists.sourceforge.net
Subject: BackupPC-users digest, Vol 1 #700 - 7 msgs
Send BackupPC-users mailing list submissions to
backuppc-users < at > lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/backuppc-users
or, via email, send a message with subject or body 'help' to
backuppc-users-request < at > lists.sourceforge.net
You can reach the person managing the list at
backuppc-users-admin < at > lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of BackupPC-users digest..."
Today's Topics:
1. Re: Large backup taking far too long (Guus Houtzager - Luna.nl)
2. Re: Large backup taking far too long (Guus Houtzager - Luna.nl)
3. Re: Large backup taking far too long (Les Mikesell)
4. Re: Large backup taking far too long (Ross Skaliotis)
5. Re: Large backup taking far too long (Carl Wilhelm Soderstrom)
6. Re: Large backup taking far too long (Carl Wilhelm Soderstrom)
7. Newbie - three problems (Andrew Wright)
--__--__--
Message: 1
Subject: Re: [BackupPC-users] Large backup taking far too long
From: "Guus Houtzager - Luna.nl" <guus < at > luna.nl>
To: David Rees <drees < at > greenhydrant.com>
Cc: backuppc-users < at > lists.sourceforge.net
Organization: Luna.nl BV
Date: Tue, 08 Jun 2004 09:44:11 +0200
Hi,
On Tue, 2004-06-08 at 00:21, David Rees wrote:
Guus Houtzager - Luna.nl wrote:
I used to have an ext3 fs, which rendered backuppc backups really,
really slow. Switching to reiserfs solved that. For me the trouble
surfaced with the running of backuppc_nightly. Using the patch with the
external program to run that in inode order solved that mostly, so
basically I don't have any performance issues at the moment.
What kernel were you using? I wonder if ext3 with the dir_index feature
turned on (available in 2.6 kernels) helps things... Right now my
backuppc servers are using reiserfs.
That was on a 2.4 kernel. I wasn't planning on running 2.6 on a
production server but I needed the performance increase to keep things
acceptable.
-Dave
Regards,
Guus
--__--__--
Message: 2
Subject: Re: [BackupPC-users] Large backup taking far too long
From: "Guus Houtzager - Luna.nl" <guus < at > luna.nl>
To: Carl Wilhelm Soderstrom <chrome < at > real-time.com>
Cc: Les Mikesell <les < at > futuresource.com>,
Ross Skaliotis <mross < at > rs-net.org>,
backuppc-users < at > lists.sourceforge.net
Organization: Luna.nl BV
Date: Tue, 08 Jun 2004 09:50:19 +0200
Hi,
On Tue, 2004-06-08 at 00:57, Carl Wilhelm Soderstrom wrote:
On 06/07 04:27 , Les Mikesell wrote:
Just guessing, I'd say the inodes involved are splattered all over
the disk and the time involved is mostly waiting for the disk
head to seek to each one. I'm not sure what you can do about
that on a very active filesystem other than add RAM to cache
more of them.
this is one of the places where SCSI (actually, drives that can do Tagged
Command Queueing) win.
TCQ lets the drive re-order the sequence of reads from the disk; so the
firmware can optimize the order in which tracks are read, possibly saving
several rotations of the media and a number of seeks.
so this is why SCSI wins in a lot of cases, when trying to process a lot
of
requests all at once.
for some fascinating discussion of why SCSI often costs more, read this:
http://www.usenix.org/publications/library/proceedings/fast03/tech/full_pape
rs/anderson/anderson_html/index.html
Yeah I know.... I had hoped to avoid some of those issues by using a
3ware card, but that obviously didn't cure it all. Those 3ware cards do
deliver acceptable performance luckily.
I think SATA-II implements TCQ aswell (WD raptor drives do) so maybe
people on a tight budget (ie. all of us
) will get decent
performance when sata-ii is released.
Regards,
Guus
--__--__--
Message: 3
Subject: Re: [BackupPC-users] Large backup taking far too long
From: Les Mikesell <les < at > futuresource.com>
To: "Guus Houtzager - Luna.nl" <guus < at > luna.nl>
Cc: Carl Wilhelm Soderstrom <chrome < at > real-time.com>,
Ross Skaliotis <mross < at > rs-net.org>, backuppc-users < at > lists.sourceforge.net
Date: Tue, 08 Jun 2004 07:40:10 -0500
On Tue, 2004-06-08 at 02:50, Guus Houtzager - Luna.nl wrote:
for some fascinating discussion of why SCSI often costs more, read this:
http://www.usenix.org/publications/library/proceedings/fast03/tech/full_pape
rs/anderson/anderson_html/index.html
Yeah I know.... I had hoped to avoid some of those issues by using a
3ware card, but that obviously didn't cure it all. Those 3ware cards do
deliver acceptable performance luckily.
SCSI is fine when you have lots of concurrent operations but I'd
expect backuppc to wait for the results of each stat before
issuing the next command so you are going to wait for head
motion regardless of the hardware. Linux is pretty aggressive
about caching in RAM and should know more than SCSI drives
about reordering seeks in the queue. I'd max out the RAM
in the box before getting more expensive drives. With a
gig or two you might cache all the inodes.
---
Les Mikesell
les < at > futuresource.com
--__--__--
Message: 4
Date: Tue, 8 Jun 2004 10:37:24 -0400 (EDT)
From: Ross Skaliotis <mross < at > rs-net.org>
To: backuppc-users < at > lists.sourceforge.net
Subject: Re: [BackupPC-users] Large backup taking far too long
I got a useful response to my question over at the reiserfs list:
Reiserfs allocates inodes dynamically, so they're spread all over the
filesystem. So, doing a 'ls -l' in a directory causes major head-seeking.
Other filesystems, including XFS apparently, group inodes together on the
disk. I would assume this solves the problem at the expense of the
filesystem having a fixed number of inodes after creation.
I'm going to give xfs a shot. I'll post my results.
-Ross
On Tue, 8 Jun 2004, Les Mikesell wrote:
On Tue, 2004-06-08 at 02:50, Guus Houtzager - Luna.nl wrote:
for some fascinating discussion of why SCSI often costs more, read
this:
http://www.usenix.org/publications/library/proceedings/fast03/tech/full_pape
rs/anderson/anderson_html/index.html
Yeah I know.... I had hoped to avoid some of those issues by using a
3ware card, but that obviously didn't cure it all. Those 3ware cards do
deliver acceptable performance luckily.
SCSI is fine when you have lots of concurrent operations but I'd
expect backuppc to wait for the results of each stat before
issuing the next command so you are going to wait for head
motion regardless of the hardware. Linux is pretty aggressive
about caching in RAM and should know more than SCSI drives
about reordering seeks in the queue. I'd max out the RAM
in the box before getting more expensive drives. With a
gig or two you might cache all the inodes.
---
Les Mikesell
les < at > futuresource.com
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
--__--__--
Message: 5
Date: Tue, 8 Jun 2004 09:40:54 -0500
From: Carl Wilhelm Soderstrom <chrome < at > real-time.com>
To: backuppc-users < at > lists.sourceforge.net
Subject: Re: [BackupPC-users] Large backup taking far too long
On 06/08 09:50 , Guus Houtzager - Luna.nl wrote:
I think SATA-II implements TCQ aswell (WD raptor drives do) so maybe
people on a tight budget (ie. all of us
) will get decent
performance when sata-ii is released.
I think TCQ is not a required part of the SATA-II spec; so there might very
well be some drives that have it, and some that don't.
WD Raptors are indeed very cool tho. I'm definitely going for them, if I
build a new box for myself in the near future.
--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com
--__--__--
Message: 6
Date: Tue, 8 Jun 2004 09:52:56 -0500
From: Carl Wilhelm Soderstrom <chrome < at > real-time.com>
To: backuppc-users < at > lists.sourceforge.net
Subject: Re: [BackupPC-users] Large backup taking far too long
On 06/08 07:40 , Les Mikesell wrote:
SCSI is fine when you have lots of concurrent operations but I'd
expect backuppc to wait for the results of each stat before
issuing the next command so you are going to wait for head
motion regardless of the hardware.
I'm not familiar with Backuppc's internal architecture, so I don't know.
This doesn't sound like a very efficient way to do things, if it were true
tho. More likely; perl just tells the kernel "read/write these files to/from
disk". The kernel then worries about how to best get the data to/from the
disk.
tho maybe I'm missing what you're getting at here.
Linux is pretty aggressive
about caching in RAM and should know more than SCSI drives
about reordering seeks in the queue.
can't. remember that what the modern drive presents to the OS, has little or
no relation to the way things are physically laid out on disk. the OS
doesn't control head seeks, because it only has an abstracted notion of
where things are on disk. the drive firmware itself handles knowing where
stuff is (otherwise transparent block reallocation wouldn't work).
I'd max out the RAM
in the box before getting more expensive drives. With a
gig or two you might cache all the inodes.
this is definitely a good idea. at times, Backuppc will take all the memory
and CPU you can give it.
--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com
--__--__--
Message: 7
Reply-To: <andy < at > carino.co.uk>
From: "Andrew Wright" <andy < at > carino.co.uk>
To: <backuppc-users < at > lists.sourceforge.net>
Date: Tue, 8 Jun 2004 15:53:46 +0100
Organization: Carino Communications
Subject: [BackupPC-users] Newbie - three problems
This is a multi-part message in MIME format.
------=_NextPart_000_0001_01C44D70.C902B410
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi
I have BackupPC running on our Linux (Mandrake 10) server, backing up =
seven
Windows hosts (1 WIn98, 4 Win2KPro and 2 WinXP Pro) to a Ext3 filesystem
(actually, it's a Lacie Porsche 160G external drive attached to the =
Linux
box through USB 2.0).=20
Three problems:=20
I keep getting "Call timed out: server did not respond after 20000
milliseconds " from one of the Win2K machines - only from this one PC.
BackupPC is not backing up files in certain directories of the hosts.
Especially in Documents and Settings directories. It's navigating the
directory tree ok but says The directory c/Documents and =
Settings/xxx/yyy is
empty '. Is this a WIndows security issue?
Directories are being backed up that Config.pl should be excluding (e.g.
/Program Files)
Config.pl and hosts files are attached.
I've searched the list archive to no avail. Any help gratefully =
received.
Andy Wright
Carino Communications
t: +44 (0)1628 526005
m: +44 7770 904037
andy < at > carino.co.uk
www.carino.co.uk
------=_NextPart_000_0001_01C44D70.C902B410
Content-Type: application/octet-stream;
name="hosts"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="hosts"
#=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -*-perl-*-
#
# Host file list for BackupPC.
#
# DESCRIPTION
#
# This file lists all the hosts that should be backed up by
# BackupPC.
#
# Each line in the hosts file contains three fields, separated
# by white space:
#
# - The host name. If this host is a static IP address this
# must the machine's IP host name (ie: something that can
# be looked up using nslookup or DNS). If this is a DHCP
# host then the host name must be the netbios name of the
# machine. It is possible to have a host name that contains
# spaces, but that is discouraged. Escape a space with "\", eg:
#
# craigs\ pc
#
# - DHCP flag. Set to 0 if this is a static IP address host
# or if the machine can be found using nmblookup. Otherwise,
# if the client can only be found by looking through the DHCP
# pool then set this to 1.
#
# - User name (unix login/email name) of the user who "owns"
# 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. This
# user name must match the name the user authenticates with
# via apache.
#
# - Optional additional user names (comma separated, no white space) =
of
# users who are also allowed to stop/start/browse/restore backups
# for this client via the CGI interface. These users are not sent
# email. These do not need to be valid email names; they simply
# need to match the name the user authenticates with via apache.
#
# AUTHOR
# Craig Barratt <craig < at > arraycomm.com>
#
# COPYRIGHT
# Copyright (C) 2001 Craig Barratt
#
# See http://backuppc.sourceforge.net.
#
#=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
#
# The first non-comment non-empty line gives the field names and should
# not be edited!!
#
host dhcp user moreUsers # <--- do not edit this line
admin2 0 andyw
dell-aw 0 andyw
dell_cs 0 andyw
#dell_laptop 1 andyw
design 0 andyw
evergreen1 0 andyw
evergreen2 0 andyw
#linuxsrvr 1 andyw
winserver 0 andyw
#farside 0 craig jill,jeff # <--- example static IP host =
entry
#larson 1 bill # <--- example DHCP host entry
------=_NextPart_000_0001_01C44D70.C902B410
Content-Type: application/octet-stream;
name="config.pl"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="config.pl"
#=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -*-perl-*-=0A=
#=0A=
# Configuration file for BackupPC.=0A=
#=0A=
# DESCRIPTION=0A=
#=0A=
# This is the main configuration file for BackupPC.=0A=
#=0A=
# This file must be valid perl source, so make sure the punctuation,=0A=
# quotes, and other syntax are valid.=0A=
#=0A=
# This file is read by BackupPC at startup, when a HUP (-1) signal=0A=
# is sent to BackupPC and also at each wakeup time whenever the=0A=
# modification time of this file changes.=0A=
#=0A=
# The configuration parameters are divided into four general groups.=0A=
# The first group (general server configuration) provides general=0A=
# configuration for BackupPC. The next two groups describe what=0A=
# to backup, when to do it, and how long to keep it. The fourth=0A=
# group are settings for the CGI http interface.=0A=
#=0A=
# Configuration settings can also be specified on a per-PC basis.=0A=
# Simply put the relevant settings in a config.pl file in the=0A=
# PC's backup directory (ie: in __TOPDIR__/pc/hostName).=0A=
# All configuration settings in the second, third and fourth=0A=
# groups can be overridden by the per-PC config.pl file.=0A=
#=0A=
# AUTHOR=0A=
# Craig Barratt <cbarratt < at > users.sourceforge.net>=0A=
#=0A=
# COPYRIGHT=0A=
# Copyright (C) 2001-2003 Craig Barratt=0A=
#=0A=
# See http://backuppc.sourceforge.net.=0A=
#=0A=
#=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
=0A=
#########################################################################=
##=0A=
# General server configuration=0A=
#########################################################################=
##=0A=
#=0A=
# Host name on which the BackupPC server is running.=0A=
#=0A=
$Conf{ServerHost} =3D 'linuxsrvr';=0A=
=0A=
#=0A=
# TCP port number on which the BackupPC server listens for and accepts=0A=
# connections. Normally this should be disabled (set to -1). The TCP=0A=
# port is only needed if apache runs on a different machine from =
BackupPC.=0A=
# In that case, set this to any spare port number over 1024 (eg: 2359).=0A=
# If you enable the TCP port, make sure you set $Conf{ServerMesgSecret}=0A=
# too!=0A=
#=0A=
$Conf{ServerPort} =3D -1;=0A=
=0A=
#=0A=
# Shared secret to make the TCP port secure. Set this to a hard to
guess=0A=
# string if you enable the TCP port (ie: $Conf{ServerPort} > 0).=0A=
#=0A=
# To avoid possible attacks via the TCP socket interface, every client=0A=
# message is protected by an MD5 digest. The MD5 digest includes four=0A=
# items:=0A=
# - a seed that is sent to the client when the connection opens=0A=
# - a sequence number that increments for each message=0A=
# - a shared secret that is stored in $Conf{ServerMesgSecret}=0A=
# - the message itself.=0A=
#=0A=
# The message is sent in plain text preceded by the MD5 digest. A=0A=
# snooper can see the plain-text seed sent by BackupPC and plain-text=0A=
# message from the client, but cannot construct a valid MD5 digest since=0A=
# the secret $Conf{ServerMesgSecret} is unknown. A replay attack is=0A=
# not possible since the seed changes on a per-connection and=0A=
# per-message basis.=0A=
#=0A=
$Conf{ServerMesgSecret} =3D '';=0A=
=0A=
#=0A=
# PATH setting for BackupPC. An explicit value is necessary=0A=
# for taint mode. Value shouldn't matter too much since=0A=
# all execs use explicit paths. However, taint mode in perl=0A=
# will complain if this directory is world writable.=0A=
#=0A=
$Conf{MyPath} =3D '/bin';=0A=
=0A=
#=0A=
# Permission mask for directories and files created by BackupPC.=0A=
# Default value prevents any access from group other, and prevents=0A=
# group write.=0A=
#=0A=
# previously $Conf{UmaskMode} =3D 027;=0A=
$Conf{UmaskMode} =3D 000;=0A=
#=0A=
# Times at which we wake up, check all the PCs, and schedule necessary=0A=
# backups. Times are measured in hours since midnight. Can be=0A=
# fractional if necessary (eg: 4.25 means 4:15am).=0A=
#=0A=
# If the hosts you are backing up are always connected to the network=0A=
# you might have only one or two wakeups each night. This will keep=0A=
# the backup activity after hours. On the other hand, if you are
backing=0A=
# up laptops that are only intermittently connected to the network you=0A=
# will want to have frequent wakeups (eg: hourly) to maximized the
chance=0A=
# that each laptop is backed up.=0A=
#=0A=
# Examples:=0A=
# $Conf{WakeupSchedule} =3D [22.5]; # once per day at 10:30 =
pm.=0A=
# $Conf{WakeupSchedule} =3D [1..23]; # every hour except =
midnight=0A=
# $Conf{WakeupSchedule} =3D [2,4,6,8,10,12,14,16,18,20,22]; # every =
2 hours=0A=
#=0A=
# The default value is every hour except midnight.=0A=
#=0A=
$Conf{WakeupSchedule} =3D [1..23];=0A=
=0A=
#=0A=
# Maximum number of simultaneous backups to run. If there=0A=
# are no user backup requests then this is the maximum number=0A=
# of simultaneous backups.=0A=
#=0A=
$Conf{MaxBackups} =3D 4;=0A=
=0A=
#=0A=
# Additional number of simultaneous backups that users can run.=0A=
# As many as $Conf{MaxBackups} + $Conf{MaxUserBackups} requests can=0A=
# run at the same time.=0A=
#=0A=
$Conf{MaxUserBackups} =3D 4;=0A=
=0A=
#=0A=
# Maximum number of pending link commands. New backups will only be=0A=
# started if there are no more than $Conf{MaxPendingCmds} plus=0A=
# $Conf{MaxBackups} number of pending link commands, plus running jobs.=0A=
# This limit is to make sure BackupPC doesn't fall too far behind in=0A=
# running BackupPC_link commands.=0A=
#=0A=
$Conf{MaxPendingCmds} =3D 10;=0A=
=0A=
#=0A=
# Maximum number of log files we keep around in log directory.=0A=
# These files are aged nightly. A setting of 14 means the log=0A=
# directory will contain about 2 weeks of old log files, in=0A=
# particular at most the files LOG, LOG.0, LOG.1, ... LOG.13=0A=
# (except today's LOG, these files will have a .z extension if=0A=
# compression is on).=0A=
#=0A=
# If you decrease this number after BackupPC has been running for a=0A=
# while you will have to manually remove the older log files.=0A=
#=0A=
$Conf{MaxOldLogFiles} =3D 14;=0A=
=0A=
#=0A=
# Full path to the df command. Security caution: normal users=0A=
# should not allowed to write to this file or directory.=0A=
#=0A=
$Conf{DfPath} =3D '/bin/df';=0A=
=0A=
#=0A=
# Command to run df. The following variables are substituted at =
run-time:=0A=
#=0A=
# $dfPath path to df ($Conf{DfPath})=0A=
# $topDir top-level BackupPC data directory=0A=
#=0A=
$Conf{DfCmd} =3D '$dfPath $topDir';=0A=
=0A=
#=0A=
# Maximum threshold for disk utilization on the __TOPDIR__ filesystem.=0A=
# If the output from $Conf{DfPath} reports a percentage larger than=0A=
# this number then no new regularly scheduled backups will be run.=0A=
# However, user requested backups (which are usually incremental and=0A=
# tend to be small) are still performed, independent of disk usage.=0A=
# Also, currently running backups will not be terminated when the disk=0A=
# usage exceeds this number.=0A=
#=0A=
$Conf{DfMaxUsagePct} =3D 95;=0A=
=0A=
#=0A=
# How long BackupPC_trashClean sleeps in seconds between each check=0A=
# of the trash directory. Once every 5 minutes should be reasonable.=0A=
#=0A=
$Conf{TrashCleanSleepSec} =3D 300;=0A=
=0A=
#=0A=
# List of DHCP address ranges we search looking for PCs to backup.=0A=
# This is an array of hashes for each class C address range.=0A=
# This is only needed if hosts in the conf/hosts file have the=0A=
# dhcp flag set.=0A=
#=0A=
# Examples:=0A=
# # to specify 192.10.10.20 to 192.10.10.250 as the DHCP address pool=0A=
# $Conf{DHCPAddressRanges} =3D [=0A=
# {=0A=
# ipAddrBase =3D> '192.10.10',=0A=
# first =3D> 20,=0A=
# last =3D> 250,=0A=
# },=0A=
# ];=0A=
# # to specify two pools (192.10.10.20-250 and 192.10.11.10-50)=0A=
# $Conf{DHCPAddressRanges} =3D [=0A=
# {=0A=
# ipAddrBase =3D> '192.10.10',=0A=
# first =3D> 20,=0A=
# last =3D> 250,=0A=
# },=0A=
# {=0A=
# ipAddrBase =3D> '192.10.11',=0A=
# first =3D> 10,=0A=
# last =3D> 50,=0A=
# },=0A=
# ];=0A=
#=0A=
$Conf{DHCPAddressRanges} =3D [];=0A=
=0A=
#=0A=
# These configuration settings aren't used by BackupPC, but simply=0A=
# remember a few settings used by configure.pl during installation.=0A=
# These are used by configure.pl when upgrading to new versions of=0A=
# BackupPC.=0A=
#=0A=
$Conf{BackupPCUser} =3D 'backuppc';=0A=
$Conf{CgiDir} =3D '/home/httpd/shared/cgi-bin/backuppc';=0A=
$Conf{InstallDir} =3D '/etc/backuppc';=0A=
=0A=
#=0A=
# Whether BackupPC and the CGI script BackupPC_Admin verify that they=0A=
# are really running as user $Conf{BackupPCUser}. If this flag is set=0A=
# and the effective user id (euid) differs from $Conf{BackupPCUser}=0A=
# then both scripts exit with an error. This catches cases where=0A=
# BackupPC might be accidently started as root or the wrong user,=0A=
# or if the CGI script is not installed correctly.=0A=
#=0A=
$Conf{BackupPCUserVerify} =3D 1;=0A=
=0A=
#=0A=
# Maximum number of hardlinks supported by the $TopDir file system=0A=
# that BackupPC uses. Most linux or unix file systems should support=0A=
# at least 32000 hardlinks per file, or 64K in other cases. If a pool=0A=
# file already has this number of hardlinks, a new pool file is created=0A=
# so that new hardlinks can be accommodated. This limit will only=0A=
# be hit if an identical file appears at least this number of times=0A=
# across all the backups.=0A=
#=0A=
$Conf{HardLinkMax} =3D 31999;=0A=
=0A=
#########################################################################=
##=0A=
# What to backup and when to do it=0A=
# (can be overridden in the per-PC config.pl)=0A=
#########################################################################=
##=0A=
#=0A=
# Name of the host share that is backed up when using SMB. This can be
a=0A=
# string or an array of strings if there are multiple shares per host.=0A=
# Examples:=0A=
#=0A=
# $Conf{SmbShareName} =3D 'c'; # backup 'c' share=0A=
# $Conf{SmbShareName} =3D ['c', 'd']; # backup 'c' and 'd' shares=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'smb'.=0A=
#=0A=
#$Conf{SmbShareName} =3D 'C$';=0A=
$Conf{SmbShareName} =3D 'c';=0A=
=0A=
#=0A=
# Smbclient share user name. This is passed to smbclient's -U argument.=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'smb'.=0A=
#=0A=
$Conf{SmbShareUserName} =3D 'backup';=0A=
=0A=
#=0A=
# Smbclient share password. This is passed to smbclient via its PASSWD=0A=
# environment variable. There are several ways you can tell BackupPC=0A=
# the smb share password. In each case you should be very careful about=0A=
# security. If you put the password here, make sure that this file is=0A=
# not readable by regular users! See the "Setting up config.pl" section=0A=
# in the documentation for more information.=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'smb'.=0A=
#=0A=
$Conf{SmbSharePasswd} =3D 'onstream';=0A=
=0A=
#=0A=
# Which host directories to backup when using tar transport. This can =
be a=0A=
# string or an array of strings if there are multiple directories to=0A=
# backup per host. Examples:=0A=
#=0A=
# $Conf{TarShareName} =3D '/'; # backup everything=0A=
# $Conf{TarShareName} =3D '/home'; # only backup /home=0A=
# $Conf{TarShareName} =3D ['/home', '/src']; # backup /home and /src=0A=
#=0A=
# The fact this parameter is called 'TarShareName' is for historical=0A=
# consistency with the Smb transport options. You can use any valid=0A=
# directory on the client: there is no need for it to correspond to=0A=
# any Smb share or device mount point.=0A=
#=0A=
# Note also that you can also use $Conf{BackupFilesOnly} to specify=0A=
# a specific list of directories to backup. It's more efficient to=0A=
# use this option instead of $Conf{TarShareName} since a new tar is=0A=
# run for each entry in $Conf{TarShareName}.=0A=
#=0A=
# On the other hand, if you add --one-file-system to $Conf{TarClientCmd}=0A=
# you can backup each file system separately, which makes restoring one=0A=
# bad file system easier. In this case you would list all of the mount=0A=
# points here, since you can't get the same result with=0A=
# $Conf{BackupFilesOnly}:=0A=
#=0A=
# $Conf{TarShareName} =3D ['/', '/var', '/data', '/boot'];=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'tar'.=0A=
#=0A=
$Conf{TarShareName} =3D '/';=0A=
=0A=
#=0A=
# Minimum period in days between full backups. A full dump will only be=0A=
# done if at least this much time has elapsed since the last full dump,=0A=
# and at least $Conf{IncrPeriod} days has elapsed since the last=0A=
# successful dump.=0A=
#=0A=
# Typically this is set slightly less than an integer number of days.
The=0A=
# time taken for the backup, plus the granularity of =
$Conf{WakeupSchedule}=0A=
# will make the actual backup interval a bit longer.=0A=
#=0A=
# There are two special values for $Conf{FullPeriod}:=0A=
#=0A=
# -1 Don't do any regular backups on this machine. Manually=0A=
# requested backups (via the CGI interface) will still occur.=0A=
#=0A=
# -2 Don't do any backups on this machine. Manually requested=0A=
# backups (via the CGI interface) will be ignored.=0A=
#=0A=
# These special settings are useful for a client that is no longer=0A=
# being backed up (eg: a retired machine), but you wish to keep the=0A=
# last backups available for browsing or restoring to other machines.=0A=
#=0A=
# Also, you might create a virtual client (by setting =
$Conf{ClientNameAlias})=0A=
# for restoring to a DVD or permanent media and you would set=0A=
# $Conf{FullPeriod} to -2 so that it is never backed up.=0A=
#=0A=
$Conf{FullPeriod} =3D 6.97;=0A=
=0A=
#=0A=
# Minimum period in days between incremental backups (a user requested=0A=
# incremental backup will be done anytime on demand).=0A=
#=0A=
# Typically this is set slightly less than an integer number of days.
The=0A=
# time taken for the backup, plus the granularity of =
$Conf{WakeupSchedule}=0A=
# will make the actual backup interval a bit longer.=0A=
#=0A=
$Conf{IncrPeriod} =3D 0.97;=0A=
=0A=
#=0A=
# Number of full backups to keep. Must be >=3D 1.=0A=
#=0A=
# In the steady state, each time a full backup completes successfully=0A=
# the oldest one is removed. If this number is decreased, the=0A=
# extra old backups will be removed.=0A=
#=0A=
# If filling of incremental dumps is off the oldest backup always=0A=
# has to be a full (ie: filled) dump. This might mean an extra full=0A=
# dump is kept until the second oldest (incremental) dump expires.=0A=
#=0A=
$Conf{FullKeepCnt} =3D 1;=0A=
=0A=
#=0A=
# Very old full backups are removed after $Conf{FullAgeMax} days. =
However,=0A=
# we keep at least $Conf{FullKeepCntMin} full backups no matter how old=0A=
# they are.=0A=
#=0A=
$Conf{FullKeepCntMin} =3D 1;=0A=
$Conf{FullAgeMax} =3D 60;=0A=
=0A=
#=0A=
# Number of incremental backups to keep. Must be >=3D 1.=0A=
#=0A=
# In the steady state, each time an incr backup completes successfully=0A=
# the oldest one is removed. If this number is decreased, the=0A=
# extra old backups will be removed.=0A=
#=0A=
$Conf{IncrKeepCnt} =3D 6;=0A=
=0A=
#=0A=
# Very old incremental backups are removed after $Conf{IncrAgeMax} days.=0A=
# However, we keep at least $Conf{IncrKeepCntMin} incremental backups no=0A=
# matter how old they are.=0A=
#=0A=
$Conf{IncrKeepCntMin} =3D 1;=0A=
$Conf{IncrAgeMax} =3D 30;=0A=
=0A=
#=0A=
# Whether incremental backups are filled. "Filling" means that the=0A=
# most recent full (or filled) dump is merged into the new incremental=0A=
# dump using hardlinks. This makes an incremental dump look like a=0A=
# full dump. Prior to v1.03 all incremental backups were filled.=0A=
# In v1.4.0 and later the default is off.=0A=
#=0A=
# BackupPC, and the cgi interface in particular, do the right thing on=0A=
# un-filled incremental backups. It will correctly display the merged=0A=
# incremental backup with the most recent filled backup, giving the=0A=
# un-filled incremental backups a filled appearance. That means it=0A=
# invisible to the user whether incremental dumps are filled or not.=0A=
#=0A=
# Filling backups takes a little extra disk space, and it does cost=0A=
# some extra disk activity for filling, and later removal. Filling=0A=
# is no longer useful, since file mangling and compression doesn't=0A=
# make a filled backup very useful. It's likely the filling option=0A=
# will be removed from future versions: filling will be delegated to=0A=
# the display and extraction of backup data.=0A=
#=0A=
# If filling is off, BackupPC makes sure that the oldest backup is=0A=
# a full, otherwise the following incremental backups will be=0A=
# incomplete. This might mean an extra full backup has to be=0A=
# kept until the following incremental backups expire.=0A=
#=0A=
# The default is off. You can turn this on or off at any=0A=
# time without affecting existing backups.=0A=
#=0A=
$Conf{IncrFill} =3D 0;=0A=
=0A=
#=0A=
# Number of restore logs to keep. BackupPC remembers information about=0A=
# each restore request. This number per client will be kept around =
before=0A=
# the oldest ones are pruned.=0A=
#=0A=
# Note: files/dirs delivered via Zip or Tar downloads don't count as=0A=
# restores. Only the first restore option (where the files and dirs=0A=
# are written to the host) count as restores that are logged.=0A=
#=0A=
$Conf{RestoreInfoKeepCnt} =3D 10;=0A=
=0A=
#=0A=
# List of directories or files to backup. If this is defined, only
these=0A=
# directories or files will be backed up.=0A=
#=0A=
# For Smb, only one of $Conf{BackupFilesExclude} and =
$Conf{BackupFilesOnly}=0A=
# can be specified per share. If both are set for a particular share, =
then=0A=
# $Conf{BackupFilesOnly} takes precedence and $Conf{BackupFilesExclude}=0A=
# is ignored.=0A=
#=0A=
# This can be set to a string, an array of strings, or, in the case=0A=
# of multiple shares, a hash of strings or arrays. A hash is used=0A=
# to give a list of directories or files to backup for each share=0A=
# (the share name is the key). If this is set to just a string or=0A=
# array, and $Conf{SmbShareName} contains multiple share names, then=0A=
# the setting is assumed to apply to only the first share name.=0A=
#=0A=
# Examples:=0A=
# $Conf{BackupFilesOnly} =3D '/myFiles';=0A=
# $Conf{BackupFilesOnly} =3D ['/myFiles']; # same as first
example=0A=
# $Conf{BackupFilesOnly} =3D ['/myFiles', '/important'];=0A=
# $Conf{BackupFilesOnly} =3D {=0A=
# 'c' =3D> ['/myFiles', '/important'], # these are for 'c' =
share=0A=
# 'd' =3D> ['/moreFiles', '/archive'], # these are for 'd' =
share=0A=
# };=0A=
#=0A=
$Conf{BackupFilesOnly} =3D undef;=0A=
=0A=
#=0A=
# List of directories or files to exclude from the backup. For Smb,=0A=
# only one of $Conf{BackupFilesExclude} and $Conf{BackupFilesOnly}=0A=
# can be specified per share. If both are set for a particular share,=0A=
# then $Conf{BackupFilesOnly} takes precedence and=0A=
# $Conf{BackupFilesExclude} is ignored.=0A=
#=0A=
# This can be set to a string, an array of strings, or, in the case=0A=
# of multiple shares, a hash of strings or arrays. A hash is used=0A=
# to give a list of directories or files to exclude for each share=0A=
# (the share name is the key). If this is set to just a string or=0A=
# array, and $Conf{SmbShareName} contains multiple share names, then=0A=
# the setting is assumed to apply to only the first share name.=0A=
#=0A=
# The exact behavior is determined by the underlying transport program,=0A=
# smbclient or tar. For smbclient the exlclude file list is passed into=0A=
# the X option. Simple shell wild-cards using "*" or "?" are allowed.=0A=
#=0A=
# For tar, if the exclude file contains a "/" it is assumed to be =
anchored=0A=
# at the start of the string. Since all the tar paths start with "./",=0A=
# BackupPC prepends a "." if the exclude file starts with a "/". Note=0A=
# that GNU tar version >=3D 1.13.7 is required for the exclude option to=0A=
# work correctly. For linux or unix machines you should add=0A=
# "/proc" to $Conf{BackupFilesExclude} unless you have specified=0A=
# --one-file-system in $Conf{TarClientCmd} or --one-file-system in=0A=
# $Conf{RsyncArgs}. Also, for tar, do not use a trailing "/" in=0A=
# the directory name: a trailing "/" causes the name to not match=0A=
# and the directory will not be excluded.=0A=
#=0A=
# Examples:=0A=
# $Conf{BackupFilesExclude} =3D '/temp';=0A=
# $Conf{BackupFilesExclude} =3D ['/temp']; # same as first
example=0A=
# $Conf{BackupFilesExclude} =3D ['/temp', '/winnt/tmp'];=0A=
# $Conf{BackupFilesExclude} =3D {=0A=
# 'c' =3D> ['/temp', '/winnt/tmp'], # these are for 'c' =
share=0A=
# 'd' =3D> ['/junk', '/dont_back_this_up'], # these are for 'd' =
share=0A=
# };=0A=
#=0A=
$Conf{BackupFilesExclude} =3D ['/"Program Files"'];=0A=
=0A=
#=0A=
# PCs that are always or often on the network can be backed up after=0A=
# hours, to reduce PC, network and server load during working hours. For=0A=
# each PC a count of consecutive good pings is maintained. Once a PC has=0A=
# at least $Conf{BlackoutGoodCnt} consecutive good pings it is subject=0A=
# to "blackout" and not backed up during hours and days specified by=0A=
# $Conf{BlackoutWeekDays}, $Conf{BlackoutHourBegin} and=0A=
# $Conf{BlackoutHourEnd}.=0A=
#=0A=
# To allow for periodic rebooting of a PC or other brief periods when a=0A=
# PC is not on the network, a number of consecutive bad pings is allowed=0A=
# before the good ping count is reset. This parameter is=0A=
# $Conf{BlackoutBadPingLimit}.=0A=
#=0A=
# Note that bad and good pings don't occur with the same interval. If a=0A=
# machine is always on the network, it will only be pinged roughly once=0A=
# every $Conf{IncrPeriod} (eg: once per day). So a setting for=0A=
# $Conf{BlackoutGoodCnt} of 7 means it will take around 7 days for a=0A=
# machine to be subject to blackout. On the other hand, if a ping is=0A=
# failed, it will be retried roughly every time BackupPC wakes up, eg,=0A=
# every one or two hours. So a setting for $Conf{BlackoutBadPingLimit}
of=0A=
# 3 means that the PC will lose its blackout status after 3-6 hours of=0A=
# unavailability.=0A=
#=0A=
# To disable the blackout feature set $Conf{BlackoutGoodCnt} to a =
negative=0A=
# value. A value of 0 will make all machines subject to blackout. But=0A=
# if you don't want to do any backups during the day it would be easier=0A=
# to just set $Conf{WakeupSchedule} to a restricted schedule.=0A=
#=0A=
$Conf{BlackoutBadPingLimit} =3D 3;=0A=
$Conf{BlackoutGoodCnt} =3D 7;=0A=
=0A=
#=0A=
# The default settings specify the blackout period from 7:00am to=0A=
# 7:30pm local time on Mon-Fri. For $Conf{BlackoutWeekDays},=0A=
# 0 is Sunday, 1 is Monday etc.=0A=
#=0A=
$Conf{BlackoutHourBegin} =3D 7.0;=0A=
$Conf{BlackoutHourEnd} =3D 19.5;=0A=
$Conf{BlackoutWeekDays} =3D [1, 2, 3, 4, 5];=0A=
=0A=
# =0A=
# A backup of a share that has zero files is considered fatal. This is=0A=
# used to catch miscellaneous Xfer errors that result in no files being=0A=
# backed up. If you have shares that might be empty (and therefore an=0A=
# empty backup is valid) you should set this flag to 0.=0A=
# =0A=
$Conf{BackupZeroFilesIsFatal} =3D 1;=0A=
=0A=
#########################################################################=
##=0A=
# General per-PC configuration settings=0A=
# (can be overridden in the per-PC config.pl)=0A=
#########################################################################=
##=0A=
#=0A=
# What transport method to use to backup each host. If you have=0A=
# a mixed set of WinXX and linux/unix hosts you will need to override=0A=
# this in the per-PC config.pl.=0A=
#=0A=
# The valid values are:=0A=
#=0A=
# - 'smb': backup and restore via smbclient and the SMB protocol.=0A=
# Best choice for WinXX.=0A=
#=0A=
# - 'rsync': backup and restore via rsync (via rsh or ssh).=0A=
# Best choice for linux/unix. Can also work on WinXX.=0A=
#=0A=
# - 'rsyncd': backup and restre via rsync daemon on the client.=0A=
# Best choice for linux/unix if you have rsyncd running on=0A=
# the client. Can also work on WinXX.=0A=
#=0A=
# - 'tar': backup and restore via tar, tar over ssh, rsh or nfs.=0A=
# Good choice for linux/unix.=0A=
#=0A=
$Conf{XferMethod} =3D 'smb';=0A=
=0A=
#=0A=
# Full path for smbclient. Security caution: normal users should not=0A=
# allowed to write to this file or directory.=0A=
#=0A=
# smbclient is from the Samba distribution. smbclient is used to=0A=
# actually extract the incremental or full dump of the share filesystem=0A=
# from the PC.=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'smb'.=0A=
#=0A=
$Conf{SmbClientPath} =3D '/usr/bin/smbclient';=0A=
=0A=
#=0A=
# Commands to run smbclient for a full dump, incremental dump or a =
restore.=0A=
# This setting only matters if $Conf{XferMethod} =3D 'smb'.=0A=
#=0A=
# The following variables are substituted at run-time:=0A=
#=0A=
# $smbClientPath same as $Conf{SmbClientPath}=0A=
# $host host to backup/restore=0A=
# $hostIP host IP address=0A=
# $shareName share name=0A=
# $userName user name=0A=
# $fileList list of files to backup (based on exclude/include)=0A=
# $I_option optional -I option to smbclient=0A=
# $X_option exclude option (if $fileList is an exclude list)=0A=
# $timeStampFile start time for incremental dump=0A=
#=0A=
$Conf{SmbClientFullCmd} =3D '$smbClientPath \\\\$host\\$shareName'=0A=
. ' $I_option -U $userName -E -N -d 1'=0A=
. ' -c tarmode\\ full -Tc$X_option - $fileList';=0A=
=0A=
$Conf{SmbClientIncrCmd} =3D '$smbClientPath \\\\$host\\$shareName'=0A=
. ' $I_option -U $userName -E -N -d 1'=0A=
. ' -c tarmode\\ full -TcN$X_option $timeStampFile - $fileList';=0A=
=0A=
$Conf{SmbClientRestoreCmd} =3D '$smbClientPath \\\\$host\\$shareName'=0A=
. ' $I_option -U $userName -E -N -d 1'=0A=
. ' -c tarmode\\ full -Tx -';=0A=
=0A=
#=0A=
# Full command to run tar on the client. GNU tar is required. You will=0A=
# need to fill in the correct paths for ssh2 on the local host (server)=0A=
# and GNU tar on the client. Security caution: normal users should not=0A=
# allowed to write to these executable files or directories.=0A=
#=0A=
# See the documentation for more information about setting up ssh2 keys.=0A=
#=0A=
# If you plan to use NFS then tar just runs locally and ssh2 is not =
needed.=0A=
# For example, assuming the client filesystem is mounted below =
/mnt/hostName,=0A=
# you could use something like:=0A=
#=0A=
# $Conf{TarClientCmd} =3D '$tarPath -c -v -f - -C =
/mnt/$host/$shareName'=0A=
# . ' --totals';=0A=
#=0A=
# In the case of NFS or rsh you need to make sure BackupPC's privileges=0A=
# are sufficient to read all the files you want to backup. Also, you=0A=
# will probably want to add "/proc" to $Conf{BackupFilesExclude}.=0A=
#=0A=
# The following variables are substituted at run-time:=0A=
#=0A=
# $host host name=0A=
# $hostIP host's IP address=0A=
# $incrDate newer-than date for incremental backups=0A=
# $shareName share name to backup (ie: top-level directory path)=0A=
# $fileList specific files to backup or exclude=0A=
# $tarPath same as $Conf{TarClientPath}=0A=
# $sshPath same as $Conf{SshPath}=0A=
#=0A=
# If a variable is followed by a "+" it is shell escaped. This is=0A=
# necessary for the command part of ssh or rsh, since it ends up=0A=
# getting passed through the shell.=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'tar'.=0A=
#=0A=
$Conf{TarClientCmd} =3D '$sshPath -q -n -l root $host'=0A=
. ' $tarPath -c -v -f - -C $shareName+'=0A=
. ' --totals';=0A=
=0A=
#=0A=
# Extra tar arguments for full backups. Several variables are =
substituted at=0A=
# run-time. See $Conf{TarClientCmd} for the list of variable =
substitutions.=0A=
#=0A=
# If you are running tar locally (ie: without rsh or ssh) then remove
the=0A=
# "+" so that the argument is no longer shell escaped.=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'tar'.=0A=
#=0A=
$Conf{TarFullArgs} =3D '$fileList+';=0A=
=0A=
#=0A=
# Extra tar arguments for incr backups. Several variables are =
substituted at=0A=
# run-time. See $Conf{TarClientCmd} for the list of variable =
substitutions.=0A=
#=0A=
# Note that GNU tar has several methods for specifying incremental =
backups,=0A=
# including:=0A=
#=0A=
# --newer-mtime $incrDate+=0A=
# This causes a file to be included if the modification time is=0A=
# later than $incrDate (meaning its contents might have =
changed).=0A=
# But changes in the ownership or modes will not qualify the=0A=
# file to be included in an incremental.=0A=
#=0A=
# --newer=3D$incrDate+=0A=
# This causes the file to be included if any attribute of the=0A=
# file is later than $incrDate, meaning either attributes or=0A=
# the modification time. This is the default method. Do=0A=
# not use --atime-preserve in $Conf{TarClientCmd} above,=0A=
# otherwise resetting the atime (access time) counts as an=0A=
# attribute change, meaning the file will always be included=0A=
# in each new incremental dump.=0A=
#=0A=
# If you are running tar locally (ie: without rsh or ssh) then remove
the=0A=
# "+" so that the argument is no longer shell escaped.=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'tar'.=0A=
#=0A=
$Conf{TarIncrArgs} =3D '--newer=3D$incrDate+ $fileList+';=0A=
=0A=
#=0A=
# Full command to run tar for restore on the client. GNU tar is =
required.=0A=
# This can be the same as $Conf{TarClientCmd}, with tar's -c replaced by =
-x=0A=
# and ssh's -n removed.=0A=
#=0A=
# See $Conf{TarClientCmd} for full details.=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D "tar".=0A=
#=0A=
$Conf{TarClientRestoreCmd} =3D '$sshPath -q -l root $host'=0A=
. ' $tarPath -x -p --numeric-owner --same-owner'=0A=
. ' -v -f - -C $shareName+';=0A=
=0A=
#=0A=
# Full path for tar on the client. Security caution: normal users should =
not=0A=
# allowed to write to this file or directory.=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'tar'.=0A=
#=0A=
$Conf{TarClientPath} =3D '/bin/gtar';=0A=
=0A=
#=0A=
# Path to rsync executable on the client=0A=
#=0A=
$Conf{RsyncClientPath} =3D '/usr/bin/rsync';=0A=
=0A=
#=0A=
# Full command to run rsync on the client machine. The following =
variables=0A=
# are substituted at run-time:=0A=
#=0A=
# $host host name being backed up=0A=
# $hostIP host's IP address=0A=
# $shareName share name to backup (ie: top-level directory =
path)=0A=
# $rsyncPath same as $Conf{RsyncClientPath}=0A=
# $sshPath same as $Conf{SshPath}=0A=
# $argList argument list, built from $Conf{RsyncArgs},=0A=
# $shareName, $Conf{BackupFilesExclude} and=0A=
# $Conf{BackupFilesOnly}=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'rsync'.=0A=
#=0A=
$Conf{RsyncClientCmd} =3D '$sshPath -l root $host $rsyncPath $argList+';=0A=
=0A=
#=0A=
# Full command to run rsync for restore on the client. The following=0A=
# variables are substituted at run-time:=0A=
#=0A=
# $host host name being backed up=0A=
# $hostIP host's IP address=0A=
# $shareName share name to backup (ie: top-level directory =
path)=0A=
# $rsyncPath same as $Conf{RsyncClientPath}=0A=
# $sshPath same as $Conf{SshPath}=0A=
# $argList argument list, built from $Conf{RsyncArgs},=0A=
# $shareName, $Conf{BackupFilesExclude} and=0A=
# $Conf{BackupFilesOnly}=0A=
#=0A=
# This setting only matters if $Conf{XferMethod} =3D 'rsync'.=0A=
#=0A=
$Conf{RsyncClientRestoreCmd} =3D '$sshPath -l root $host $rsyncPath =
$argList+';=0A=
=0A=
#=0A=
# Share name to backup. For $Conf{XferMethod} =3D "rsync" this should=0A=
# be a file system path, eg '/' or '/home'.=0A=
#=0A=
# For $Conf{XferMethod} =3D "rsyncd" this should be the name of the =
module=0A=
# to backup (ie: the name from /etc/rsynd.conf).=0A=
#=0A=
# This can also be a list of multiple file system paths or modules.=0A=
# For example, by adding --one-file-system to $Conf{RsyncArgs} you=0A=
# can backup each file system separately, which makes restoring one=0A=
# bad file system easier. In this case you would list all of the mount=0A=
# points:=0A=
#=0A=
# $Conf{RsyncShareName} =3D ['/', '/var', '/data', '/boot'];=0A=
#=0A=
$Conf{RsyncShareName} =3D '/';=0A=
=0A=
#=0A=
# Rsync daemon port on the client, for $Conf{XferMethod} =3D "rsyncd".=0A=
#=0A=
$Conf{RsyncdClientPort} =3D 873;=0A=
=0A=
#=0A=
# Rsync daemon user name on client, for $Conf{XferMethod} =3D "rsyncd".=0A=
# The user name and password are stored on the client in whatever file=0A=
# the "secrets file" parameter in rsyncd.conf points to=0A=
# (eg: /etc/rsyncd.secrets).=0A=
#=0A=
$Conf{RsyncdUserName} =3D '';=0A=
=0A=
#=0A=
# Rsync daemon user name on client, for $Conf{XferMethod} =3D "rsyncd".=0A=
# The user name and password are stored on the client in whatever file=0A=
# the "secrets file" parameter in rsyncd.conf points to=0A=
# (eg: /etc/rsyncd.secrets).=0A=
#=0A=
$Conf{RsyncdPasswd} =3D '';=0A=
=0A=
#=0A=
# Whether authentication is mandatory when connecting to the client's=0A=
# rsyncd. By default this is on, ensuring that BackupPC will refuse to=0A=
# connect to an rsyncd on the client that is not password protected.=0A=
# Turn off at your own risk.=0A=
#=0A=
$Conf{RsyncdAuthRequired} =3D 1;=0A=
=0A=
#=0A=
# Arguments to rsync for backup. Do not edit the first set unless you=0A=
# have a thorough understanding of how File::RsyncP works.=0A=
#=0A=
# Examples of additional arguments that should work are =
--exclude/--include,=0A=
# eg:=0A=
#=0A=
# $Conf{RsyncArgs} =3D [=0A=
# # original arguments here=0A=
# '-v',=0A=
# '--exclude', '/proc',=0A=
# '--exclude', '*.tmp',=0A=
# ];=0A=
#=0A=
$Conf{RsyncArgs} =3D [=0A=
#=0A=
# Do not edit these!=0A=
#=0A=
'--numeric-ids',=0A=
'--perms',=0A=
'--owner',=0A=
'--group',=0A=
'--devices',=0A=
'--links',=0A=
'--times',=0A=
'--block-size=3D2048',=0A=
'--recursive',=0A=
#=0A=
# Add additional arguments here=0A=
#=0A=
];=0A=
=0A=
#=0A=
# Arguments to rsync for restore. Do not edit the first set unless you=0A=
# have a thorough understanding of how File::RsyncP works.=0A=
#=0A=
#=0A=
$Conf{RsyncRestoreArgs} =3D [=0A=
#=0A=
# Do not edit these!=0A=
#=0A=
"--numeric-ids",=0A=
"--perms",=0A=
"--owner",=0A=
"--group",=0A=
"--devices",=0A=
"--links",=0A=
"--times",=0A=
"--block-size=3D2048",=0A=
"--relative",=0A=
"--ignore-times",=0A=
"--recursive",=0A=
#=0A=
# Add additional arguments here=0A=
#=0A=
];=0A=
=0A=
#=0A=
# Amount of verbosity in Rsync Xfer log files. 0 means be quiet,=0A=
# 1 will give will give one line per file, 2 will also show skipped=0A=
# files on incrementals, higher values give more output. 10 will=0A=
# include byte dumps of all data read/written, which will make the=0A=
# log files huge.=0A=
#=0A=
$Conf{RsyncLogLevel} =3D 1;=0A=
=0A=
#=0A=
# Full path for ssh. Security caution: normal users should not=0A=
# allowed to write to this file or directory.=0A=
#=0A=
$Conf{SshPath} =3D '/usr/bin/ssh';=0A=
=0A=
#=0A=
# Full path for nmblookup. Security caution: normal users should not=0A=
# allowed to write to this file or directory.=0A=
#=0A=
# nmblookup is from the Samba distribution. nmblookup is used to get the=0A=
# netbios name, necessary for DHCP hosts.=0A=
#=0A=
$Conf{NmbLookupPath} =3D '/usr/bin/nmblookup';=0A=
=0A=
#=0A=
# NmbLookup command. Given an IP address, does an nmblookup on that=0A=
# IP address. The following variables are substituted at run-time:=0A=
#=0A=
# $nmbLookupPath path to nmblookup ($Conf{NmbLookupPath})=0A=
# $host IP address=0A=
#=0A=
# This command is only used for DHCP hosts: given an IP address, this=0A=
# command should try to find its NetBios name.=0A=
#=0A=
$Conf{NmbLookupCmd} =3D '$nmbLookupPath -A $host';=0A=
=0A=
#=0A=
# NmbLookup command. Given a netbios name, finds that host by doing=0A=
# a NetBios lookup. Several variables are substituted at run-time:=0A=
#=0A=
# $nmbLookupPath path to nmblookup ($Conf{NmbLookupPath})=0A=
# $host NetBios name=0A=
#=0A=
# In some cases you might need to change the broadcast address, for=0A=
# example if nmblookup uses 192.168.255.255 by default and you find=0A=
# that doesn't work, try 192.168.1.255 (or your equivalent class C=0A=
# address) using the -B option:=0A=
#=0A=
# $Conf{NmbLookupFindHostCmd} =3D '$nmbLookupPath -B 192.168.1.255 =
$host';=0A=
#=0A=
# If you use a WINS server and your machines don't respond to=0A=
# multicast NetBios requests you can use this (replace 1.2.3.4=0A=
# with the IP address of your WINS server):=0A=
#=0A=
# $Conf{NmbLookupFindHostCmd} =3D '$nmbLookupPath -R -U 1.2.3.4 =
$host';=0A=
#=0A=
# This is preferred over multicast since it minimizes network traffic.=0A=
#=0A=
# Experiment manually for your site to see what form of nmblookup
command=0A=
# works.=0A=
#=0A=
$Conf{NmbLookupFindHostCmd} =3D '$nmbLookupPath $host';=0A=
=0A=
#=0A=
# For fixed IP address hosts, BackupPC_dump can also verify the netbios=0A=
# name to ensure it matches the host name. An error is generated if=0A=
# they do not match. Typically this flag is off. But if you are going=0A=
# to transition a bunch of machines from fixed host addresses to DHCP,=0A=
# setting this flag is a great way to verify that the machines have=0A=
# their netbios name set correctly before turning on DCHP.=0A=
#=0A=
$Conf{FixedIPNetBiosNameCheck} =3D 0;=0A=
=0A=
#=0A=
# Full path to the ping command. Security caution: normal users=0A=
# should not be allowed to write to this file or directory.=0A=
#=0A=
# If you want to disable ping checking, set this to some program=0A=
# that exits with 0 status, eg:=0A=
#=0A=
# $Conf{PingPath} =3D '/bin/echo';=0A=
#=0A=
$Conf{PingPath} =3D '/bin/ping';=0A=
=0A=
#=0A=
# Ping command. The following variables are substituted at run-time:=0A=
#=0A=
# $pingPath path to ping ($Conf{PingPath})=0A=
# $host host name=0A=
#=0A=
# Wade Brown reports that on solaris 2.6 and 2.7 ping -s returns the =
wrong=0A=
# exit status (0 even on failure). Replace with "ping $host 1", which=0A=
# gets the correct exit status but we don't get the round-trip time.=0A=
#=0A=
$Conf{PingCmd} =3D '$pingPath -c 1 -w 3 $host';=0A=
=0A=
#=0A=
# Compression level to use on files. 0 means no compression. =
Compression=0A=
# levels can be from 1 (least cpu time, slightly worse compression) to=0A=
# 9 (most cpu time, slightly better compression). The recommended value=0A=
# is 3. Changing to 5, for example, will take maybe 20% more cpu time=0A=
# and will get another 2-3% additional compression. See the zlib=0A=
# documentation for more information about compression levels.=0A=
#=0A=
# Changing compression on or off after backups have already been done=0A=
# will require both compressed and uncompressed pool files to be stored.=0A=
# This will increase the pool storage requirements, at least until all=0A=
# the old backups expire and are deleted.=0A=
#=0A=
# It is ok to change the compression value (from one non-zero value to=0A=
# another non-zero value) after dumps are already done. Since BackupPC=0A=
# matches pool files by comparing the uncompressed versions, it will =
still=0A=
# correctly match new incoming files against existing pool files. The=0A=
# new compression level will take effect only for new files that are=0A=
# newly compressed and added to the pool.=0A=
#=0A=
# If compression was off and you are enabling compression for the first=0A=
# time you can use the BackupPC_compressPool utility to compress the=0A=
# pool. This avoids having the pool grow to accommodate both compressed=0A=
# and uncompressed backups. See the documentation for more information.=0A=
#=0A=
# Note: compression needs the Compress::Zlib perl library. If the=0A=
# Compress::Zlib library can't be found then $Conf{CompressLevel} is=0A=
# forced to 0 (compression off).=0A=
#=0A=
$Conf{CompressLevel} =3D 1;=0A=
=0A=
#=0A=
# Maximum round-trip ping time in milliseconds. This threshold is set=0A=
# to avoid backing up PCs that are remotely connected through WAN or=0A=
# dialup connections. The output from ping -s (assuming it is supported=0A=
# on your system) is used to check the round-trip packet time. On your=0A=
# local LAN round-trip times should be much less than 20msec. On most=0A=
# WAN or dialup connections the round-trip time will be typically more=0A=
# than 20msec. Tune if necessary.=0A=
#=0A=
$Conf{PingMaxMsec} =3D 20;=0A=
=0A=
#=0A=
# Timeout in seconds when listening for the transport program's=0A=
# (smbclient, tar etc) stdout. If no output is received during this=0A=
# time, then it is assumed that something has wedged during a backup,=0A=
# and the backup is terminated.=0A=
#=0A=
# Note that stdout buffering combined with huge files being backed up=0A=
# could cause longish delays in the output from smbclient that=0A=
# BackupPC_dump sees, so in rare cases you might want to increase=0A=
# this value.=0A=
#=0A=
# Despite the name, this parameter sets the timeout for all transport=0A=
# methods (tar, smb etc).=0A=
#=0A=
$Conf{ClientTimeout} =3D 7200;=0A=
=0A=
#=0A=
# Maximum number of log files we keep around in each PC's directory=0A=
# (ie: pc/$host). These files are aged monthly. A setting of 12=0A=
# means there will be at most the files LOG, LOG.0, LOG.1, ... LOG.11=0A=
# in the pc/$host directory (ie: about a years worth). (Except this=0A=
# month's LOG, these files will have a .z extension if compression=0A=
# is on).=0A=
#=0A=
# If you decrease this number after BackupPC has been running for a=0A=
# while you will have to manually remove the older log files.=0A=
#=0A=
$Conf{MaxOldPerPCLogFiles} =3D 12;=0A=
=0A=
#=0A=
# Optional commands to run before and after dumps and restores.=0A=
# Stdout from these commands will be written to the Xfer (or Restore)=0A=
# log file. One example of using these commands would be to=0A=
# shut down and restart a database server, or to dump a database=0A=
# to files for backup. Example:=0A=
#=0A=
# $Conf{DumpPreUserCmd} =3D '$sshPath -l root $host =
/usr/bin/dumpMysql';=0A=
#=0A=
# The following variable substitutions are made at run time for=0A=
# $Conf{DumpPreUserCmd} and $Conf{DumpPostUserCmd}:=0A=
#=0A=
# $type type of dump (incr or full)=0A=
# $xferOK 1 if the dump succeeded, 0 if it didn't=0A=
# $client client name being backed up=0A=
# $host host name (could be different from client name if=0A=
# $Conf{ClientNameAlias} is set)=0A=
# $hostIP IP address of host=0A=
# $user user name from the hosts file=0A=
# $moreUsers list of additional users from the hosts file=0A=
# $share the first share name=0A=
# $shares list of all the share names=0A=
# $XferMethod value of $Conf{XferMethod} (eg: tar, rsync, smb)=0A=
# $sshPath value of $Conf{SshPath},=0A=
#=0A=
# The following variable substitutions are made at run time for=0A=
# $Conf{RestorePreUserCmd} and $Conf{RestorePostUserCmd}:=0A=
#=0A=
# $client client name being backed up=0A=
# $xferOK 1 if the restore succeeded, 0 if it didn't=0A=
# $host host name (could be different from client name if=0A=
# $Conf{ClientNameAlias} is set)=0A=
# $hostIP IP address of host=0A=
# $user user name from the hosts file=0A=
# $moreUsers list of additional users from the hosts file=0A=
# $share the first share name=0A=
# $XferMethod value of $Conf{XferMethod} (eg: tar, rsync, smb)=0A=
# $sshPath value of $Conf{SshPath},=0A=
# $type set to "restore"=0A=
# $bkupSrcHost host name of the restore source=0A=
# $bkupSrcShare share name of the restore source=0A=
# $bkupSrcNum backup number of the restore source=0A=
# $pathHdrSrc common starting path of restore source=0A=
# $pathHdrDest common starting path of destination=0A=
# $fileList list of files being restored=0A=
#=0A=
$Conf{DumpPreUserCmd} =3D undef;=0A=
$Conf{DumpPostUserCmd} =3D undef;=0A=
$Conf{RestorePreUserCmd} =3D undef;=0A=
$Conf{RestorePostUserCmd} =3D undef;=0A=
=0A=
#=0A=
# Override the client's host name. This allows multiple clients=0A=
# to all refer to the same physical host. This should only be=0A=
# set in the per-PC config file and is only used by BackupPC at=0A=
# the last moment prior to generating the command used to backup=0A=
# that machine (ie: the value of $Conf{ClientNameAlias} is invisible=0A=
# everywhere else in BackupPC). The setting can be a host name or=0A=
# IP address, eg:=0A=
#=0A=
# $Conf{ClientNameAlias} =3D 'realHostName';=0A=
# $Conf{ClientNameAlias} =3D '192.1.1.15';=0A=
#=0A=
# will cause the relevant smb/tar/rsync backup/restore commands to be=0A=
# directed to realHostName, not the client name.=0A=
#=0A=
# Note: this setting doesn't work for hosts with DHCP set to 1.=0A=
#=0A=
$Conf{ClientNameAlias} =3D undef;=0A=
=0A=
#=0A=
# Advanced option for asking BackupPC to load additional perl modules.=0A=
# Can be a list (array ref) of module names to load at startup.=0A=
#=0A=
$Conf{PerlModuleLoad} =3D undef;=0A=
=0A=
#########################################################################=
##=0A=
# Email reminders, status and messages=0A=
# (can be overridden in the per-PC config.pl)=0A=
#########################################################################=
##=0A=
#=0A=
# Full path to the sendmail command. Security caution: normal users=0A=
# should not allowed to write to this file or directory.=0A=
#=0A=
$Conf{SendmailPath} =3D '/usr/sbin/sendmail';=0A=
=0A=
#=0A=
# Minimum period between consecutive emails to a single user.=0A=
# This tries to keep annoying email to users to a reasonable=0A=
# level. Email checks are done nightly, so this number is effectively=0A=
# rounded up (ie: 2.5 means a user will never receive email more=0A=
# than once every 3 days).=0A=
#=0A=
$Conf{EMailNotifyMinDays} =3D 2.5;=0A=
=0A=
#=0A=
# Name to use as the "from" name for email. Depending upon your mail=0A=
# handler this is either a plain name (eg: "admin") or a fully-qualified=0A=
# name (eg: "admin < at > mydomain.com").=0A=
#=0A=
$Conf{EMailFromUserName} =3D 'backuppc';=0A=
=0A=
#=0A=
# Destination address to an administrative user who will receive a=0A=
# nightly
