rsync read block size

Matthias Schniedermeyer ms at citd.de
Tue May 26 09:02:53 GMT 2009


On 26.05.2009 02:17, Andrew Gideon wrote:
> On Sun, 24 May 2009 00:45:09 +0200, Matthias Schniedermeyer wrote:
> 
> > On the other hand the quiescent and device/filesystem snapshotting
> > results in a rsyncable copy.
> 
> Another possibility is to have the files on a volume or file system that 
> supports snapshots.  That won't guarantee "quiescent", but it will 
> guarantee consistency (in the sense that the entire copy will be from a 
> given moment in time).

The biggest differenct between "quiescent/snapshot" and "just snappshot" 
is that most databases have to do a recover-step. But that shouldn't be 
a real problem for any ACID-compliant Database (Which should be just 
about any, excluding MySQL with MyISAM-Backend). The important thing is 
that all the data is from the same point in time.

It's a simulation of: "Ups, my power just failed". And ACID-complient 
databases are supposed to recover from that. :-)




Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.



More information about the rsync mailing list