BackupPC-users

Re: [BackupPC-users] Bug in Backuppc causing unnecessary re-transfer of data with rsync

2009-07-23 22:10:35
Subject: Re: [BackupPC-users] Bug in Backuppc causing unnecessary re-transfer of data with rsync
From: Adam Goryachev <mailinglists AT websitemanagers.com DOT au>
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Fri, 24 Jul 2009 12:06:13 +1000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Holger Parplies wrote:
> Hi,
> 
> Adam Goryachev wrote on 2009-07-24 08:35:50 +1000 [Re: [BackupPC-users] Bug 
> in Backuppc causing unnecessary re-transfer of?data with rsync]:
>> [...]
>> Sure, I understand that there was some communication problem, and the
>> backup failed, but...
>> [...]
>> That is the problem, it is NOT thrown away, it is marked as completed
>> successfully.
> 
> there was a similar report on the list not long ago. It appears there is a bug
> in BackupPC which may lead to an interrupted rsync backup (not sure if only
> incremental or also full; not sure about the cause of interruption) being
> marked as successful, even though the log file indicates that an error was
> detected at some point. The interrupted backup will be partial (i.e. missing
> files), but BackupPC will treat it as if it were complete. The next backup
> done with the partial one as reference (note that this next backup may also
> be a full!) will need to re-transfer (i.e. not just check checksums of) all
> files the partial is missing.
> 
> Is this summary correct? Can anyone add more information that may be relevant
> for debugging?

Yes that is correct.

>> So, why is the incr backup saved as successfull instead of thrown away
>> or marked as partial?
> 
> This remains to be found out and fixed. I'll try to have a look over the
> weekend, but I can't promise anything. Adam, did I understand you correctly
> that you can reproduce the problem?

Well, I haven't attempted to reproduce this, but it has happened on more
than one occassion so far. Last time I noticed earlier and simply
deleted the bad backup, so that the next backup was based on the earlier
proper backup.

I could probably try and reproduce it if it was helpful by killing the
ssh connection or similar. Let me know if you need this, and also what
extra logging you need enabled....

Regards,
Adam
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkppFxQACgkQGyoxogrTyiXoHACfcvAKcv/wwKvU+M9l8AJbFydX
+OwAn3pMJhRBHWGzU25AciXXgb5KsyX2
=DaLp
-----END PGP SIGNATURE-----

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