A proposed Subversion vision and roadmap
Posted Apr 4, 2010 6:05 UTC (Sun) by emk
In reply to: A proposed Subversion vision and roadmap
Parent article: A proposed Subversion vision and roadmap
1. A central server is required as the one which is stored on fully
backed up storage. (yeah yeah, DVCS means there's a copy on everybody's
desktop. All in the same building. Real backups are off site)
I've managed offsite backups for both Subversion and git, for
repositories in the 320GB range. In my experience, reliable Subversion
backups require a script to hotcopy the entire repository, and a fresh
whole-repository backup using a full-fledged backup system. This tends
to cause minor headaches for incremental backup systems.
Git, in contrast, can do very fast incremental backups via cron and git
pull. Even better, it can trivially verify the integrity of a repository by
checking all the hash sums.
Now, there are drawbacks to using git for certain kinds of large
organizations. Git submodule support, for example, is pretty arcane and
requires a moderate level of git-fu. But from a backup perspective, I'd
rather use git than subversion any day of the week.
to post comments)