I came to the conclusion that tar was actually a faster way to do backups on
the local system. Less CPU usage, and bandwidth is not a problem. YMMV.
You do need to use sudo in order to make sure you can access all the files,
however, so add a couple of lines like this to your /etc/sudoers:
# allow backuppc to run as root, in order to get all the files
backuppc ALL=NOPASSWD: /bin/tar
here's my localhost.pl file:
#
# Local server backup of /etc as user backuppc
#
$Conf{XferMethod} = 'tar';
# let it back itself up anytime it wants to.
$Conf{BlackoutPeriods} = [];
$Conf{TarShareName} = ['/'];
$Conf{BackupFilesExclude} = ['/proc', '/sys', '/var/lib/backuppc',
'/var/log', '/tmp', '/var/tmp', '/mnt', '/media'];
$Conf{TarClientCmd} = '/usr/bin/env LC_ALL=C /usr/bin/sudo $tarPath -c -v -f
- -C $shareName --totals';
# remove extra shell escapes ($fileList+ etc.) that are
# needed for remote backups but may break local ones
$Conf{TarFullArgs} = '$fileList';
$Conf{TarIncrArgs} = '--newer=$incrDate $fileList';
# turning off compression on these files, so they can be recovered without
# backuppc.
# wouldn't make sense to need your backup server,
# in order to recover your backup server, now would it?
$Conf{CompressLevel} = 0;
--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
