Thank you for your comments, Andreas:
> Literally any situation where the undesired change to be
> recovered from happened before this last and single copy
> was taken.
I am going to prevent this by means of `svnadmin verify':
> > Is it practical to call it [verify] daily with a several
> > Gb, several thousand-revision repository?
>
> Again, you don't need to care about how long the backup
> takes. Only about it's consistency and the time to restore
> in a restore event.
Then I propose the following strategy:
1. Maintain a repository mirror by calling
svnadmin hotcopy --incremental
from a post-commit hook.
2. Store the last verified hot-copy in an archive:
a. make a hot copy of the mirror
b. verify this secondary hot-copy in order not to lock
the mirror for a long time,
c. archive the secondary hot-copy in a format with error-
correction, such as .rar. I haven't found a free,
stable, and easiliy available archiver with built-in
error-correcion.
Of course, my script will notify the administrator of errors
at any step.
--
Please, do not forward replies to my e-mail.
