SVN Server Best Practices?

[Mariusz Droździel <md...@gmail.com>]

Hello,

After spending almost 2 days on recovering broken FSFS, which turned
out to be broken for over year already I have a question. What are
suggested best practices for SVN Repo? Some kind of cronbot which
would do a verify and a full checkout dialy comes to mind. What else?
Are there any scripts to do dialy checks on repo out there already?
What do you suggest? Thanks in advance.

-- 
Mariusz Drozdziel

Re: SVN Server Best Practices?

[B Smith-Mannschott <bs...@gmail.com>]

2010/3/3 Mariusz Droździel <md...@gmail.com>:
> Hello,
>
> After spending almost 2 days on recovering broken FSFS, which turned
> out to be broken for over year already I have a question. What are
> suggested best practices for SVN Repo? Some kind of cronbot which
> would do a verify and a full checkout dialy comes to mind. What else?
> Are there any scripts to do dialy checks on repo out there already?
> What do you suggest? Thanks in advance.
>

one idea:

I have read-only (svnsync) clones of all my important repositories in
a separate building from the real svn server. This happened more by
accident than by design: my continuous build checks out from the
clones instead of the original repository. That way, I don't have to
worry about my build jobs flooding the central server with polling to
see if anything has changed yet. (There is some of this, however,
since there's a cron job to keep the repositories up-to-date.

This has helped me diagnose and repair repository corruption in one
case, and it gives me a warm fuzzy feeling (despite the fact that I've
been told that the central svn server is backed up).

// ben