on second thought, i've given up on the coda backup system. no offense
to the smart people who make coda a great system to use, but the backup
system is too fragile to be trusted for production applications. nothing
worries me more than the possibility of "write-only" backups.

after a couple of years of success using rdiff-backup for source code
and general system backups, i just started using it for my coda
backups. rdiff-backup reads from the mounted coda filesystem and
writes the backup to cheap disk. it maintains a live mirror with diffs
going back as far as you want. it's an excellent tool.

http://rdiff-backup.stanford.edu/

you can run the backup using only one line of code, with no configuration
required. just run venus on your backup host.

rdiff-backup /coda/db.domain.com/ /home/backup/mirror

On 07/06/04, Steve Simitzis <steve_at_saturn5.com> wrote: 

> On 07/06/04, Steve Simitzis <steve_at_saturn5.com> wrote: 
> 
> > running volutil dump by hand seems to work okay, though.
> 
> actually.
> 
> the filesize of the backup doesn't get any larger than 4295301252 (4GB
> exactly) when running volutil dump, even though it will continue to
> transfer data (as evidenced by the display of "...........").
> 
> -- 
> 
> steve simitzis : /sim' - i - jees/
>           pala : saturn5 productions
>  www.steve.org : 415.282.9979
>   hath the daemon spawn no fire?
> 

-- 

steve simitzis : /sim' - i - jees/
          pala : saturn5 productions
 www.steve.org : 415.282.9979
  hath the daemon spawn no fire?