On Oct 31, 2006, at 12:03, Dennis Allen wrote:
> A team member (who is no longer here) had a repository installed on
> his local machine. I want to move that repository that to a
> publicly accessible server, and allow others to access it. The
> move should retain any history. Also, I will want to rename the
> root folder on the new server.
>
> Background: The server uses svnserve (not Apache) and all of the
> clients will use either Tortoisesvn or the Eclipse plug-in. The
> repository is the OS file system option.
>
> Do I just:
> a) Copy the repository directory (XCOPY) to the new server. Then
> do a "switch" ??? on the client machines?
You can do this, if the repository is FSFS-based, or if the
repository is BDB-based AND both servers have exactly the same
versions of BDB.
> or
>
> b) Do an export then re-import?
You would lose the history, which you say you don't want to do, so
don't do this.
> or
>
> c) Your steps here...
You could "svnadmin dump" the old repository on the old server, then
"svnadmin load" the dumpfile into a new repository created on the new
machine with "svnadmin create". This is the way that you would
migrate between BDB versions, and this is the way that you would
migrate from a BDB- to an FSFS-based repository, and this way will
always work, whereas simply copying the repository might not. But
don't forget to also manually move any hooks and config files as
these are not preserved in a dumpfile.
> I have tried a variation on "a" above and ran into problems where
> the client complained that the file(s) were already linked to
> another repository, so I must be doing something wrong.
As someone said, you need not "svn switch" but "svn switch --relocate".
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 31 20:40:45 2006