The method I use is that I use rsync+ssh. I then create a regular backuppc
user and limit sudo access to the tools needed to perform the backup, plus
anything needed to be done as root in the pre/post backup scripts, such as
my dbdump script. Here is my /etc/sudoers.d/backuppc:
# This file
The method I use is that I use rsync+ssh. I then create a regular backuppc
user and limit sudo access to the tools needed to perform the backup, plus
anything needed to be done as root in the pre/post backup scripts, such as
my dbdump script. Here is my /etc/sudoers.d/backuppc:
# This file is
Hi,
I can understand the question. If BackupPC will use root permission,
your BackupPC will become No. 1 target. Because when the attacker
controls your BackupPC, she can access every box within your network
as root. Nothing you really want. And in business, you will have
multiple sys-admins..
On Linux, how is communication between the clients and the backup
server achieved as far as security? Does the backup server pull or do
the clients push and as which user?
Can the web server reside on a different system than the backup server?
- Grant
On Sun, 30 Jun 2013 01:17:04 -0700 Grant emailgr...@gmail.com wrote:
On Linux, how is communication between the clients and the backup
server achieved as far as security? Does the backup server pull or do
the clients push and as which user?
This depends on the transfer method:
- tar and
On Linux, how is communication between the clients and the backup
server achieved as far as security? Does the backup server pull or do
the clients push and as which user?
This depends on the transfer method:
- tar and rsync tunnel their data over ssh - secure.
I would use this.
And as