In my first inquiry I asked "Is it as simple as doing a repo dump
from the 1.2.1 version and then restoring into the newer version?"
So, my understanding of your explanation is that svnadmin dump
path-to-repo > dumpfile is the best way to get them moved.
Then you say that I have a choice as to where they get loaded, on
the new server. So, I have a question about that.
If I use the following example: svnadmin dump /home/testrepo >
testrepo.dump to create my dump file and then move it over to the new
server and run the command svnadmin load path-to-repo < testrepo.dump; it
is this "path-to-repo" that affords me the choice of location to load?
System Engineer Sr. Professional
575 E. Swedesford Road, Suite 300, Wayne, PA 19464
GIS | p: 610.989.7105 | f: 610.989.7100 | pmoss4_at_csc.com | www.csc.com
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
Les Mikesell <lesmikesell_at_gmail.com>
01/30/2009 01:28 PM
Patricia A Moss/GIS/CSC_at_CSC
Re: Merge of 2 separate subversion installations.
Patricia A Moss wrote:
> They are not the same projects. They are 2 separate
> that will contain totally different projects. What, I believe, is going
> to happen is in our second quarter they are going to purchase a high
> capacity server. Which will be used to house a single subversion
> installation. The repositories from the 1.2.1 version and the
> repositories from the second installation will be combined onto this one
> So, you are saying that I can just move the repositories to the new
> server? Is there a specific command or do I just move the entire
It is always best to use svadmin dump and load operations since they
deal with differences between server versions, etc.. But, you have your
choice as to whether you load into some directory in the old repo (which
will change all the revision numbers in the part being loaded but
otherwise keep the history) or create a new empty repo and load there.
If you are using svnserve you can do something like this:
And likewise with http(s) access you can just put multiple repos under
the same top level directory it is serving.
Note that the dump/load won't take hook scripts or authentication or
access control configuration, so you will have to copy those separately
if you have any.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-30 20:09:50 CET