Howdy -
I'm attempting to implement a warm backup strategy with two machines
and no shared storage using 'svn hotcopy' as a post-commit hook, something
like so:
commit happens
svnadmin hotcopy /live/repos/ /backups/repos/
commit returns
time passes...
cron wakes up and runs
rsync --checksum /backups/repos/ backupmachine:/live/repos/
When the svn server fails, we can mangle dns, start apache on
backupmachine: and be up and running inside 10 minutes. That's the
plan, anyway. Test runs bear this out to a greater or lesser degree,
so I think the theory is sound for a first pass. (If this ends up proving
workable, I may work towards real failover, but first thing's first.)
My biggest problem is the post-commit hook calling svnadmin hotcopy.
The repository (fsfs) only weighs in at 120MB, but it's taking between
20 and 30 seconds for the hotcopy to come back, with the client's
checkin transaction dutifully waiting. I fear this pause will be too
long for users.
I don't think this is a bug - more than likely is fallout from the
desktop-class machine (and its disk) subversion's running on (in which
case "upgrade your server" is an acceptable answer to my problem).
Are other folks doing hotcopy-from-post-commit running into this
situation? If so, how are you dealing with it?
What other alternatives can I consider?
Can one convince hotcopy to do incremental / overlay or something?
Are the backup options like so? (no new hardware purchases if possible)
(1) asynchronous (hourly?) hotcopy
(2) asynchronous (hourly?) dump mixture of full and incremental
(3) svnadmin dump incremental in a post-commit hook
(4) filesystem-level copies (scp, cp, rsync)
(5) filesytem replication (coda, lustre, drbd)
Or if I involve non-filesystem things
(1) svnsync
(2) svk
I think my best fallback option might be svnsync, but I'm running
on fedora5 and haven't seen updated packages (I'd prefer that to
attempting to build from source - anybody know when those will be
released, or where to go to find out?).
Thanks in advance for your help.
Cheers
- Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 1 22:51:08 2006