[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: some requests/questions .

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-07-12 14:44:18 CEST

Féliciano Matias <feliciano.matias@free.fr> writes:

> First, excuse my poor english.
>
> ** Can i do a hot dump (with svnadmin dump).

hot-backup.py already exists. It's a feature of Berkeley DB.

For our own repository, we run hot-backup.py as a post-commit hook script.

>
> ** Is there any problems using a repository with http://... for remote
> users and the same repository with file://... for local users (not very
> useful ...).

No, no problems.

> ** Are there any plan to use a classique db (for exemple postgresql
> which is a full-feature db, transation, versionning, hot backup, ...).
> this should give the possibility do to something like this in httpd.conf
> and perhaps in .htaccess. :

Yes. People are working on SQL backends.

BerkeleyDB still has the 'full features' you mention, however -- like
transactions, hot backups, etc. It just doesn't have rows.

> howerer, it's good to keep an embedded db version of subversion that
> don't require a db administrator.

That's also true. :-)

>
> ** For backup, i would like something like this :
> $ svnadmin dump repos 0 youngest_version > full_backup
> $ svnadmin dumpdiff repos youngest_version new_youngest_version >
> partial_backup

What is 'dumpdiff'? You can still create a partial dump as you
suggest by running 'svnadmin dump repos N N+M'.

Actually, I need to point out that 'svnadmin dump' is *not* meant for
backup purposes. It's meant to *migrate* data from one repository to
another. For example, we use it whenever we change the internal DB
design of the repository. And it will be needed if you want to move
your data from a BerkeleyDB repository to a SQL repository.

If you want to make a backup, use hot-backup.py. BerkeleyDB is
designed to be backed up while running. 'svnadmin dump' is too
laborious.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 12 14:48:55 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.