Féliciano Matias <feliciano.matias@free.fr> writes:
> Le sam 13/07/2002 à 00:54, Ben Collins-Sussman a écrit :
>
> > To me, a backup is something you quickly copy to tape every night --
> > or in our case, after every single commit. It needs to be fast. It
> > exists for the short-term only; there's no worry that I suddenly
> > won't have the right tools around to read the backup.
>
> I keep in mind that restoring a backup is the last chance when every
> thing go wrong.
That's true. But... if you need to restore a svn repository backup,
after a catastrope, you need the subversion program no matter what.
You either need 'svn' to read the berkeley repository directly, or you
need 'svnadmin' to load the dumpfile into an empty repository. They
both depend on libsvn_fs.so.
Either way, you need to compile subversion. When my computer bursts
into flames, I'm not particularly worried about which DB backend of
subversion I'm going to need to compile on my new computer. It's not
like the source code is going to vanish suddently. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 13 03:09:48 2002