Thanks for the advice folks. I have already practiced with the dump/load cycle and it works smoothly and without pain. I just need to test with Tortoise, etc before the official switch over.
From: Andy Levy [mailto:email@example.com]
Sent: Mon, 23 Jul 2007 05:14:01 -0700
Subject: Re: Migration Question
On 7/23/07, Simon Large <firstname.lastname@example.org> wrote:
> On 23/07/07, Dave Lawrence <email@example.com> wrote:
> > Simon Large wrote:
> > > On 20/07/07, Robert Denton
> > > <firstname.lastname@example.org> wrote:
> > >> My question concerns how I should handle TortoiseSVN installations in my
> > >> company, given a current migration that is occurring:
> > >>
> > >> I am in the process of migrating a subversion 1.3 repository on a windows
> > >> server to a subverion 1.4.3 repository on a linux server. Members of the
> > >> subversion mailing list assure me that this should not be a painful
> > >> process
> > >> as long as I use the svnadmin dump and load commands wisely.
> > >
> > > In fact you don't even need to do a dump/load cycle. The repo format
> > > is compatible. However, I believe you will benefit from better
> > > compression if you do.
> > -- Not quite true. I'm sure I read that the bdb format cannot be
> > transferred from one filesystem to another. But the default format is
> > FSFS - it is likely that is the one you are using. In that case you can
> > just copy it - we copied ours from a windows 2000 system with NTFS to
> > a Ubuntu linux system with FAT32 without problems.
> > Still a dump load cycle is very straightforward.
> Oops, well spotted. I saw the 1.30 to 1.4.3 and missed the Windows to
> Linux bit. The rest of the questions were about client/server
> compatibility, so the answers to those are still correct.
IIRC, even staying on the same OS, if you're using BDB and change SVN
versions a dump/load cycle is recommended.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Jul 24 01:07:27 2007