Rsync help needed...

lsk ellsatish at gmail.com
Fri Feb 24 19:08:33 GMT 2006



Wayne Davison-2 wrote:
> 
> On Fri, Feb 24, 2006 at 05:58:26AM -0800, lsk wrote:
>> 2) And Matt could explain little more on what do you mean by "atomicity"
> 
> What he meant is that, without --inplace, rsync creates an updated file
> and moves it into place, making the update atomic (i.e. none of the
> destination files are ever in a partially-updated state).  When the
> --inplace option is used, the updates are written directly to the
> destination files, which can be a bad thing if someone is trying to
> read the file at the same time.
> 
> ..wayne..
> 
> ////****/// lsk:- Thanks for the clarification Wayne, in my case no one
> would be allowed to use the destination file until the process is
> complete. As soon as my destination server is upgraded to the newer
> version of rsync which supports --inplace option I am going to try with
> in-place and -no-whole-file option without -- checksum since rsync
> algorithm does it.
> 
> Wayne I have one more question regarding -- checksum, I don't do rsync at
> directory level I do datafile by datafile so does this option of
> --checksum is useful only if I did at a directory level rysnc to check all
> files in the directory *before* transfer to determine which files need to
> be transferred. If I do at file level since it does the checksum by itself
> I don't need to explicitly specify am I right ? 
> 
> Because I don't need all files in the directory to be transferred...
> 
> I have been using the following syntax..
> 
> rsync -cvz /d01/app/testfile1.dbf  tarser:/t01/app/testfile1.dbf
> 
> but I would change to the one below and test a 40 GB transfer and see the
> results...
> 
> rsync -zv --no-whole-file --stats /d01/app/testfile2.dbf 
> tarser:/t01/app/testfile2.dbf
> 
> Thanks,
> lsk.
> 
> 

--
View this message in context: http://www.nabble.com/Rsync-help-needed...-t1170765.html#a3113956
Sent from the Samba - rsync forum at Nabble.com.



More information about the rsync mailing list