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

Re: upgrading server

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Wed, 26 Jul 2017 08:53:29 -0400

On Tue, Jul 25, 2017 at 2:00 PM, Andy So <akso_at_vitria.com> wrote:
> We have an old subversion version 1.4.3 (r23084) running on Solaris.
>
> We would like to upgrade to use new hardware on Linux based OS (CentOS 6.9),
> possibly version 1.8.x or 1.9.x

If you're bumping Subversion release to 1.8.x or 1.9.x, I'd urge you
to go to CentOS 7, which at least starts with Subverison 1.7, and get
the latest RPM's from Wandisco.

> Our plan is to installed and configure the latest SVN on CentOS 6.9. Then go
> through dump and load of the repository as described in various online post
> and documentations. The repository is quite large…guessing the size to be
> in the order of 20-40GB

See above. Installing the latest Subversion on CentOS 6 gets into some
fairly awkward library dependencies, especially for the "serf"
libraries which are notably out of date on CentOS 6.

> Before we start undertaking such tasks
>
> 1. Does anyone know if there are there any problem/gotcha in migrating
> the repository?
>
> 2. Does anyone know how long it would take to export the repository of
> this size? This will give us an estimate how long to schedule down time and
> cut off time.

Definitely use svnsync, if possible, so you have no downtime and can
write-lock the original repository and do a DNS based switchover.
Rollback, if there are *any* mismatched writes to the new repository,
means starting over with all working copies, which can be quite
painful.

> Thanks for any insight.

You might consider less of an extreme version update. The more
versions you update between, I've noted more likelihood of
incompatible workflows such as the changes in the "svn:external"
formats.
Received on 2017-07-26 14:53:35 CEST

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