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

Re: Directions on SVN from 2008 to 2012 (UNCLASSIFIED)

From: Pavel Lyalyakin <pavel.lyalyakin_at_visualsvn.com>
Date: Mon, 27 Jun 2016 22:15:47 +0300

Hello Mary,

On Mon, Jun 27, 2016 at 7:25 PM, Covington, Mary E CTR USARMY RDECOM
(US) <mary.e.covington6.ctr_at_mail.mil> wrote:
> Hi, we are transitioning from a 2008 server to 2012. Can you provide me directions on how to setup the 2012 server and move all of the data from the 2008 server. Thanks.

I'm sure that you are not asking about how to setup Windows Server
2012, but about how to move your existing Subversion server
installation and the repositories to a new server machine. Right?

In such case, you could provide us with a bit more information about
your current Subversion installation just because it's very hard to
give you any directions without knowing at least the basic information
such as whether you build the Subversion server yourself or use some
Subversion server package such as VisualSVN Server or SVN Edge (what's
the version of the server package, BTW?), which Subversion version and
maybe Apache HTTP Server you run now in case you build the server

But the basic step-by-step procedure is going to look like:
1. Install and configure the Subversion server on the new machine.
2. Move your repositories to the new machine. For instructions, read
    SVNBook | Migrating Repository Data Elsewhere:
3. Make sure to move your repository hook scripts if there are any and
    check that they work as expected.

I'd like to note again that this is the most basic instruction. At the
moment, there is not enough info available about your current SVN
server installation to give a detailed advice tailored to your
particular situation.

With best regards,
Pavel Lyalyakin
VisualSVN Team
Received on 2016-06-27 21:16:31 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.