BackupPC-users

Re: [BackupPC-users] Backup aborted: No backup directory /.../new

2012-12-19 11:49:56
Subject: Re: [BackupPC-users] Backup aborted: No backup directory /.../new
From: Les Mikesell <lesmikesell AT gmail DOT com>
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Wed, 19 Dec 2012 10:48:25 -0600
On Wed, Dec 19, 2012 at 7:47 AM, Lars Tobias Skjong-Børsting
<lists AT snota DOT no> wrote:
> On 6/21/12 4:55 PM, Les Mikesell wrote:
>
>> On Thu, Jun 21, 2012 at 8:57 AM, Aaron Cossey <aaron.cossey AT gmail DOT 
>> com> wrote:
>>
>> I don't think I've seen anything about this problem before, so it may
>> be unique to your system.
>
> I have recently experienced this error on incremental backups.
>
> Ubuntu 12.04.1 LTS
> backuppc version 3.2.1-2ubuntu1.1
> XferMethod: rsync
>
>> Have you looked through the system logs
>> for disk errors, etc.?
>
> In /var/log/backuppc/LOG:
>
> 2012-12-19 02:30:17 Backup failed on nas (No backup directory
> /var/lib/backuppc/pc/nas/new)
> 2012-12-19 05:10:22 Backup failed on nas (No backup directory
> /var/lib/backuppc/pc/nas/new)
> 2012-12-19 07:52:13 Backup failed on nas (No backup directory
> /var/lib/backuppc/pc/nas/new)
>
> Nothing related in syslog. No disk errors.
>
> Correlating rsyncd logs from the nas host:
>
> 2012/12/19 02:13:37 [31215] building file list
> 2012/12/19 03:33:44 [31215] rsync error: timeout in data send/receive
> (code 30) at io.c(137) [sender=3.0.9]
> 2012/12/19 04:56:34 [31249] connect from  (192.168.1.7)
> 2012/12/19 04:56:34 [31249] rsync on . from backuppc@nas (192.168.1.7)
> 2012/12/19 04:56:34 [31249] building file list
> 2012/12/19 06:16:40 [31249] rsync error: timeout in data send/receive
> (code 30) at io.c(137) [sender=3.0.9]
> 2012/12/19 07:30:26 [31285] connect from nas (192.168.1.7)
> 2012/12/19 07:30:26 [31285] rsync on . from backuppc@nas (192.168.1.7)
> 2012/12/19 07:30:26 [31285] building file list
> 2012/12/19 08:50:33 [31285] rsync error: timeout in data send/receive
> (code 30) at io.c(137) [sender=3.0.9]
> 2012/12/19 15:48:48 [31404] connect from nas (192.168.1.7)
>
> So it seems it may be caused by a timeout.

Does this run through a stateful firewall or NAT router?   Instances
have been reported where rsync processing had long enough idle periods
for the device to time the connnection out.    If that is the case you
might enable keep-alives to fix it.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
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/