On 8/29/07, <b class="gmail_sendername">Richard Edward Horner</b> <<a href="mailto:rich@richhorner.com">rich@richhorner.com</a>> wrote:<div><span class="gmail_quote"></span><div><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Can you explain what you mean by "Of course this will cause any file<br>larger than this chunk size to be backed up again!"<br><br>Are you saying that every time you run backup a given target that an<br>unchanged file whose size is greater than the chunk size will be
<br>backed-up even if it hasn't changed? Or something else?<br></blockquote></div><br>If a file is larger than the chunk size, than it is broken up into chunks and backed up. If you have already backed up a file, then change the chunk size, the next time you go to back up that file, brackup will identify it as too large and break it up. Since the brackup file system is based on digests of the files to be backed up, and these chunks will have a different digest than that of the whole file, the file system will treat these three files as separate and upload them. Assuming you don't make further changes to the chunk size (or the file in question), however, any subsequent backups will break up the large file into chunks, and the digest of those chunks will match the digest of the chunks earlier uploaded, so they will not be re-uploaded.
<br><br>sean<br clear="all"><br>-- <br>Sean M. Graham - <a href="http://www.sean-graham.com/">http://www.sean-graham.com/</a>