Basically, this job is as easy as:
- Dump the repository on the old server
- Load the dump into a new repository on the new server
Dumping is explained here, and I won't go into detail because I wasn't the one doing it, Roman did it (I ain't touching a BSD box, more harm than good would result).
However, step two is in my ballpark, because the repository is moving to a Windows box. Two commands and you are up and running again (it can take quite some time, especially if your dump is like mine - a little over 528 MB!)
svnadmin create c:\repositories\fidalgo
svnadmin load c:\repositories\fidalgo < "e:\fidalgo.dump"
All that is left to do now is to restore the configuration and hooks (details in my last blog post on Subversion)
In closing, credit where credit is due: I gathered some inspiration from the following blog entry: A Rank Amateur Upgrades His Subversion Repository
Remember me complaining about InCD and how it gobbles up memory so you cannot use more than 1GB of physical memory with VirtualPC? Well, sometime in December I threw v18.104.22.168 off my machine to finally be able to use the full 2GB. Today I decided to risk a reboot or two to give v22.214.171.124 a shot - and Jehova! the new version works as expected. No more out of memory issues! Using InCD? Get the latest version here.