Eric Brown wrote:
> Hello-
>
> We're starting up software CM on my project, and are going with subversion.
> I've read where it doesn't play nice with an NFS. We're going to
have LOTS
> of data on here (our baseline is going to be about 30-40Gig). Would
like
> to have some sort of network access to the repository, and I'd like
to backup
> the repos after every commit. Thinking of using RAID or a SAN. Is
this possible?
If you use the BDB backend, then you can't store it on a volume that
doesn't have a really good locking implementation. BDB is sensitive
to not being able to lock things. This basically rules out storing
a BDB database on an NFS/SMB/whatever volume. It might work with your
SAN implementation. I've done some basic testing on an EMC setup
on win32 and BDB worked ok, but it was hardly exhaustive.
The good news is that if you use the FSFS backend, you don't have this
problem. You can stick your FSFS repository on pretty much anything,
share it to several places (i.e. NFS mount to multiple Apache servers)
and it'll keep working just fine. We have a "load balancing" kind of
setup at work that's going like this.
Backing up after each commit, given the size of your repository,
sounds like ideal for the use of "svnadmin dump --incremental -rN"
as a post-commit hook.
daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 7 00:53:05 2005