> From: "Dave Neary" <david@phenix.fr>
[snip]
> There are of course other ways to obtain the same result - by backing up
> all of the berkley DB transaction logs before deleting them, you can (in
> principle) rebuild an entire Berkley database without even having
> subversion on there by replaying all the transactions. This also gives a
> way to do an incremental back-up - you are only backing up the most
> recent DB log files.
Still new to svn, but here's a thought. Looking in my very simple
test repository, and based on the name of the log files I see there,
it looks like new log files may be generated from time to time. Too
bad, because it would have been simple, using softlinks, to keep the
log files on another filesystem otherwise. Is there a configuration
option someplace that controls where to put the log files?
If there WERE a way to create them in another filesystem, then would
they not actually serve as online backup files? Of course you need
to have 100% faith in the logging and restoring capabilities of the
log files (from my own experience I know this can be problematical.)
Just don't delete the log files until you've done a complete backup
of the repository.
(A)
If the primary disk fails or the repository is damaged in some way,
use the log files to do a restore.
(B)
If the log file disk fails or the log files are damaged in some way,
the repository is still there, undamaged.
(C)
If there's an svn, db, or other related software problem then you're
in big trouble anyway, backups or not.
Raye.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 28 19:02:33 2004