Backing Data

[Herbie Marais]

Good day.

 

We are reviewing some alternate source control solutions for our Cape
Town operation.

 

One of the pre-requisites for us, is an absolute guarantee that the
source control repository will not get corrupted. 

Our employees often work remotely and the source control system needs to
be able to recover is the connection is interrupted while the user is
busy checking in a file.

 

We are kind of partial towards the systems that use a relational
database like sql server or mysql to store data, since this aspect is
take care of by the database's transaction handling.

 

Using a relational database as backing store also makes the backup of
the repository a breeze...

 

I have scanned through svn's website and could not find any information
on guaranteed transaction management and backup...

 

Please advice.

Kind Regards.

 

Herbie Marais

Senior Software Developer

TRIPLE POINT TECHNOLOGY, INC.

+27 21.861.6840 | office

+27 21.887.7168 | fax

www.tpt.com  

 

WE KNOW SHIPPING.

 

Re: Backing Data

[Konstantin Kolinko]

2011/6/15 Herbie Marais :
>
> I have scanned through svn’s website and could not find any information on
> guaranteed transaction management and backup...
>

1. Have you seen The Book [1]?

[1]: http://svnbook.red-bean.com/index.en.html

> Our employees often work remotely and the source control system needs to be 
> able to recover is the connection is interrupted while the user is busy 
> checking in a file.

2. It works fine. The files are transmitted and after that the
transaction is performed in one step.

If connection is aborted the stale files are left behind.  The
"svnadmin rmtxns" command is there to remove them. That is with FSFS
backend. I do not have practical experience with BDB one.


Best regards,
Konstantin Kolinko

Re: Backing Data

[Ulrich Eckhardt]

On Wednesday 15 June 2011, Konstantin Kolinko wrote:
> 2011/6/15 Herbie Marais :
> > Our employees often work remotely and the source control system needs to
> > be able to recover is the connection is interrupted while the user is
> > busy checking in a file.
> 
> 2. It works fine. The files are transmitted and after that the
> transaction is performed in one step.
> 
> If connection is aborted the stale files are left behind.  The
> "svnadmin rmtxns" command is there to remove them. That is with FSFS
> backend. I do not have practical experience with BDB one.

In any case, the commits are as atomic as you would expect from a database. In 
particular these half commits don't block the system for other users, neither 
with the FSFS nor the current BDB backend, so you don't have to get to an 
admin to run rmtxns on the repository.

Uli
**
Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**
Visit our website at http://www.dominolaser.com
**
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten 
bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen 
Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein 
sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, 
weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte 
Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht 
verantwortlich.
**