I had something strange happen. One of my backups had started about 15
minutes before. I then decided to move the cable to the backup host from a
switch to a router. In the process of moving the cable, the backup kept
right on going. Has anyone seen this happen?

Chris Baker -- cbaker AT intera DOT com
systems administrator
INTERA -- 512-425-2006
 

>>-----Original Message-----
>>From: Les Mikesell [mailto:lesmikesell AT gmail DOT com] 
>>Sent: Friday, April 23, 2010 8:02 AM
>>To: General list for user discussion,questions and support
>>Subject: Re: [BackupPC-users] Noted Observations & Complaints 
>>Using BackupPC for 5 mon
>>
>>Tyler J. Wagner wrote:
>>> On Friday 23 April 2010 00:56:42 Saturn2888 wrote:
>>>> @Tyler J. Wagner
>>>> If it's confirmed Rsync works better than Rsyncd, I'll 
>>switch to it.
>>>>
>>>> The problem with SSH Rsync configurations is the 
>>public/private keys. 
>>>> I  seem to always have problems getting those setup, but I've 
>>>> recently not  had those problems so I can try that method, 
>>but I've 
>>>> never done it before  on Windows machines and will 
>>probably have great difficulty doing so.
>>>>  DeltaCopy has an ssh.exe, but I believe that is only a 
>>client, not a  
>>>> server. I do have PuTTY on some of the machines if that's 
>>helpful at all.
>>> 
>>> I was referring to using rsync for Linux clients, not Windows.  For 
>>> the 1 Windows server I archive, I use rsyncd.  I have not 
>>even tried 
>>> rsyncd on Linux.
>>> 
>>> Setting up SSH keys is easy:
>>> 
>>> On BackupPC server, as root:
>>
>>Errr... On the backuppc side you want to do this as the 
>>backuppc user...
>>
>>> ssh-keygen -b 2048 -t rsa
>>> 
>>> Set no passphrase.  Still on the server, do this for each client, 
>>> entering that client's root password.
>>> 
>>> ssh-copy-id -i /root/.ssh/id_rsa.pub root@client
>>> 
>>> This is equivalent to copying /root/.ssh/id_rsa.pub from 
>>the server to 
>>> each client's /root/.ssh/authorized_keys file.  Note that both .ssh 
>>> and authorized_keys must be readable/writable/executable by 
>>the user 
>>> only, not group/other.
>>
>>But what you really want it /home/backuppc/.ssh/id_rsa.pub 
>>appended to each remote's /root/.ssh/authorized_keys file 
>>(there could be other entries there already).
>>
>>-- 
>>   Les Mikesell
>>    lesmikesell AT gmail DOT com
>>
>>
>>--------------------------------------------------------------
>>----------------
>>_______________________________________________
>>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/
>>



------------------------------------------------------------------------------
_______________________________________________
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/