Hello. The server for my LAN has "user" stuff on it, and it makes more sense to back it up to some other machine, and then leave the server to backup all the other machines. But, the server is due for hardware upgrades, so I am starting with BackupPC from the "other" machine.
The intention is to have two users (backuppc1 and backuppc2) which are doing the backups from different machines. I've read about doing SSH logins via keys without passphrases, but until yesterday, never set one up. I have gotten far enough along in this process, that looking at http://localhost/backuppc/ with a web browser made sense. The lead page said the server was down. Most of my machines have multiple partitions on their filesystems, such as a /var/log partition. The Debian directory /var/lib/backuppc was changed to be a symlink to /home/backuppc based on advice in config.pl. The /home/backuppc partition is a btrfs RAID-10. Trying to start the BackupPC service manually, I am getting an error about not being able to set up a trial hard link between /var/lib/backuppc/pc/ and /var/lib/backuppc/cpool. I thought it a little odd that something would want to hardlink to a directory, but it does appear to cause an error. As near as I can tell, hard links to directories are not good ideas. So, perhaps I made some error in editing config.pl which precipitated this? I wanted to try and reduce the impact of having this key login, so after some looking around, I decided to try "only". http://at.magma-soft.at/sw/blog/posts/The_Only_Way_For_SSH_Forced_Commands/ At first just with shell session type things. I could have it connect to to the "server" and if I gave it a "legal" command, I would see that it connected in auth.log and that the "logger" program I was running would put a message in syslog. If I gave it a command that wasn't "legal" (like echo), there were entries in auth.log, and nothing in syslog. Then on the server (to backup) I set up sudo/sudoers such that this ordinary user could use sudo to do a passwordless spawning of logger to put a message in my syslog. And that works. What was next was to see if rsync could work. And so I stumble into this pc/cpool thing. I was expecting that there could be some problems with getting --rsync-path="/usr/bin/sudo /usr/bin/rsync", but I think your config.pl (or an email in your archives?) file talks about setting RSyncClientPath to this string. Other backup packages also mention using sudo in this way, but there is quoting/escape issues. One place had to put two backslashes in front of the space, inside of the double quoted string to get things to propagate to the client. I.e.: --rpath-path="/usr/bin/sudo\\ /usr/bin/rsync" There doesn't seem to be any special notes in config.pl at this point about this being needed or not. Thanks for any light you might shed on this. Gord _______________________________________________ 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/
