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

Failed backup - restore help request

From: Ken Mankoff <mankoff_at_gmail.com>
Date: 2006-06-13 19:07:04 CEST

Hi svn users,

We just lost our disk, and restoring from backup has raised some
problems. It appears that I was doing our backups incorrectly. I was
using a simple copy command (not even svn dump) rather than
'hot-backup.py' or 'svnadmin hotcopy'

The copy was done via cron, but since I am the only developer, I was
not too concerned about backing up a corrupt file. I know for
*certain* that the latest backup was not done at the same time as a
commit.

To restore, I simply copied repos/ back to where it was before. If I
do as svnadmin verify, it appears to work:

$ svnadmin verify ./repos/
* Verified revision 0.
* Verified revision 1.
...
* Verified revision 242.
$

However, the latest revision is 553, and this can be seen in
repos/db/revs/.

Why is svn not seeing 243 and beyond? Any advice to recover this
data? All other commands I type imply everything is healthy with the
repository. lstxns does show a revision beyond 242, but does not
appear to have a problem with that...

$ svnadmin lstxns ./repos/
2-1
298-1
232-1
72-1
$

$ svnadmin recover ./repos/
Repository lock acquired.
Please wait; recovering the repository may take some time...

Recovery completed.
The latest repos revision is 242.
$

Thanks in advance for any help,

   -k.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 13 19:11:30 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.