[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Best practice

From: <andy.glew_at_amd.com>
Date: 2004-04-20 00:10:34 CEST

> I've got a question - what is the best -
> one repository for all projects I develop
> or special repository for every project?
> It's interesting to hear pro and contras?
---+ Backups
Since you cannot safely rely on filesystem based
backups, you have to develop a backup methodology
for SVN on your own. E.g. a cron job that hotcopies
nightly, and then writes an ascii dump off the hotcopy.
If you have a single repository, you write this once
and only once.
If you have multiple repositories, you have to do this
for each repository. That may be a hassle, although
it also gives you the ability to customize the backup
Also, any sysadmin knows that you have to frequently
verify that you can actually restore from backup;
i.e. you have to test the backups. (Or else when you
really need the backup, it will be broken.)
One repository means that you only need to do
this once.
Related: the backup load can be pretty high. Multiple
repositories can run on different servers, and back up
in parallel.
Received on Tue Apr 20 00:11:33 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.