On 2004-02-19 10:17:09 -0500, Perry E. Metzger wrote:
> Thanks to someone who seemed excessviely interested in flaming me for
> wanting to get text dumps, it seems no one paid attention to the
> questions I was actually asking, so I'm going to ask them again...
I do an incremental dump on commit and a cumulative dump every night.
If something takes out the repo, loosing 1 day's worth of log message
changes doesn't seem like the end of the world. Besides, it seems like
the only other way to have an complete backup is to hotcopy the entire
repo every commit.
> 1) Metadata:
> a) The fact that metadata is unversioned makes updates of log messages
> more dangerous than they need to be.
> b) The fact that metadata is unversioned means incremental dumps of
> the database, which are useful for all sorts of reasons, don't
> include updates to things like log messages.
> Therefore, there there any chance of revisiting the decision not to
> version metadata, or at least of finding a way of fixing b)?
>
> 2) AnonSVN:
> I can see to obvious ways to run a "shadow" AnonSVN server mirroring
> an original in near-real time:
> a) Do an incremental dump after every commit, and push it to the anon
> sever(s) where they get loaded -- only 1) gets in the way here.
> b) Send over the db transaction logs and replay them, but I
> don't really know how to do this.
> Any advice available on this?
Can't you push the new property to the shadow repo in
pre-revprop-change? I believe you get the new value on standard input.
Or - couldn't you have your read-only anonSVN repo be an svk mirror?
Your commit scripts could send a message to the anonSVN server that it
needs to update it's local copy. I don't really know a lot about svk,
but from what I've heard, it might be worth looking into for a situation
like this.
--
Maybe I feel detached. I may just look too shy.
It's disinterest, not that I'm a timid guy.
-The Faint, "Glass Danse"
- application/pgp-signature attachment: stored
Received on Thu Feb 19 16:41:01 2004