> It is ok to allow my network admin to tape-backup my fsfs
> repositories? I've got him to exclude the db\transactions folder.
> No danger of any locks during backup causing screw-ups if I try to
> commit at the same time??
Here is what my FSFS notes
(http://svn.collab.net/repos/svn/notes/fsfs) say about backups:
Naively copying an FSFS repository while a commit is taking place
could result in an easily-repaired inconsistency in the backed-up
repository. The backed-up "current" file could wind up referring to
a new revision which wasn't copied, or which was only partially
populated when it was copied.
The "svnadmin hotcopy" command avoids this problem by copying the
"current" file before copying the revision files. But a backup
using the hotcopy command isn't as efficient as a straight
incremental backup. FSFS may evolve so that "svnadmin recover"
(currently a no-op) knows how to recover from the inconsistency
which might result from a naive backup.
Naively copying an FSFS repository might also copy in-progress
transactions, which would become stale and take up extra room until
manually removed. "svnadmin hotcopy" does not copy in-progress
transactions from an FSFS repository, although that might need to
change if Subversion starts making use of long-lived transactions.
So, if you are using standard backup tools to make backups of an
FSFS repository, configure the software to copy the "current" file
before the numbered revision files, if possible, and configure it
not to copy the "transactions" directory. If you can't do those
things, use "svnadmin hotcopy", or be prepared to cope with the very
occasional need for manual repair of the repository upon restoring
it from backup.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 7 00:19:43 2004