Hi,
I intend to run Subversion on a server with two separate disks. Both
disk are backed up on a distant server. One of the disks has plenty of
room and is planned to contain the repository, the other disk is smaller
and contains the /var directory in which I can write logs or smaller
files such as incremental dumps.
I need to be able to recover from the crash of one of the two disks -
*including* the latest commits.
I've read paragraph "Repository Backup" from chapter 5 of "Version
Control with Subversion" and paragraph "Backups" from chapter 3 of
"Practical Subversion". It's still not clear how to best handle this.
My intention is to perform a "hot copy" every evening from and to the
repository disk. The "hot copy" will be backed up when the back up
process runs later in the evening.
If the repository disk crashes, I'll lose the commits since the last
back up. The idea is to write incremental backups to the second disk
that contains /var. Using the last backed up "hot copy" and the
incremental backups, I should be able to recover the repository.
What's the best strategy? An incremental backup since the latest hot
backup of the repository with every commit? Are there any scripts that
do that ? I can use the hot-backup.py script for backing up the
repository, but I would still need a set of scripts to create the
incremental backup from the post-commit hook and maybe to delete old
incremental backups when a new hot backup is performed.
I guess this is similar to this thread:
http://svn.haxx.se/users/archive-2005-05/1147.shtml
Unfortunately the scripts do not seem to be available on line.
Dimitri Papadopoulos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 26 15:57:09 2005