Thank you for your answers. Currently I've setup svnsync and I am doing test run of synchronizing repositories. I will have a small window to migrate repositories. Using the svnsync gives me possibility to do major job before the change window and then final sync during the change.
In this step I have some doubts whether users will have possibility to relocate their local copies to new repository on new server. The first step of sync procedure is to create fresh repository, I am afraid that it will have different ID and svn will say “its not the same repository” I will test it but you are welcome to give me your comments. I have about 400 repositories to migrate. Svnsync showed about 60 -70 hours to sync all repos. Thanks much Leszek Szarlej On 11 August 2010 15:50, Stefan Sperling <s...@elego.de> wrote: > On Wed, Aug 11, 2010 at 09:11:29AM -0400, Edward Ned Harvey wrote: > > As far as subversion is concerned, as long as you get it installed, there > is > > nothing for you to think or care about. > > It depends on the Subversion repository backend. > > If the BerkeleyDB backend is used, a dump/load cycle is probably necessery, > so just do it to be on the safe side. > > With repositories using FSFS, there is nothing to worry about. > > The file "db/fs-type" in a repository tells you which kind of backend > the repository is using: "bdb" or "fsfs" > > Stefan >
