I recently changed the Filesystem target in svn to do an existence check (a size check, actually) on the file-to-be-uploaded before actually uploading it (er, "copying it" ... I use sshfs to backup a local "filesystem" remotely). I should push that up a layer so all targets (S3, etc) get that for free. But that means more round-trips in the case in the common case, where the target doesn't actually have it, and you're just backing up 1 server to 1 target. So I should probably make it a target option.<br>
<br>Something like:<br><br>[TARGET:foo]<br>type = Amazon<br>check_file_existence_before_upload = true<br><br>And you'd set that on any target that you expect the contents to already be there, either from losing the inventory database, or from being backed up from another server.<br>
<br>I'll keep this in my inbox until I do that. But if you're using the Filesystem target, get the latest svn from <a href="http://code.google.com/p/brackup">code.google.com/p/brackup</a>.<br><br><br><div class="gmail_quote">
On Sun, Apr 13, 2008 at 2:06 AM, Ed W <<a href="mailto:lists@wildgooses.com">lists@wildgooses.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi, Brackup looks like a good fit for my needs, but I need to backup quite a few identical servers (to S3) and so I'm looking to share the index files.<br>
<br>
How have other people solved this? Seems like the options are:<br>
<br>
- Backup from one machine accessing the filesystems remotely<br>
- Use some way to share the db files online (I guess sqlite deals with multiusers over a shared filesystem?)<br>
- Backup servers one by one and sync the dbs around to each one by one (yuck)<br>
- Modify brackup to use mysql for the shared db files?<br>
<br>
Any comments from existing users?<br>
<br>
Cheers<br><font color="#888888">
<br>
Ed W<br>
</font></blockquote></div><br>