You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Andy Levy <an...@gmail.com> on 2010/08/02 13:22:18 UTC
Re: Moving NAS owner and upgrading?
On Sat, Jul 31, 2010 at 14:41, Christopher Nagel
<ch...@yahoo.com> wrote:
> 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
> forward.
> 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
> Or:
> - 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?)
> Or:
> - 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:
http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate
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.
http://subversion.apache.org/docs/release-notes/1.6.html
http://subversion.apache.org/docs/release-notes/1.5.html
http://subversion.apache.org/docs/release-notes/1.4.html
Re: Moving NAS owner and upgrading?
Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
On Monday 02 August 2010, Christopher Nagel wrote:
> 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.
That doesn't sound like a good idea. If I get you right, you don't want to
start a new repository but only move the existing one. Leaving both in place
presents the danger that people commit to both repositories, unless you take
other measures to prevent that.
That said, by all means preserve the old repository until the new one is in
place and running, otherwise be prepared to restore from a backup. Just in
case.
Uli
--
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
Re: Moving NAS owner and upgrading?
Posted by Christopher Nagel <ch...@yahoo.com>.
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.
Best regards,
Chris
________________________________
From: Andy Levy <an...@gmail.com>
To: Christopher Nagel <ch...@yahoo.com>
Cc: users@subversion.apache.org
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
<ch...@yahoo.com> wrote:
> 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
> forward.
> 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
> Or:
> - 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?)
> Or:
> - 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:
http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate
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.
http://subversion.apache.org/docs/release-notes/1.6.html
http://subversion.apache.org/docs/release-notes/1.5.html
http://subversion.apache.org/docs/release-notes/1.4.html