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


From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-01-17 21:46:18 CET

On Jan 17, 2007, at 12:37, Adrian Marsh wrote:

> I'm using svnsync to create a backup of a repo.. However I think
> that maybe
> I missed something when I originally setup the "mirror"..
> Particularly the
> UUID settings. The idea is that if we loose the main repo, then we
> can
> restore using the backup.
> I used "svnadmin create" to create the repo mirror, before using
> "svnsync
> init" to start the copy, then I use "svnsync sync" to update.
> A look at both repos shows different UUIDs, as below. Do I need to
> force-update the local backup (file://)? Can I do that to the
> backup repos
> now? Or wipe it and start again?

I believe that's how it's designed to work. Repositories must have
different IDs. svnsync is designed to create a read-only mirror of
your main repository. It is not (yet) designed as a way to provide a
hot spare repository that you can seamlessly switch to in case the
primary repository goes offline. If you want to use the mirror
repository in this way, there is some manual work that you have to do
at the time that you want the switch to occur. Among these tasks is
that you have to change its UUID to match that of the master
repository, and then switch --relocate all working copies to point to
the mirror server.


> (sync runs every 2 hours, which is why the revs are different)

FYI: If the repositories are even a single revision different when
the master crashes and you have to switch to the slave, things will
not work for anyone whose working copy includes the revision which
the master has and the slave doesn't. So you must sync immediately
after a revision is committed, for example in the post-commit hook on
the master.

The same advice goes for backups. Any backup strategy that does not
ensure that you have every revision as soon as it is created is
insufficient and will cause you problems if your repository needs to
be restored from backup.

To reply to the mailing list, please use your mailer's Reply To All  
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 17 21:46:51 2007

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.