Hello.
“rsync target::” works just fine:
vm-backuppc# /usr/local/bin/rsync 192.168.0.118::
docs Documents and Settings
dDrive Entire D Drive
The logs don't provide anything more specific than “Backup failed on
<HostName> (inet connect: Operation timed out)”. I guess the problem
is somewhere with how BackupPC handles the sockets or nearby, judging
by results of “grep -r "inet connect" *”...
Sincerely,
Maxim
2012/1/31 Les Mikesell <lesmikesell AT gmail DOT com>:
> On Tue, Jan 31, 2012 at 9:29 AM, haruspex <princeps.candidus AT gmail DOT
> com> wrote:
>>
>> I have installed BackupPC 3.2.1 on a FreeBSD server to back several
>> Windows workstations up. The Xfer method is rsyncd. Some of them
>> workstations work fine, but three display strange behaviour:
>>
>> 1) One gives “inet connect: Connection refused” though “telnet <IP>
>> 873” from the very same FreeBSD server works just time. BackupPC
>> managed to make a successful backup of one share (of two) on this
>> computer once. Not sure what was different.
>>
>> 2) One gives “no ping”, then, after making $PingCmd for it empty,
>> “inet connect: Operation timed out”. telnet is successful as well
>> here; “nmblookup <name>” or “ping -c 1 <IP>” don't show any problems
>> when run from shell either.
>>
>> 3) The only Windows 7 box (the others are XP). Just plain “inet
>> connect: Operation timed out”, can't connect from any other computer
>> as well.
>>
>> To sum up, I have two problems: BackupPC not connecting while
>> everybody else can, and rsyncd not working properly on Windows 7.
>>
>> Any help will be strongly appreciated. The bizarre BackupPC failures
>> are making me question my sanity.
>
> Recent windows versions have a firewall on by default that needs to be
> configured to allow inbound connections. One way to test basic
> connectivity with rsynd is to run 'rsync target::' or 'rsync
> target::module' from the backuppc server. Note the double colons that
> distinguish a connection to rsyncd as opposed to running over ssh, and
> that if you don't specify a destination in the command you should get
> a directory listing. Not sure what to check on the one that works on
> some of the shares - see if the logs show anything specific and look
> for any possible network issues.
>
> --
> Les Mikesell
> lesmikesell AT gmail DOT com
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> 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/
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
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/
|
