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

Re: use hotcopy or dump for network repository

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Tue, 21 Feb 2012 12:57:26 -0500

On Tue, Feb 21, 2012 at 12:37 PM, Les Mikesell <lesmikesell_at_gmail.com>wrote:

> On Tue, Feb 21, 2012 at 11:18 AM, e-letter <inpost_at_gmail.com> wrote:
>
>> Readers,
>>
>> The manual states that 'hotcopy' of 'dump' are examples of commands to
>> use to create a copy of a repository. An svn repository was created on
>> a network using the protocol 'svn+ssh'; what is the most appropriate
>> method to make a copy (e.g. onto a CD) and then use that copy to
>> transfer that repository to another computer?
>>
>
> Svnadmin dump/load is the most generic approach and should always work
> without much concern for differences in CPU types, subversion versions, or
> relocating the path where you load it. If those things are all the same,
> hotcopy should work too.
>
>
>
It's also a FAQ. Do note, "svnadmin hotcopy" does replicate symlinks now,
and replicates the configuration files and scripts in the particular
repository. But it does *not* replicate permissions or file ownership
settings, so if you rely on these for access control to scripts or
authentication files, you need some out of band mechanism to replicate
them. And it cannot replicate Apache based settings, such as those in
/etc/httpd/conf.d/subversion.conf on an RPM installed Linux server.

svnsync does not replicate those configurations at all. Again, if you want
to preserve or back those up, you need an out of band mechanism. This sort
of thing, and the engineering time burned on spinning your own solutions,
is precisely where a commercial system (such as Wandisco's product) can be
well worth the money to get a plug and play, multi-homed, commercial grade
live failover solution.
Received on 2012-02-21 18:57:59 CET

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