Thanks Andy, especially for the hint about stopping svnserve!
I think I'll let the existing repository's mounted space go back into the pool
and just reserve a new one for the new repos, this way both can be active at the
same time. That'll make things more straightforward.
From: Andy Levy <andy.levy_at_gmail.com>
To: Christopher Nagel <chrisnagelmiami_at_yahoo.com>
Sent: Mon, August 2, 2010 9:22:18 AM
Subject: Re: Moving NAS owner and upgrading?
On Sat, Jul 31, 2010 at 14:41, Christopher Nagel
> This may resolve to a fairly simple operation, but right now I'm a bit in
> the weeds and would like to ask your help in charting the best course
> I administer the SVN repository for our workgroup. I started it on a found
> copy of svn 1.3.9, but was fortunate to get the repository stored on a NAS
> mounted at /svnroot. The SunOS box that svnserve runs on is being
> end-of-lifed and we've gotten a shiny new virtual linux box to use. Sounds
> great, except now I have to make the move.
> I've considered the following:
> - add user svn to new system, ensure its UID/GIDs are same as on old system
> - install svn 1.3.9 on new system under new user
> - move the mount from old system to new, same mount point
> - restart svnserve and see if it works
> - upgrade svn to latest version in place
> - create new svn user
> - install latest version of svn
> - export repository on old system (hopefully enough disk space is around)
> - wipe disk, mount storage on new system
> - create new repository
> - import old repository to new (history is preserved?)
> - create new svn user and install latest svn on new system
> - move mount to new system
> - chown -R *
> - let svn update repository structure if it doesn't like it as-is
> What's the best way to do this? I'm no linux admin, just a developer who
> likes safe code...
Your middle option is best, especially since you're changing OS here
too. Shut down svnserve (just to make sure no one commits after you've
started your migration - that won't be a deal-breaker but it adds some
extra work you'll have to do), then run svnadmin dump to get a
portable representation of the repository. Install the latest
Subversion on the Linux box, create the repository, then svnadmin load
to import your repository. As usual, the fine manual provides:
By doing this, you'll keep your data safe *and* take advantage of the
many improvements made to Subversion and the back-end storage over the
years since 1.3 was released.
You'll also want to look over the Release Notes as they have some
information on upgrading as well.
Received on 2010-08-02 23:02:32 CEST