On 2, are you doing a complete svnadmin dump or doing the 'hot backup'
python script? If your not doing the 'hot backup' python script, you may
want to look into this and schedule it regularly during the day (ie. 12 and
12 or 12, 6, 12, and 6). With incremental dumps , you'll want to dump each
commit (in the post commit hook script). Combined the 'hot backup', you can
recover from any point.
As far as your repository, I have no idea how to recover without an
incremental dump from each commit. At this point, you may want get the last
full dump you have that works and have all the user commit everything from
they have in their working copies currently. Unfortunately everything is
lost from that point on till when the your repository crashed.
Johnathan
On 6/26/06 10:59 AM, "Bryan D. Andrews" <bandrews@trendcore.com> wrote:
> Any thoughts on this? We are dead in the water.
>
>
> -----Original Message-----
> From: Bryan D. Andrews [mailto:bandrews@trendcore.com]
> Sent: Sunday, June 25, 2006 10:41 PM
> To: users@subversion.tigris.org
> Subject: Corruption
>
> We have a problem where somehow something was corrupted on a commit in a
> new directory added.
>
> We cannot do a complete dump now as it chokes on that revision:
> svnadmin: Can't read length line in file 'c:\svn\AppTheory\db\revs\2445'
>
> We cannot update from that directory either:
>
> Error: REPORT request failed on '/projects/!svn/vcc/default'
> Error: REPORT of '/projects/!svn/vcc/default': 200 OK (http://myserver)
>
>
> 3 questions:
>
> 1. we have had approximately 10 commits since then and I need to know
> the best way to deal with situations like this.
>
> 2. what is the best way to automatically backup in the windows
> environment. I do full dumps each night but now I am not sure of the
> integrity -- it still creates the dump files even though the dump did
> not complete successfully. I have heard that it returns codes but I am
> not sure how to retrieve them in my script.
>
> 3. Are their commercial products to help manage SVN and SVN backups?
>
> Any help is appreciated.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 26 18:14:11 2006