title: best practice for backing up cvs repository?
body: <p>Some of our projects are still on cvs. We currently use tar to backup the repository nightly. </p>
  
  <p>Here's the question:
  best practice for backing up a cvs repository?</p>
  
  <p>Context: We're combining a several servers across the country onto one central server. The combined repsitory size is 14gb.  (yes this is high,  most likely due to lots of binary files, many branches,  and the age of the repositories). </p>
  
  <p>A 'straight tar'  of the cvs repository yields ~5gb .tar.gz file.  Restoring files from 5gb tar files will be unwieldy. Plus we fill up tapes quickly.</p>
  
  <p>How well does  a full-and-incremental backup approach, i.e. weekly full backup, nightly incremental backups? What open source tools solve this problem well? (e.g. Amanda, Bacula).</p>
  
  <p>thanks,</p>
  
  <p>bill</p>