You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Patricia A Moss <pm...@csc.com> on 2009/01/30 16:01:02 UTC
Merge of 2 separate subversion installations.
I am running version 1.2.1 of Subversion on a RedHat 4.0 server. I have a
counterpart, in MA, that is about to install and begin implementing the
latest version of Subversion. I am not sure of the brand of OS that will
be used. My question is. If/when we decide to merge these 2 separate
installations into one, is there anything that would need to have been
done prior?
Is it as simple as doing a repo dump from the 1.2.1 version and then
restoring into the newer version?
Is there anything that the tech, installing the newer version, would need
to do at the time of setup to make the merge as seamless as possible?
Thanks
PATI MOSS
System Engineer Sr. Professional
CSC
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
delivery.
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
purpose.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1075170
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Merge of 2 separate subversion installations.
Posted by Andy Levy <an...@gmail.com>.
On Fri, Jan 30, 2009 at 12:55, Patricia A Moss <pm...@csc.com> wrote:
>
> Les,
>
> They are not the same projects. They are 2 separate installations
> 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 server.
> 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 directory?
You can host multiple repositories on one Subversion server (one box
AND in one server process). The fine manual outlines how. You won't
want to just copy the repository directories; use the dump/load cycle
outlined in the "Migrating Data Elsewhere" section of the manual.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1075896
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Merge of 2 separate subversion installations.
Posted by Patricia A Moss <pm...@csc.com>.
Les,
You rock! Thank you for clearing up all of my questions.
PATI MOSS
System Engineer Sr. Professional
CSC
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
delivery.
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
purpose.
Les Mikesell <le...@gmail.com>
01/30/2009 02:56 PM
To
Patricia A Moss/GIS/CSC@CSC
cc
users@subversion.tigris.org
Subject
Re: Merge of 2 separate subversion installations.
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
storage.
> 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?
Yes.
> 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
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1090105
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Merge of 2 separate subversion installations.
Posted by Les Mikesell <le...@gmail.com>.
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
storage.
> 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?
Yes.
> 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
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1076272
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Merge of 2 separate subversion installations.
Posted by Patricia A Moss <pm...@csc.com>.
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.
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?
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?
4. Dumping from an older version and then loading into a newer
version of Subversion will not cause any issues?
PATI MOSS
System Engineer Sr. Professional
CSC
575 E. Swedesford Road, Suite 300, Wayne, PA 19464
GIS | p: 610.989.7105 | f: 610.989.7100 | pmoss4@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
delivery.
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
purpose.
Les Mikesell <le...@gmail.com>
01/30/2009 02:18 PM
To
Patricia A Moss/GIS/CSC@CSC
cc
users@subversion.tigris.org
Subject
Re: Merge of 2 separate subversion installations.
Patricia A Moss wrote:
> Les,
>
> 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?
Yes, you can either create a new, empty repo and load it in at the top,
or make a new directory in your old one and load under that. The
differences will be that keeping thing separate will make the old
revision numbers remain consistent and make it easier if you ever want
to pull them apart again. Merging them might make maintenance of
authentication/access control easier.
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1076170
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Merge of 2 separate subversion installations.
Posted by Les Mikesell <le...@gmail.com>.
Patricia A Moss wrote:
> Les,
>
> 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?
Yes, you can either create a new, empty repo and load it in at the top,
or make a new directory in your old one and load under that. The
differences will be that keeping thing separate will make the old
revision numbers remain consistent and make it easier if you ever want
to pull them apart again. Merging them might make maintenance of
authentication/access control easier.
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1076107
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Merge of 2 separate subversion installations.
Posted by Patricia A Moss <pm...@csc.com>.
Les,
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?
PATI MOSS
System Engineer Sr. Professional
CSC
575 E. Swedesford Road, Suite 300, Wayne, PA 19464
GIS | p: 610.989.7105 | f: 610.989.7100 | pmoss4@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
delivery.
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
purpose.
Les Mikesell <le...@gmail.com>
01/30/2009 01:28 PM
To
Patricia A Moss/GIS/CSC@CSC
cc
users@subversion.tigris.org
Subject
Re: Merge of 2 separate subversion installations.
Patricia A Moss wrote:
> Les,
>
> They are not the same projects. They are 2 separate
installations
> 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
> server.
> 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
> directory?
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:
http://wordaligned.org/articles/one-svnserve-multiple-repositories
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.
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1076074
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Merge of 2 separate subversion installations.
Posted by Les Mikesell <le...@gmail.com>.
Patricia A Moss wrote:
> Les,
>
> They are not the same projects. They are 2 separate installations
> 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
> server.
> 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
> directory?
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:
http://wordaligned.org/articles/one-svnserve-multiple-repositories
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.
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1075908
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Merge of 2 separate subversion installations.
Posted by Patricia A Moss <pm...@csc.com>.
Les,
They are not the same projects. They are 2 separate installations
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
server.
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
directory?
Thanks
PATI MOSS
System Engineer Sr. Professional
CSC
575 E. Swedesford Road, Suite 300, Wayne, PA 19464
GIS | p: 610.989.7105 | f: 610.989.7100 | pmoss4@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
delivery.
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
purpose.
Les Mikesell <le...@gmail.com>
01/30/2009 12:21 PM
To
Patricia A Moss/GIS/CSC@CSC
cc
users@subversion.tigris.org
Subject
Re: Merge of 2 separate subversion installations.
Patricia A Moss wrote:
> I am running version 1.2.1 of Subversion on a RedHat 4.0 server. I have
a
> counterpart, in MA, that is about to install and begin implementing the
> latest version of Subversion. I am not sure of the brand of OS that
will
> be used. My question is. If/when we decide to merge these 2 separate
> installations into one, is there anything that would need to have been
> done prior?
> Is it as simple as doing a repo dump from the 1.2.1 version and then
> restoring into the newer version?
> Is there anything that the tech, installing the newer version, would
need
> to do at the time of setup to make the merge as seamless as possible?
> Thanks
Are you developing the same project(s)? If you are, there isn't a good
way to maintain or merge duplicate repositories. If you aren't, you
don't really have to ever merge them unless you want to. Merging will
break any revision number references you might have to the old history
(like in trouble tickets, etc.) for the one that is merged. You can
simply move them to the same server as separate repos if you want. If
you use http(s) access you can make separate repositories appear under
the same URL anyway.
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1075699
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Merge of 2 separate subversion installations.
Posted by Les Mikesell <le...@gmail.com>.
Patricia A Moss wrote:
> I am running version 1.2.1 of Subversion on a RedHat 4.0 server. I have a
> counterpart, in MA, that is about to install and begin implementing the
> latest version of Subversion. I am not sure of the brand of OS that will
> be used. My question is. If/when we decide to merge these 2 separate
> installations into one, is there anything that would need to have been
> done prior?
> Is it as simple as doing a repo dump from the 1.2.1 version and then
> restoring into the newer version?
> Is there anything that the tech, installing the newer version, would need
> to do at the time of setup to make the merge as seamless as possible?
> Thanks
Are you developing the same project(s)? If you are, there isn't a good
way to maintain or merge duplicate repositories. If you aren't, you
don't really have to ever merge them unless you want to. Merging will
break any revision number references you might have to the old history
(like in trouble tickets, etc.) for the one that is merged. You can
simply move them to the same server as separate repos if you want. If
you use http(s) access you can make separate repositories appear under
the same URL anyway.
--
Les Mikesell
lesmikesell@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1075561
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].