CODEWITHSUNDEEP
svntortoisesvnvisualsvn-servervisualsvn
nonopolarity
nonopolarity

Reputation: 151046

How to move all source code over when it was on VisualSVN Server on Vista and migrating to Windows 7?

I had VisualSVN Server running perfectly on a Windows Vista machine, and then now it is to run Windows 7 on that same machine (installed on a new partition).

So now all the source code are in the repository on D: drive (it used to be on C:)

(Windows 7 will be C:, and the Vista will now become D:)

Can we just copy the D:\Repositories over as C:\Repositories, and then install VisualSVN Server on Windows 7 again and let it use C:\Repositories, and then all source code, all history (the diff and comment) will be available again?

Upvotes: 2

Views: 668

Answers (5)

bahrep
bahrep

Reputation: 30662

When you move VisualSVN Server from one computer to another you need to follow the steps specified in the article KB166: Migrating VisualSVN Server to another computer.

Note that in most cases you do not need to use svnadmin dump and svnadmin load in process of migration.

Upvotes: 0

nonopolarity
nonopolarity

Reputation: 151046

Yes, I tried it finally and it worked perfectly. A good thing is, I don't even need to add the project using TortoiseSVN on the new Windows 7 clients. It is added automatically from before (I think from the hidden .svn folders).

Upvotes: 0

Lasse V. Karlsen
Lasse V. Karlsen

Reputation: 391406

Yes, this will work, I've done the same myself when setting up a new server at home and restoring repositories from backup.

Just ensure the VisualSVN service user has authorization to write to the files in question (typical problem when copying files/folders from one system to another without the same users.)

Basically, install VisualSVN server, copy over the repositories, and restart the service, and if the authorization is in place, that's it.

You might also want to look into the Security settings in VisualSVN afterwards. I'm not 100% positive it stores them using the auth files in the repositories or if it keeps them outside (I suspect it stores them there, I'm just not 100% sure of it.)

Upvotes: 2

tster
tster

Reputation: 18237

A very similar move worked fine for me.

Upvotes: 2

si618
si618

Reputation: 16848

I'd say give it a shot, but take an svnadmin dump of the repository before doing so. If things don't work (try svnadmin verify, update a working copy on a different box, check the log history), then go down the usual path of svnadmin dump, create, load.

So long as the URL isn't changing, i.e. the server name stays the same, clients won't need to relocate their working copy.

Upvotes: 4

Related Questions