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

Re: Backing up locks: dump doesn't maintain lock state?

From: Kenneth Porter <shiva_at_sewingwitch.com>
Date: 2006-12-20 22:09:46 CET

--On Wednesday, December 20, 2006 3:31 PM +0100 Troels Arvin
<troels@arvin.dk> wrote:

> Actually, I think that "svnadmin hotcopy" preserves all of locks, svnserve
> config, and hooks. - Without the need to take the repos offline. A
> reference to "svnadmin hotcopy" could be part of the output from "svnadmin
> help dump".

That's fine if the objective is backup to protect against catastrophe. But
the use case where it fails is when changing the repo representation, such
as when upgrading FSFS or switching between BDB and FSFS. The method
prescribed for doing that has been to dump and restore one's archive. There
should be some mechanism for preserving the rest of the repo representation
(ie. lock state and hook scripts) when doing that.

Is the svnserve config held "within" the repo? I'm only familiar with
Apache config, and that's held outside the repo, in Apache's configuration
domain, and can be backed up as part of Apache, not Subversion.

To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Dec 20 22:14:51 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.