6
votes

We have just had a file server fail which contained our SVN repository.

We're trying to recover the file system but at the moment, that looks like it isn't going to happen so we're looking at backups.

The best full backup that I have available is one week old.

My plan is to restore this backup to a new SVN server. Then run through every developers machine and check latest revision numbers, then manually export the latest version of each project and commit it all to the new server.

My question is, does anyone have an experience of this? My plan is very much a manual one and therefore prone to errors!

The server we use is Visual SVN and the client we use is Tortoise SVN.

Any suggestions would be appreciated.

1
I sure hope you will now backup more frequently than once a week.JoshD
That is the nice thing about a DVCS: Everyone has everything, so there is no single point of failure. With Subversion, you can set up a mirror repository that gets a copy of every single commit as soon as it comes it.Thilo

1 Answers

4
votes

Surely there is no automatic method.

I would do it this way: After restore, I go to each developer, re-checkout projects, write over with their local files, commit. Pay attention to .svn folders - you should not copy them over (You can set Total COmander to ignore them).