Home / server / Questions / 3972
Accepted
Jay R.
Asked: 2009-05-05 05:07:32 +0800 CST

What are the gotchas of moving an SVN server/repository from Linux to Windows?

  • 772

We have a server running Fedora 7 that we use as our SVN repository server. New IT policies where I work are mandating that we to a Windows box if we want to allow our server to be on the network.

What are the challenges that must be overcome to make this move? Some of these items may be used to get a policy exception in place.

windows linux svn

5 Answers

  1. Best Answer

    A little check-list:

    • Access method. If you access your SVN server via SSH, you might consider switching to HTTP since it's much more mainstream on Windows.
    • UUID. If you move your repo, just don't forget to make the old one either inaccessible or read-only. Then you can even reuse the same UUID, and enjoy the --relocate option of the switch subcommand on the client for a seamless relocation (no need for a fresh checkout)
    • Apache. You might already have an IIS (or another Web server on the box) so you should change the
    • Database. If you use FSFS as the repository database you can just copy it over. BDB requires a svn dump/load cycle. Think hard if you want to put your database on a network share : only FSFS will work (it's not really recommended though).
    • Users. You have to think about how your users will be authenticated. It may be as simple as copying a htpasswd file over.
    • SVN Version. Just beware that you use the same version of your SVN server. If not, you might require a svn dump/load cycle.
    • Hooks. If you have hooks on your SVN server, it is possible that you have to port them. Either by installing the same script language (think ActivePython or ActivePerl), or just rewrite them in vbs or equivalent.
    • Firewall. Just in case your server box is on a workstation edition, don't forget to open the firewall ports (quite trivial, but I got bitten once).
    • 7

  2. Not sure about all the details, but keep in mind any hooks/scripts you have running on your repository will need to be rewritten as batch files.

    • 6

  3. Dump/load would be the proper procedure and keep you safe from any problems. See the svn book

    • 5

  4. Running the VisualSVN Server on Windows has been very smooth. VisualSVN Server can host any number of independent Subversion repositories.

    You can move repositories by any Subversion recommended method, it's a standard repository on both sides. Note the repository version, you may need to upgrade. Access permissions are windows oriented, you may have to change the way clients authenticate against the server. Good luck with hook scripts, if any. I hope they are written in a portable scripting language, e.g. Perl or Python.

    • 4

  5. If you are attempting the move in reverse -- using svnadmin in Windows to make an dumpfile of a repository -- be sure to use the cmd.exe prompt and NOT the powershell.

    I did this and found out (the hard way) that redirecting output from the powershell results in a Unicode file that svnadmin cannot read when you go to load the same file into the destination repository. It also takes a lot longer to run (and, obviously, the file is twice as big).

    • 1