Maarten te Paske wrote:
>
>>> I do not really consider this an advantage. Either way you have to
>>> install and configure a client: rsync or bacula-fd.
>> Most unix-like systems already have sshd, rsync and tar installed and
>> windows can use the admin file shares for clientless backup.
>
> Even if you have rsync installed (which I don't install by default on
> any server installation) you need client side configuration. At least, I
> do the following on each BackupPC client:
>
> - Create a local user that can run rsync via sudo
> - Restrict the commands that can be run to 'sudo rsync' in the
> authorized_keys file.
> - Restrict SSH connections to the hostname of the BackupPC server in the
> authorized_keys file.
I normally have sshd/rsync configured for content management on all
machines anyway, and the only extra configuration is to add the
authorized key for backuppc, which you can do through a script that
prompts for the password for the connection that installs the key.
> So my point is, with both solutions it requires some work. Unless you
> use "admin file shares for clientless backup", but I'm not quite sure
> what you mean with that.
Windows always exports hidden file shares for each drive (C$, D$, etc.)
that you can access from a login with administrator or backup user rights.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
