'Re: [Zope-dev] [ZODB-Dev] SVN woes.'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zope-dev
Subject:    Re: [Zope-dev] [ZODB-Dev] SVN woes.
From:       Wichert Akkerman <wichert () wiggy ! net>
Date:       2008-11-11 15:49:18
Message-ID: 4919A97E.6090707 () wiggy ! net
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On 11/11/08 4:10 PM, Izak Burger wrote:
> Jim Fulton wrote:
>    
>> I'm going to restore svn from a backup and see where that leaves us.
>> I'm going to disable svn access while I work on this.
>>      
>
> Good luck :-) I know a little something about the hard work involved in
> recovering subversion repos, in the last year we had TWO cases of
> corrupted revisions in an svn repo we were managing. It had something to
> do with concurrent commits and the fact that we were running
> apache-mpm-worker (instead of prefork).
>    

FWIW, the setup we have for svn.plone.org may be useful for others as 
well: we have two servers (svn.plone.org and svn-mirror.plone.org) with 
a svnsync setup to keep the mirror (almost) realtime in sync with the 
main server. There is an LDAP database which is replicated between the 
two servers as well which we use for authentication. This setup allows 
us to swich svn.plone.org to the other server in minutes if it dies, 
without any loss of data.

Wichert.

[Attachment #5 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 11/11/08 4:10 PM, Izak Burger wrote:
<blockquote cite="mid:4919A061.7040201@upfrontsystems.co.za" type="cite">
  <pre wrap="">Jim Fulton wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">I'm going to restore svn from a backup and see where that leaves us.   
I'm going to disable svn access while I work on this.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Good luck :-) I know a little something about the hard work involved in 
recovering subversion repos, in the last year we had TWO cases of 
corrupted revisions in an svn repo we were managing. It had something to 
do with concurrent commits and the fact that we were running 
apache-mpm-worker (instead of prefork).
  </pre>
</blockquote>
<br>
FWIW, the setup we have for svn.plone.org may be useful for others as
well: we have two servers (svn.plone.org and svn-mirror.plone.org) with
a svnsync setup to keep the mirror (almost) realtime in sync with the
main server. There is an LDAP database which is replicated between the
two servers as well which we use for authentication. This setup allows
us to swich svn.plone.org to the other server in minutes if it dies,
without any loss of data.<br>
<br>
Wichert.<br>
<br>
</body>
</html>

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

[prev in list] [next in list] [prev in thread] [next in thread] 