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

Re: How to do a failover from primary to secondary system

From: Andy Levy <andy.levy_at_gmail.com>
Date: Mon, 28 Jul 2008 12:20:45 -0400

Please be sure to Reply To All

On Mon, Jul 28, 2008 at 12:07, Baeriswyl Kuno - Extern (IT-BA-MV)
<kuno.baeriswyl_at_sbb.ch> wrote:
> [The only data they should lose is whatever they don't back up before performing a fresh checkout.]
> So, the only option is to backup to local copy without .svn, to do a fresh checkout and to copy the backup to the local copy. Two things are troubling me with this solution, though. First, doing a checkout is a very extensive task with our environment. Second, renamed and deleted files might get reincarnated. Are there any other optinions?

You could use svn switch --relocate but not with your current nightly
backups. In your current setup, you can't (I'm fairly sure) do this
because the WCs will be expecting the repository to be at revision X,
but when they contact the "new" server they'll find it at X-Y where Y
is the number of revisions between your last backup and the failure.
If you sync your commits as they happen, this is mitigated.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-28 18:21:15 CEST

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

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