> And for the record, I don't necessarily disagree with you that there
> are things that can be improved but your attitude is going to get you
> less than nowhere. Also, the coders are hardly stupid and there are
> good reasons for the various tradeoffs they have made that you would
> be wise in
Harald Amtmann wrote at about 19:29:07 +0100 on Monday, December 7, 2009:
> So, for anyone who cares (doesn't seem to be anyone on this list who
> noticed), I found this post from 2006 stating and analyzing my exact problem:
You are assuming something that is not true...
>
> http://www.topo
Les Mikesell wrote at about 14:11:12 -0600 on Monday, December 7, 2009:
> It applies to full rsync or rsyncd backups. An interrupted full should
> be marked as a 'partial' in your backup summary - and the subsequent
> full retry should not transfer the completed files again although it
> wi
Harald Amtmann wrote:
>> Conf{IncrLevels} are fairly recent additions - be sure you have a
>> current backuppc version and the code and documentation match. Even
>> the current version won't find new or moved content if it exists in the
>> pool, though.
>
> Are you referring to 3.2.0 beta 1 o
> Conf{IncrLevels} are fairly recent additions - be sure you have a
> current backuppc version and the code and documentation match. Even
> the current version won't find new or moved content if it exists in the
> pool, though.
Are you referring to 3.2.0 beta 1 or 3.1.0 as recent version? I
Harald Amtmann wrote:
> Original-Nachricht
>> Datum: Mon, 07 Dec 2009 13:08:52 -0600
>> Von: Les Mikesell
>> An: "General list for user discussion, questions and support"
>>
>> Betreff: Re: [BackupPC-users] RsyncP problem
>
Original-Nachricht
> Datum: Mon, 07 Dec 2009 13:08:52 -0600
> Von: Les Mikesell
> An: "General list for user discussion,questions and support"
>
> Betreff: Re: [BackupPC-users] RsyncP problem
> Harald Amtmann wrote:
> > So, for an
Harald Amtmann wrote:
> So, for anyone who cares (doesn't seem to be anyone on this list who
> noticed), I found this post from 2006 stating and analyzing my exact problem:
>
> http://www.topology.org/linux/backuppc.html
> On this site, search for "Design flaw: Avoidable re-transmission of massiv
in the new location.
"
Original-Nachricht
> Datum: Thu, 22 Oct 2009 22:31:32 +0200
> Von: "Harald Amtmann"
> An: [email protected]
> Betreff: [BackupPC-users] RsyncP problem
> My problem is still that rsyncP with rsyncd as client
My problem is still that rsyncP with rsyncd as client still retransmits
unchanged files. I reduced the testcase:
1) Full Backup. All files are transmitted, This is the logoutput from the
client:
2009/10/22 21:35:44 [3820] connect from UNKNOWN (192.168.5.9)
2009/10/22 21:35:55 [3820] rsync on .
closedir D;
return if @list > 3;
unlink "$d/attrib" if ( @list == 3 && -f "$d/attrib" );
rmdir $d;
}
}, $dir );
}
Hope this little trick will help other users like me.
Regards,
Jean-Michel.
Re
Holger Parplies wrote:
presuming I had a new enough version of rsync for the man page to
include an
> explanation of what '--prune-empty-dirs' does, I'd probably be asking, why
> you would want to use that.
It's the only way (as far as I understood the rsync-man page) to include
a directory recur
Hi,
Bernhard Ott wrote on 16.02.2007 at 01:21:56 [[BackupPC-users] rsyncp problem
--prune-empty-dirs]:
> there seems to be a problem using the rsync --prune-empty-dirs
> (-m) option with backuppc (see log-file/config).
presuming I had a new enough version of rsync for the man page to incl
Hi,
there seems to be a problem using the rsync --prune-empty-dirs
(-m) option with backuppc (see log-file/config).
The rsync command/options works with all clients invoked via shell (and,
of course, without the -m option), but not via rsyncp. Seems like rsync
"reads" all the directories and filt
14 matches
Mail list logo
