Re: repository on client is newer than on server as a result of server hd failure

> And what happens if two users commit changes one right after one the
> other? I'd expect the two dump processes together to clobber the
> dumpfile. Doesn't sound like such a great strategy, unless you've
> built in some mechanism that you're not showing that ensures only one
> dump process runs at a time.

Yes, the script shown is an overly simplified version of what I did. In
actuality, I am dumping to a temp file (name by time stamp), and once
the dump is finished, then I copy the temp file to its final destination
and rename it to the proper name (project.svnduimp or something).

Of course, this puts a dent on the overall performance, especially when
you have many commits back to back for the same repository, but it works
well for me. I have a repository that does not get as many commits
(maybe a dozen a day), but it is crucial that I do not lose any
revisions. So I am willing to sacrifice a little performance for that.

Actually, this works pretty well for me so far, the backup is completely
transparent to the users, they do not see any delay when comitting.

Thank you for pointing that out :-)