From: Bob W. <re...@be...> - 2010-07-05 12:54:05
|
On 07/04/2010 04:03 PM, Matthias Meyer wrote: > Bob Wooden wrote: > > >> On the server, I would run the troubleshoot command: >> >> 'sudo -u backuppc /usr/share/backuppc/bin/BackupPC_dump -v -f >> [backupclient]' >> >> >> > Hello Bob, > > I have some Linux as well as some Windows client with public/private key > over ssh and I didn't have had this problem with any of my clients. > Do you have established the host key on the client? > What is the error message of "'Start Full Backup' would fail"? > > The BackupPC_dump isn't a "troubleshoot command" but the normal backup > command. Normaly called from the backuppc daemon. > For this communication, I choose to call this command a "troubleshoot command" because it is the first suggestion to try from the backuppc wiki page. The "-v" of the 'BackupPC_dump" portion gives verbose output, so users can see what is happen and diagnose failure issues. When I ran this command, the only thing I remember having to do, in each case was, agree that the host was to be added to the 'known_host' file. If I understand ssh correctly, that would be the client being added to the server (backuppc server) 'known_host' file. I guess I will read up on ssh. If I am correct, I did not scp anything to the server form the client, essentially telling the server that this client is acceptable. I think if I study this issue, more intently, I will discover it is an piece of the setup process I messed up. But, thanks for your suggestion and thoughts. I appreciate it. > br > Matthias > -- Bob Wooden Nashville, TN "Enjoying life at my best!" |