Re: question: repository backups?

Dan Berger <dberger@ix.netcom.com> writes:

> > > 1. Operational Concerns: One of the nice things about CVS is that the
> > > repository is transparent - you can tar it up, move it around, dump it
> > > to tape like any other file system - do incremental backups, etc. Can
> > > someone on this list discuss how subversion intends to address
> > > day-to-day repository maintenance?

The svn repository is a directory full of Berkeley .db files and
scripts. You can tar it up, move it around, dump it to tape. You can
do 'hot backups' -- we have a script that does that already (in our
source tree.)

Read about Berkeley DB at www.sleepycat.com. The repository is really
just a berkeley 'environment'.

> > > 2. Client library language bindings: I seem to recall that there's been
> > > discussion of client library bindings for C and Python - any plans for
> > > Java? I've got a project in front of me that I'm starting to evaluate
> > > revision control systems for - and one requirement is a set of Java
> > > bindings. Any comment?

Alex Mueller is writing JNI bindings. He commits very frequently.
:-) Look in the bindings/ directory of our tree.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:52 2006