Re: Safe to backup if failed svnadmin verify?

No and Yes. It's not practical continue the backup if the verify failed. But if your backup is not overwriting a previous backup, you could continue, but your backup will not be complete if your dumping the repository. If you running the hot backup script. It'll do the job, but you still have the bad revision or revision(s) and your verify will still fail.

When we discovered we had about ten bad revisions, our repo was still working and functioning correctly until we got those revisions fixed by CollabNet and dump and reloaded the repository with the correct revisions. By the way, our repo was corrupted due to a hardware issue and not Subversion/Apache.

Johnathan

>>> On Thu, Apr 26, 2007 at 7:59 PM, in message <f0rhte$vms$1@sea.gmane.org>,
"Mark Clements" <gmane@kennel17.co.uk> wrote:
> I have setup a nightly backup script to do hotcopy and a dump of my
> repository.
>
> I also have a script that runs svnadmin verify and sends me an e- mail if
> there is a problem.
>
> My question: Is it safe to run the backup if 'verify' failed? Old backups
> are kept, so there is no issue about bad backups overwriting good ones, just
> whether I could further damage the repo.
>
> I guess a secondary question is whether there is any point - i.e. will the
> backup succeed, and will the backups be usable (aside from the damaged
> revisions, obviously).
>
> - Mark Clements
>
>
>
> ---------------------------------------------------------------------
> 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 Fri Apr 27 15:22:43 2007