Re: Repository failover

[Mahantesh M Vantmuri]

Mark wrote:

> Haven't looking into this much, but if CVSup can send based on date, maybe it
> can be used to assist failover. Any thoughts from those that have used/are
> using CVSup?
> [...]
We are using cvsup as a repository syncing tool. The cvsup client, 
running on machine having local repositiry, gets the changes that were 
made on the remote repository every one hour. As others mentioned 
earlier in this thread, the local repository becomes read-only which 
means we can use it for only updates but not for commits. If we have to 
commit we do need to change our CVSROOT to the remote  repository 
through some tcl script.

So in the similar way we can have failover repository by using CVSUP. 
Have two repositories on two different machines one being read-only, and 
the other write also(but end users or users can completely ignore the 
existance of the backup repository). Have one cron job to pull changes 
done  on main repository. In case something happens to main repository, 
you can immediately, stop CVSUP activities on backup cvs server, and 
change permissions on modules on backup cvs server and  put it on to 
production as mail repository(Do remember that one needs to again setup 
CVSUP server and similar backup server for this server which just now 
came as production server for CVS)

I hav'nt come acoss clustering kind of CVS servers which will take care 
of repositories as soon as one of the servers gets corrupted. Do have a 
look as DCVS also.

Cheers.
Mahantesh.