--- brane@xbc.nu wrote:
> Quoting Neal Jhala <njhala@yahoo.com>:
> > input: python.exe hot-backup.py d:/svn d:/svn_backup >>
> > d:/svn_backup/hot-backup.log
> >
> > hot-backup.log output with errors:
> > Beginning hot backup of 'd:/svn'.
> > Youngest revision is 9755
> > Backing up repository to 'd:/svn_backup\svn-9755'...
> > Unable to backup the repository.
> >
> > hot-backup.log output with no errors:
> > Beginning hot backup of 'd:/svn'.
> > Youngest revision is 9853
> > Backing up repository to 'd:/svn_backup\svn-9853'...
> > Done.
> > Removing old backup: d:/svn_backup\svn-9424
> >
> > It fails roughly 25% of the time, so pretty hard to reliably reproduce.
> > Any way to get more debugging info from the hotcopy command?
>
> What happens if you just run "svnadmin hotcopy repos backup --clean-logs"? If
> that fails, I presume it prints some output to stderr (which, BTW, you didn't
> redirect to your log file).
>
> Brane
I tried running svnadmin hotcopy directly, instead of via hot-backup.py, and
was lucky enough to get it to fail. The error below is a little more useful
than the "Unable to backup the repository" message which apparently
hot-backup.py translates from an error status of the svnadmin hotcopy call.
>svnadmin hotcopy d:\svn d:\svn_backup\test --clean-logs
svn: DB_RUNRECOVERY: Fatal error, run database recovery
I also ran svnadmin verify on the resulting d:\svn_backup\test, and it verified
successful to the last revision, so apparently it completed part of the
hotcopy, but not all steps? Original repository is fine. I assume the error
above is referring to db recover on the backup repository?
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 10 22:11:50 2004