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

Re: hot-backup vs svnadmin dump

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 4 Apr 2008 12:55:28 -0400

On 4/4/08, David Pratt <fairwinds_at_eastlink.ca> wrote:
> Hi. I am in the process of automating a backup and recovery and would like
> to know what is best for complete restoration of the repository. The
> machines have different os's so just want to ensure I do not run into snags.
>
> My repository is hosted on an mac osx machine. I would prefer to do cron
> hot-backups and unarchive my repository without any consequences to a CentOS
> machine in event of failure. Will I run into any trouble with this scenario?
> Would it be better to do a dump and then load the dump file to a new
> repository on the Linux box. I guess I am questioning whether these method
> are os agnostic and if not how to work around this. Many thanks.

svnadmin dump is the correct way to move a repository between
platforms. The dumpfile format and dump/load process takes into
account any platform differences between them.

Run the hotcopy first, then dump the hotcopy. If you attempt to dump
an active repository, you could end up with an unusable dumpfile if
there's a transaction in-progress when the dump is performed.

You're in essence describing a combination of "hotcopy for backup" and
"migrate to a different platform." See
http://svnbook.red-bean.com/en/1.4/svn-book.html#svn.reposadmin.maint.backup
and then "Migrating Repository Data Elsewhere" which is linked from
it.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-04 18:55:49 CEST

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