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

Re: Upgrading/Moving SVN after exists on other server

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 22 Sep 2010 09:21:12 -0400

On Wed, Sep 22, 2010 at 08:31, KM <info4km_at_yahoo.com> wrote:
>
>
> I have an existing older installation of svn 1.4.3 on solaris 8.   We are doing work on Solaris 10 now.  To save time I wanted to install svn 1.6.x on the solaris 10 box and set up a new svn repository for this version of our project.
>
> My question is - if i do that how do I later move the existing repositories from the old server?  can i just copy them in, or do i have to dump them and create empty ones on the new box and load them.   Also I assume between 1.4.x and 1.6.x there are conversions for the databases?
>
> Eventually the entire solaris 8 will be migrated to Solaris 10 ... just don't have the resources or time now.

If you're using FSFS and you're staying on the same processor
architecture, you may be able to just copy the database over. But a
dump/load cycle is the safest way to go and you'll be able to take
full advantage of the changes made to FSFS since 1.4 - sharding,
packing & rep-sharing - which may result in significant space usage.
Received on 2010-09-22 15:22:33 CEST

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.