[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SourceSafe to SVN

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Fri, 22 Aug 2008 09:56:14 +0100

2008/8/22 Stefan Küng <tortoisesvn_at_gmail.com>:
> Simon Large wrote:
>> 2008/8/22 kevin <kcocol_at_gmail.com>:
>>> In SourceSafe (SS) we run daily jobs to ensure the DB is sound. If
>>> not, we can run jobs to correct. Does SVN require anything like this?
>>
>> No. VSS is notorious for its DB corruption, and MS's recommendation
>> that you check for corruption is an admission that it is completely
>> broken. SVN is *much* more robust and this sort of daily check simply
>> isn't necessary. That's not to say you don't need a backup, just as
>> you do with any important data.
>
> http://svnbook.red-bean.com/en/1.4/svn.ref.svnadmin.c.verify.html
> http://svnbook.red-bean.com/en/1.4/svn.ref.svnadmin.c.recover.html

I had forgotten about svnadmin verify. Sure, it's a good idea to
verify periodically, but you don't need to do this every day, or
before you checkout a working copy. SVN is most definitely NOT
SourceSafe.

svnadmin recover is only for BDB repositories, and I believe it only
runs incomplete commands when the repo is wedged. I don't think it can
recover from corruption. AFAIK it is a no-op for FSFS repositories.

Simon

-- 
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-22 10:56:27 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.