I have a script that:<div> - iterates though my MySQL tables</div><div> - dumps each table</div><div> - pipes the dump through gzip</div><div> - write the file to a temp file</div><div> - copies the file to [remote storage] (now Tahoe grid)</div>
<div> - deletes temp file</div><div><br></div><div>This gives me a daily snapshot of all of the active databases on my server every night.</div><div><br></div><div>The current backup is ~ 300 MB/night, which isn't bad, but after one year, that's 110+GB x 3.3 and counting of consumed tahoe space. Unless tahoe has a better garbage collection system than I have come to believe, that's going to be a problem on a 500 GB grid.</div>
<div><br></div><div>In my reading of the tahoe docs, I have not come across any alarms concerning mutable files. Is there something I should be made aware of?</div><div><br></div><div>jody<br clear="all">----<br>- Think carefully.<br>
- Contra mundum - "Against the world" (St. Athanasius)<br>- Credo ut intelliga - "I believe that I may know" (St. Augustin of Hippo)<br>
<br><br><div class="gmail_quote">On Sun, Jan 3, 2010 at 10:50 PM, Zooko O'Whielacronx <span dir="ltr"><<a href="mailto:zookog@gmail.com">zookog@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, Jan 3, 2010 at 10:33 PM, Jody Harris <<a href="mailto:havoc@harrisdev.com">havoc@harrisdev.com</a>> wrote:<br>
> I have set up my web server to store backup files on my tahoe grid, shifting<br>
> from the use of a server at my house. One thing that initially alarmed me<br>
> was that the timestamps of the backed up files is not updated in the<br>
> tahoe-lafs interface. I did confirm that the shares timestamps are updated.<br>
<br>
</div>Tahoe-LAFS doesn't store timestamps or other metadata on files, only<br>
on links to files, which links are stored in directories. So if you<br>
have a directory which contains a link named "README.txt" to version 1<br>
of your file, and then you upload version 2 of your file and you<br>
change that directory to link to version 2, then Tahoe-LAFS will<br>
update the timestamp on that link named "README.txt" when it updates<br>
the link to point to the new file.<br>
<br>
Did you say "mutable files"? You should probably not be using mutable<br>
files for anything. Immutable files (plus directories) probably fit<br>
all your needs for backups, and mutable files have significant<br>
performance problems.<br>
<br>
How do you trigger these backups -- are you using "tahoe cp" or "tahoe<br>
backup" or sending HTTP requests to the WAPI or something else?<br>
<br>
Regards,<br>
<br>
Zooko<br>
_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@allmydata.org">tahoe-dev@allmydata.org</a><br>
<a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
</blockquote></div><br></div>