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

Re: Merge of 2 separate subversion installations.

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Fri, 30 Jan 2009 13:56:28 -0600

Patricia A Moss wrote:
> Les,
> First, thank you for answering all of my questions. There are a
> couple more things that I would like to get cleared up.
> 1. So, a dump is not the same as a Unix tar command. If I were to
> tar /home/testrepo and then restore it I would get the full directory
> structure of /home/testrepo restored to whatever path I used in the untar.

Correct. A tar backup/restore might work when the source/destination
servers and subversion versions are similar. Svnadmin dump generates a
portable format and gives the loading version a chance to optimize the

> When I give a path for the dump I am simply pointing to the area by which
> to get the data to dump from? Is that a correct statement?

Yes, svnadmin needs file-level access and this is the file-level path to
the repo.

> 2. Since these repos are going to a new server there is no "old
> one" to load into. So that would mean for every repo that I dump from the
> old server I would need to create a new/empty one on the new server;
> before I perform, the load?


> 3. By creating new/empty repos I keep the integrity of the
> revision numbers?

Yes, and you can maintain (or not) the original repository UUID. If you
keep it, clients will be able to use svn switch to move a checked out
copy to point to the new repo. If you don't, the clients will have to
check out fresh copies.

> 4. Dumping from an older version and then loading into a newer
> version of Subversion will not cause any issues?

No, the dump format is designed to accommodate that kind of change.

   Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-30 20:57:27 CET

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

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