From: Leen B. <le...@co...> - 2009-06-03 20:20:02
|
Hi Folks, Recently I took the patch Elias Penttilä wrote and 'forward-ported' it to rsync 3. For people who don't know what it does, it implements backup of open files on Windows with rsync. Because I think rsync 3 is more efficient and more current in comparison to rsync 2, it uses an incremental filelisting system to try and be more efficient. Especially memory-wise. I made a small readme-page with information about what I've done so far and the status/limitations/binaries: http://www.consolejunky.net/cwrsync-vss/ As most people, I'm a bit strapped for time and thus I like to prioritize the kind of features/fixes/other changes that I need/peole want. I'm contacting you folks to have a look, because I hope to get some feedback on what people need. My hope is to get something that works so well to have it included it in the cwrsync=installer: http://www.itefix.no/i2/cwrsync Their seems to be some interest from the cwrsync maintainer to possible include it. Have a nice day, Leen Besselink. |
From: Tino S. <bac...@ti...> - 2009-06-04 09:50:36
|
Hi Leen, On Wed, Jun 03, 2009 at 10:04:43PM +0200, Leen Besselink wrote: > Recently I took the patch Elias Penttilä wrote and 'forward-ported' it to rsync 3. > > For people who don't know what it does, it implements backup of open files on Windows with rsync. > > Because I think rsync 3 is more efficient and more current in comparison to rsync 2, it uses > an incremental filelisting system to try and be more efficient. Especially memory-wise. Note that you won't gain anything with BackupPC because BackupPC uses it's own implementation of the rsync protocol which does not yet support rsync3. Tino. -- "What we nourish flourishes." - "Was wir nähren erblüht." www.lichtkreis-chemnitz.de www.craniosacralzentrum.de |
From: Jeffrey J. K. <bac...@ko...> - 2009-06-04 15:40:15
|
Tino Schwarze wrote at about 11:50:35 +0200 on Thursday, June 4, 2009: > Hi Leen, > > On Wed, Jun 03, 2009 at 10:04:43PM +0200, Leen Besselink wrote: > > > Recently I took the patch Elias Penttilä wrote and 'forward-ported' it to rsync 3. > > > > For people who don't know what it does, it implements backup of open files on Windows with rsync. > > > > Because I think rsync 3 is more efficient and more current in comparison to rsync 2, it uses > > an incremental filelisting system to try and be more efficient. Especially memory-wise. > > Note that you won't gain anything with BackupPC because BackupPC uses > it's own implementation of the rsync protocol which does not yet support > rsync3. I don't believe this is fully true. Now indeed BackupPC doesn't use the latest protocol=30 which is due to the fixed protocol limitations of perl-File-RsyncP-0.68-2.fc8.1.i386.rpm. However, I believe that the memory-saving features are independent of the protocol and hence still shine through.. (I may be wrong, so correct me if so) |
From: Leen B. <le...@co...> - 2009-06-04 23:29:54
|
Jeffrey J. Kosowsky wrote: > Tino Schwarze wrote at about 11:50:35 +0200 on Thursday, June 4, 2009: > > Hi Leen, > > > > On Wed, Jun 03, 2009 at 10:04:43PM +0200, Leen Besselink wrote: > > > > > Recently I took the patch Elias Penttilä wrote and 'forward-ported' it to rsync 3. > > > > > > For people who don't know what it does, it implements backup of open files on Windows with rsync. > > > > > > Because I think rsync 3 is more efficient and more current in comparison to rsync 2, it uses > > > an incremental filelisting system to try and be more efficient. Especially memory-wise. > > > > Note that you won't gain anything with BackupPC because BackupPC uses > > it's own implementation of the rsync protocol which does not yet support > > rsync3. > Tino, Ahh, I see, hmm, well, euh... Maybe Jeffrey could be right: > I don't believe this is fully true. Now indeed BackupPC doesn't use > the latest protocol=30 which is due to the fixed protocol limitations > of perl-File-RsyncP-0.68-2.fc8.1.i386.rpm. However, I believe that the > memory-saving features are independent of the protocol and hence still > shine through.. (I may be wrong, so correct me if so) > I took a large filetree and tested a bit and it looks like you might be right. |
From: Leen B. <le...@co...> - 2009-06-04 23:27:40
|
Jeffrey J. Kosowsky wrote: > Tino Schwarze wrote at about 11:50:35 +0200 on Thursday, June 4, 2009: > > Hi Leen, > > > > On Wed, Jun 03, 2009 at 10:04:43PM +0200, Leen Besselink wrote: > > > > > Recently I took the patch Elias Penttilä wrote and 'forward-ported' it to rsync 3. > > > > > > For people who don't know what it does, it implements backup of open files on Windows with rsync. > > > > > > Because I think rsync 3 is more efficient and more current in comparison to rsync 2, it uses > > > an incremental filelisting system to try and be more efficient. Especially memory-wise. > > > > Note that you won't gain anything with BackupPC because BackupPC uses > > it's own implementation of the rsync protocol which does not yet support > > rsync3. > Tino, Ahh, I see, hmm, well, euh... Maybe Jeffrey could be right: > I don't believe this is fully true. Now indeed BackupPC doesn't use > the latest protocol=30 which is due to the fixed protocol limitations > of perl-File-RsyncP-0.68-2.fc8.1.i386.rpm. However, I believe that the > memory-saving features are independent of the protocol and hence still > shine through.. (I may be wrong, so correct me if so) I took a large filetree and tested a bit and it looks like you might be right. |