Re: Keeping a hot/live FSFS repo for failover
Gotcha. So maybe just be easier to set the UUID of the backup to be the
same UUID as the primary (using your method, seems a bit safer), and that
won't mess up anything?
On 11/16/06, Garrett Rooney <email@example.com> wrote:
> On 11/16/06, Kyle Kline <firstname.lastname@example.org> wrote:
> > One more follow-up on this:
> > I notice the UUID of the backup repo is different than the live repo,
> > would cause issues with commits if we had to failover.
> > Is the below approach sufficient:
> > copied the *backup* UUID as UUID.backup
> > copied the live UUID file into the *backup* as UUID.live
> > In the event of a failover, do a
> > copy UUID.live UUID (windows folks, sorry)
> > And when "failing back" to primary, to turn it back into the sync/backup
> > copy UUID.backup UUID
> > (Same with revprop 0, have a 0.backup and a 0.live)
> There is a "nicer" way to do it via svnadmin described in
> http://svn.collab.net/repos/svn/trunk/notes/svnsync.txt, but yeah,
> you've got the general idea.
Received on Thu Nov 16 18:18:51 2006
This is an archived mail posted to the Subversion Users