You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Thomas Mandl <ma...@ikarus.at> on 2007/04/19 15:59:36 UTC
svn-hot-backup and restore question
hi all,
I wonder if you can help me with a svn backup and restore question.
szenario:
a svn server (linux/subversion-1.2.3) is backed up every night using the
"svn-hot-backup" script, which is part of the svn distribution.
how can I do the following:
1) restore a full backup (done with svn-hot-backup script) to a different
svn server (using 'svnadmin dump repos' and 'svnadmin load repos' is
***not*** an option***). I have to test a disaster recovery plan (and in
this plan the svn server has crashed and the svn repository must be restored
from tape backups on a brand new server system).
2) do the same thing as unter 1), but with a different/new path for the
svnroot directory (using automount/autofs is ***not*** an option).
I was seeking for several days, but could not find any hints how to restore
a full backup which has been priviously done with svn-hot-backup.
many thanks in advance
regards
thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn-hot-backup and restore question
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Apr 19, 2007, at 10:59, Thomas Mandl wrote:
> a svn server (linux/subversion-1.2.3) is backed up every night
> using the
> "svn-hot-backup" script, which is part of the svn distribution.
>
> how can I do the following:
>
> 1) restore a full backup (done with svn-hot-backup script) to a
> different
> svn server (using 'svnadmin dump repos' and 'svnadmin load repos' is
> ***not*** an option***). I have to test a disaster recovery plan
> (and in
> this plan the svn server has crashed and the svn repository must be
> restored
> from tape backups on a brand new server system).
The backup created by a hot copy is in itself a completely functional
repository. So all you have to do is make a copy of the hot-copied
backup and point your server's configuration at it. If this is a
different machine than the one on which the backup was created, and
if it is a BerkeleyDB-based repository, you will need to ensure that
the version of BerkeleyDB is the same, and that the processor
architecture is the same. If the repository is FSFS-based (the
default since Subversion 1.2.0), then no such restrictions apply.
> 2) do the same thing as unter 1), but with a different/new path for
> the
> svnroot directory (using automount/autofs is ***not*** an option).
Moving the repository to a different location on the server's disk is
not a problem. Just move it, and update your configuration to point
to the repository's new location.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org