[cvsnt] Opinion: open source-"supported" CVS backup capabilities are very weak

Philip Bondi pjbondi at SystemDatabase.com
Mon Jan 7 03:29:00 GMT 2008

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

Open source-"supported" CVS backup capabilities are very weak.  Simple
solutions require potentially high-bandwidth brute force techniques.

For personal purposes, I've recently investigated CVSUP, CSUP, CVSYNC
and DCVS.

CVSUP seems to be the reigning king.  However, it is neither available
for RHEL5 nor Windows nor Solaris (SPARC) 10.  It is supported on
BSD.  So this is an RHEL4/BSD solution only.  I used CVSUP
successfully for a couple of years on RHEL3 and Solaris 8.  This
successful "experiment" ended in Dec. 2006 when I upgraded my SPARC
box to Solaris 10.  It will be buried when I (imminently) retire my
RHEL3 server, in favour of my RHEL5 server.

The simple CVS repository backup solution using RSYNC works fine on
LANs or low cost WANs.  However, a CVS TAG operation that affects a
large group of files will cause retransmission of entire RCS archive

The only widely-supported, multi-platform, open source, viable
solution for low-bandwidth repository backup is Subversion.

Over this Christmas break, my respect for CVS has been significantly
eroded.  The open source community has (in my opinion) clearly turned
its back on CVS.

Help me out.  I like CVS for binary files that change infrequently.  Who 
wants to give up double the disk space for a Subversion working copy with 
family photos and mp3 that rarely change?

However, if I want to keep my CVS repository backed up automatically, 
there seems to be no solution.

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook