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

How to do a failover from primary to secondary system

From: Baeriswyl Kuno - Extern (IT-BA-MV) <kuno.baeriswyl_at_sbb.ch>
Date: Mon, 28 Jul 2008 17:39:59 +0200


What is the recommend way to do a failover to a secondary system?

We do a nightly backups of our repositories. In an emergency case, e.g. hardware failure, we would like to set up a second server using the backup from the last night. We tried to use the relocate functionality, that is implemented in TortoiseSVN and Subclipse. Though, we stated that the local repository and the server must be in sync in order to make it work with a relocation. Typically, this situation isn't guaranteed. Particularly, revisions in the local copy that weren't available on the server anymore let to errors while updating to the new repository instance.

How can the developers reconnect to this new subversion instance without a fresh checkout and loosing data? In order to achieve this objective, do I need to set up a slave instance that is continuously synchronised with its master?

Thanks for your help.

Received on 2008-07-28 17:40:34 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.