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

Re: SVN Help: Repository migration from one server to another

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: Tue, 8 Sep 2009 15:50:08 +0200

On Tuesday 08 September 2009, Krishnamoorthy wrote:
> We are in the process of having a single repository for multiple
> projects. In our projects, we come across the following requirements. Is
> there any possibility to achieve this without the loss of history?
> 1. Move a repository from one server space to another server without
> losing the history.

This has pretty little to do with TSVN, since TSVN is rather an SVN client.
The server typically runs a vanilla SVN installation. Therefore, this is
better asked on the SVN mailing list.

However, let me ask you a question: If you don't know how to do that, how
would you ever recover your repository after e.g. a fatal hardware failure?
Seriously, this recovery process is part of your backup strategy and you
absolutely must test it. SVN is not a backup tool that magically preserves
your data when the server goes up in flames.

In order to move a repository, you would normally use 'svnadmin' to dump and
load it. All that is documented, just look for 'svnadmin', 'dump' and 'load',
that will get you started.

> The target server is already populated with a repository (not actually
> merging but moving). Here we need to move a current working repository
> from its own server to another server as a second project. While doing
> this, there is a risk of losing the history, but we need to retain that.
> How to achieve this?

Wait: Firstly, you can have multiple repositories on one server, so it might
be easiest to do just that and keep the separate projects in separate

If you really want to merge repositories including their history, you need to
dump/load them, using svndumpfilter on the intermediate dump files. Do a
websearch on this, the problem isn't new and the various solutions aren't

> 2. After moving the repository, we have two working copies for those two
> projects (as stated above).

Typically, you can check out as many working copies from a repository as you
want. Those are considered scrap space to work on and then throw away when
not needed any longer. I guess you either mean directories inside the
repository or maybe something different. Please reread the documentation, the
term "working copy" is defined there, so that you don't confuse it with
anything else.

> But the issue is that we need to keep track
> of revisions separately for each projects. Is this possible? If so,
> please guide us to achieve this.

"keep track of revisions separately" - what does that mean? Do you mean that
you want the revision numbers used by SVN internally to be separate? In that
case, again, read the documentation (I believe that even is an FAQ entry). In
short, it isn't possible.

BTW: You will need the "svn relocate --switch" command to reuse existing
working copies when moving repositories.


ML: http://tortoisesvn.tigris.org/list_etiquette.html
FAQ: http://tortoisesvn.net/faq
Sator Laser GmbH
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.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-09-08 15:50:33 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.