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

Re: Moving FreeBSD to a new server

From: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Fri, 6 Feb 2009 18:21:11 -0600

On Feb 6, 2009, at 18:10, Alec Kloss wrote:

> On 2009-02-06 15:56, Paul Klepac wrote:
>> I'm new to UNIX but I've been given the task of moving our
>> existing
>> TortoiseSVN
>> to a new server. Basically what is going on is that our existing
>> FreeBSD/TortoiseSVN
>> server is starting to have some disk problems and so we want to
>> build a
>> new server
>> (install FreeBSD, Apache, and SVN) and move the Berkeley Database.
>> So as I understand it, I need to install:
>> * FreeBSD OS: 7.1-RELEASE-i386-disc1.iso
> [chop]
> If you're able to tolerate a bit of down time, it might be easier
> to dump all the filesystems from the old server and restore them
> on the new server. If you're really replacing the machine, this
> will guarantee you get every last detail right. If you try to
> reconfigure a new installation to match an existing one, you're
> almost certain to miss some mundane detail that you'll wish you
> hadn't. With dump/restore, the only things you have to reconfigure
> is *maybe* the network interface configuration in /etc/rc.conf.
> (If you can't tolerate a bit of down time, you can do
> do level 0s while the respository is active and then do level 1s
> with the repository machine isolated from access. If you practice
> a few times and have less than a few hundred committers I bet you
> can do it with less than five minutes down without too much
> difficulty.)

Another possibility is to use svnsync to replicate the old repository
onto the new server. The new repository will be built from scratch so
it'll be like a dump and load in that respect, but the sync can
happen while the old server is online. When it's done, you can
disable connections to the old server, run svnsync again to catch any
last commits from the old server, and then switch to the new server.
You'll also have to copy your hook scripts and conf files from the
old server, if applicable; svnsync does not copy these. (Neither
would a dump/load.)


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-07 01:22:08 CET

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.