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

Re: SVN Server migration to a new server

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Tue, 14 Apr 2020 10:16:40 +0200

On Tue, Apr 14, 2020 at 9:28 AM Dheeraj <kvdheeraj_at_gmail.com> wrote:
>
> Hi
>
> I have upgraded my SVN from RHEL 6 to RHEL 7 to a new server.
> I still have RHEL 6 server in production and have an DNS alias named svn-server poditing to the old server. My plan is to do a SVN dump of repos from old server and load it on new server. Once I load all repos, I will make the old server (RHEL 6) to read only and then make DNS change to point svn-server alias to new server (RHEL 7) and make it production.
> Do I need to do any other thing apart from this.
> Will I get any error while doing commit/check out to the existing one, since server is changed.
> Will I get "svn: E155000:" error?

Hi Dheeraj,

Dump & load will only transfer the versioned data (FSFS database).
Don't forget to also copy over:

  - hook scripts: OLDREPOS/hooks to NEWREPOS/hooks (it's best to
review them at this point, to make sure they'll work on the new
machine)

  - conf files: OLDREPOS/conf to NEWREPOS/conf (also, review them, and
check the new default conf files to see if there are any interesting
new options or comments)

  - locks: OLDREPOS/db/locks to NEWREPOS/db/locks (the locks that are
kept in working copies, for which a token is held on the server -- be
sure to do this during your maintenance window)

If you've done a full dump and load onto the new machine (in a freshly
created new repository), the repository UUID should be transferred as
well, so normally your old working copies will keep working, and you
won't get the E155000 error.

Perhaps also take a look at this FAQ entry for some more details of
the dump&load procedure:
http://subversion.apache.org/faq.html#dumpload

-- 
Johan
Received on 2020-04-14 10:17:00 CEST

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