Hello,

I know little if anything about svn, so need your assistance. I have a linux server running svn. I have a Windows server running svn. First, I'm looking for a way to copy an svn repository from the linux server to a new Windows server repository. I've looked for how to do this on the Internet and within the Apache.org website(which is now the maintainer of SVN).

I haven't found anything on a very granuler way to copy a repository from one O/S to another other than folks say it can be done. Not how.

Second, is there a way to automatically do this on a regular basis? I see the manual process of svnadmin dump and svnload. Also there is a manual process of svnadmin hotcopy.

I'd appreciate any input on how these two things may work. Anyone have any experience on how to do these two things?

Thanks very much for your time and consideration.

Blaine

Hello,

Have a look at these two sites, you'll get moving your data pretty fast.

Migrating repository data elsewhere
Step by step: moving a subversion repository to another server

About automating, you have the disadvantage of working with two operating systems, so I would think you'd need to script something in a language that's supported on both OS, like Python for example, for the automation process.

Kind regards,

Eric

Thanks, EricTRA!

I'll look into the two sites you suggest. As far as scripting between the two O/S's, would you think this would be a onetime process for the first transfer then incremental transfers after that? Sorry, I'm not a coder and will have to get with the developers on both ends of the O/S stream.

Thanks again for your time and consideration...

Blaine

Hi,

You're welcome. Are you going to maintain both repositories, one being a copy of the other? May I ask why? Because I don't see a direct use for that.

Kind regards,

Eric

Thanks for asking, Eric...

In a nutshell, we're in a tight spot for our code repository. I'm trying to come up with the safest and most cost effective means of having the repository backed up and immediately available should the primary server go down.

The primary is an old linux box and the corporate server(in another geographical location) is a new Windows server running the Windows version of svn.

Not exactly my choice, but I have to play the cards I'm given.

Perhaps you know of a better way?

Blaine

Hi,

If it's just for backup purposes, then why don't you make a svndump on a regular basis with a script running through crontab and copy that dump over to the Windows server? In case the Linux box goes down, you'll be able to import the dump instantly on the Windows server and all your users have to do is sync with the Windows version of Subversion. Just an idea. The fact of having two copies of the same code available is asking for trouble since you can never trust all your users to play by the rules. Having two copies will surely get you in trouble after some time, having different versions of the same code on the two repositories. You'll loose a lot more time when you need to solve that kind of problems then when you have to import a dump file in my opinion.

Kind regards,

Eric

Ah! That makes sense... I tried a modification of what you suggested using a crontab entry in a cygwin terminal on the windows server and it seems to work like a charm.

Thanks for teh help and validation!

Blaine