Re: [BackupPC-users] smb scheduled backup fails, but manual works
Travis Fraser wrote: On Wed, 2006-12-06 at 17:11 -0700, Chris Purves wrote: I have a problem where a scheduled smb backup does not run. The home page for that machine shows 'Pings to king-graham have failed 109 consecutive times.' However, I can ping the machine from the command line and I can manually start an incremental backup after which the home page shows 'Pings to king-graham have succeeded 2 consecutive times.' Is this a laptop where it might go into suspend or leave the network? It's a machine that I dual-boot windows/linux. When I boot to linux the hostname changes, so it does effectively leave the network. -- Chris - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
Re: [BackupPC-users] smb scheduled backup fails, but manual works
Tristan Stahnke wrote: On 12/6/06, Chris Purves [EMAIL PROTECTED] wrote: I have a problem where a scheduled smb backup does not run. The home page for that machine shows 'Pings to king-graham have failed 109 consecutive times.' However, I can ping the machine from the command line and I can manually start an incremental backup after which the home page shows 'Pings to king-graham have succeeded 2 consecutive times.' I had a similar problem on my home network when I set the DHCP flag in the conf/hosts file to 1. Setting it to 0 seemed to fix that problem. Since I don't have a DNS server on my home network I'm guessing it wasn't able to properly query the router for DHCP information, but it was still able to communicate to the client when I manually started a backup. If you manually specify the host in /etc/hosts and can ping it from the commandline, I believe setting the DHCP flag to 0 should fix the problem. Granted if the IP address of king-graham changes perhaps something else is amiss. Good luck. Okay, I set the DHCP flag to 0, and that seems to have fixed the problem. Thanks for the help. After checking the docs for the DHCP flag, I found that you should only set the flag to 1 if nmblookup (or gethostbyname) fails. In this case you need to specify a range of IP addresses and backuppc will query those specific addresses to request the hostname from those machines. Now that I understand this better, it's clear that I should have set the flag to 0. Thanks Tristan for pointing me in the right direction. -- Chris - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
[BackupPC-users] Not pooling or compressing
Hello: It seems that my files are not pooling. I have read the docs and have looked in the folders that the pooled files should be in and they are not there. For each backup there is a folder and the backed up files are all contained inside that folder. I am using SMB for transport and am backing up one linux and two xp machines. Are there settings that I can check to make sure pooling happens? Also, my files are not compressing, could this be causing the pooling issue? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
[BackupPC-users] problem in backuppc
got this problem backing up a linux box. ssh was configured already but still got this error. Running: /usr/bin/ssh -q -x -l root 192.168.6.50 /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group --devices --links --times --block-size=2048 --recursive --ignore-times . /home/ Xfer PIDs are now 5508 Rsync command pid is 5508 Fetching remote protocol Got remote protocol 1953722184 Fatal error (bad version): Host key verification failed. Checksum seed is 2036689696 Got checksumSeed 0x79656b20 Read EOF: Connection reset by peer Tried again: got 0 bytes fileListReceive() failed Done: 0 files, 0 bytes Got fatal error during xfer (fileListReceive failed) Backup aborted (fileListReceive failed) please help. - Have a burning question? Go to Yahoo! Answers and get answers from real people who know.- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
Re: [BackupPC-users] problem in backuppc
On Thursday 07 December 2006 21:23, louie aguilos wrote: got this problem backing up a linux box. ssh was configured already but still got this error. Running: /usr/bin/ssh -q -x -l root 192.168.6.50 /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group --devices --links --times --block-size=2048 --recursive --ignore-times . /home/ Xfer PIDs are now 5508 Rsync command pid is 5508 Fetching remote protocol Got remote protocol 1953722184 Fatal error (bad version): Host key verification failed. I think you need to su - backuppcUserNameHere and try to ssh -l root 192.168.6.50 as that user so it gets the key for the remote host stored in ~/.ssh/known_hosts. Also, I would personally recommend using rsyncd rather than rsync over ssh just so you don't have a non-priveliged user of one machine becoming root on another, but that's just my advice. If you choose to go the ssh route, this should work! HTH! Randy - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
