> On Mon, Oct 15, 2012 at 3:19 PM, Cooke, Mark
> <mark.cooke_at_siemens.com> wrote:
>
> > -----Original Message-----
> > From: Arivarasan Manivasagam
> > To: users_at_subversion.apache.org
> > Subject: Subversion server upgrade from 1.4 to 1.7
> >
>
> > Hi,
> > We want to upgrade subversion server from 1.4 to 1.7
> > Is this feasible?
> > Can you share any steps or documents related to the same?
> >
> > thanks,
> > Arivarasan Manivasagam
>
>
> It is feasible and there are plenty of hits using
> google with very similar questions. It would be useful if
> you could say what your platform is (or will be if you plan
> on upgrading the hardware also).
>
> I suggest you start with the release notes for the 1.5,
> 1.6 and 1.7 [1] versions which should cover most of the
> gotchas but in theory a current server should be able to just
> pick up the old repositories and serve them. However, I
> would guess that a 1.4 to 1.7 upgrade would benefit from a
> dump / load cycle to make use of the latest repository
> structure features (as well as giving you a handy dump file
> backup of the pre-upgrade repositories).
>
> Perhaps you can provide more info and ask some more
> specific questions?
>
> ~ Mark C
>
> [1] http://subversion.apache.org/docs/release-notes/1.7.html
>
> -----Original Message-----
> From: Arivarasan Manivasagam [mailto:wings.arivarasan_at_gmail.com]
> Sent: 15 October 2012 11:11
> To: Cooke, Mark
> Cc: users_at_subversion.apache.org
> Subject: Re: Subversion server upgrade from 1.4 to 1.7
>
> Thanks for the reply.
>
> Currently we run this version (svn, version 1.4.6 (r28521))
> on a AIX machine. I am looking at upgrading to
> v1.7.6-1(http://www.perzl.org/aix/index.php?n=Main.Subversion)
Hmm, I'm sure I've seen some messages recently about AIX ~ have you searched the list archive (see http://subversion.apache.org/mailing-lists.html for search links)?
> Is it enough if I do the following
> (http://subversion.apache.org/faq.html#dumpload)? Or do I
> need to do anything more?
Did you have a look at the Subversion Book contents linked from that FAQ? Useful reading.
> 1. Shut down svnserve, Apache, and anything else that
> might be accessing the repository.
> 2. svnadmin dump /path/to/repository > dumpfile.txt ,
> using version X of svnadmin.
> 3. mv /path/to/repository /path/to/saved-old-repository
> 4. Now upgrade to Subversion Y (i.e., build and install Y,
> replacing X).
> 5. svnadmin create /path/to/repository, using version Y of
> svnadmin.
> 6. svnadmin load /path/to/repository < dumpfile.txt ,
> again using version Y of svnadmin.
> 7. Copy over hook scripts, etc, from the old repository to
> the new one.
> 8. Restart svnserve, Apache, etc.
That should be good for you, I've done similar on Windoze.
> Can you also elaborate step 7 on hook scripts and etc.,?
Subversion supports "hook scripts" that are called by subversion before/after specific actions [2]. They are in the repositories `hooks` folder (along with a load of templates with the `.tmpl` extension). If you have any hooks active, e.g. for emailing people after a commit, then you need to transfer these to the new repository yourself, there is no automatic support for this. Make sure that you set the required permissions on these files for whichever user account runs the subversion server process!
> Thanks again for the support!
[2] http://svnbook.red-bean.com/en/1.7/svn.reposadmin.create.html#svn.reposadmin.create.hooks
Hope that helps. Do read the release notes for each version upgrade before you do anything and don't do it on a live system without testing offline!
~ mark c
Received on 2012-10-15 12:40:32 CEST