[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Repository migration between different access methods

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Wed, 2 Sep 2009 14:12:42 +0100

2009/9/2 el_es <el.es.cr_at_gmail.com>:
> Hello,
> I am about to migrate the repository of SVN, created with Tortoise, to a
> Linux-based server (running Ubuntu Intrepid).
> Which method is better (after setting server access and paths that is) :

This is a server question so it should really be asked on the
subversion users list.

> 1) copy the repository files from the Windows machine to where I want to have
> them served (it is the native FS it's created on the current host) on the Linux
> machine,

I'm not sure if the repository is portable between architectures. Best
to assume that it is not.

> 2) set up server access in Tortoise and use it to import project(s) to the Linux
> server ?

Not sure what you mean by this. Import is a client operation, but it
does not retain history.

The proper way to do this is to use a dump/load cycle as described in
the subversion book. Dump your existing repository content (creates a
very large file). Copy that file to the Linux server and load it into
a fresh repository. You will need to set the UUID of the new
repository to match the old one if you want to avoid making fresh

Once the new server is running you will need to relocate your existing
working copies to point to the new server. Or make fresh checkouts.

> The repository so far only hosts projects written by one man (me and my
> predecessor, but not at the same time) and now I need to set it up so another
> man can access it, preferably preserving the history - so the import is probably
> preferred? If the copy method could work, I'd probably need to run svn files via
> dos2unix (for cr-lf conversion) ? (the project(s) files however, are supposed to
> be Windows only)
> After the migration, I will only use server connection (will not use the local
> repository any more)

Glad to hear that. Best to move the repository folder to avoid
accidental commits.

> Of course I could do just import the project from working copy, or from export;
> effectively zeroing the history, but that would probably be the lats thing I
> want to do.
> Anybody ever done that ? Pointers? (I searched the group over for 'migration'
> (yay for gmane.org search engine)
> Btw, which method of access is :
> -faster at local network level (comparable to samba file transfer) (I gather,
> WebDAV?)
> - secure at the outside access (Webdav over https?)
> at the same time ?
> - easier to set up than svn:+ssl (WebDAV+https?)
> Am I thinking correctly here ?

Not sure what you are thinking.

svnserve (svn://) is generally faster than apache (http://) and works
well over a LAN and over my broadband connection from home. It is very
easy to set up.

svnserve now supports SASL security, which should also be easy to set up.

But, setting up a linux server is definitely outside the scope of this
list. You need to ask these questions on the subversion users list.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-09-02 15:13:03 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.