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

Re: Advice on upgrading svn and moving to new server

From: David Chapman <dcchapman_at_acm.org>
Date: Fri, 01 Apr 2011 08:51:28 -0700

On 4/1/2011 5:45 AM, KM wrote:
> Thanks I think. Not sure it helps with my original question.
> ... which i am sure i'll figure out by trial and error.
> Whether to updgrade to solaris 10 w/new server, install newer svn and
> dependent packages and then copy reppos from old server - dump it and
> load it. Or do I need to install and upgraded svn and repos on
> old server then copy to new server - etc -
> Since i am only at 1.4.3 on solais 8 and I want to be on Solaris 10
> with svn 1.6.x I just wasn't sure how easy or difficult it all would
> be, and what the order of the tasks should be to make it the least
> effort and most efficient upgrade.
> Just wanted some advice about the easiest way to accomplish my task.
> Thx a bunch.
> KM

The ideal procedure is to upgrade the operating system and Subversion on
a second machine, dump the repository on the old machine and load it on
the new machine, then verify that it all works while the original
machine is still available to the developers. Then take the original
machine offline and dump/load the repository one more time. This way
the repository is unavailable only for the time it takes to dump and
load it. Using an incremental dump can make the down time very low.

I work solo and I can't do any development while I am upgrading a
machine, so I typically dump the repository to a backup location,
upgrade the machine and Subversion, load the repository under the new
operating system, then test it. But that means the repository is down
for a day (I always reformat the hard drive when I upgrade the operating
system). Your mileage may vary.

     David Chapman         dcchapman_at_acm.org
     Chapman Consulting -- San Jose, CA
Received on 2011-04-01 17:52:23 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.