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

Question on db backup strategy

From: Henderson, Michael D <michael.d.henderson_at_lmco.com>
Date: 2004-04-14 05:39:18 CEST

I'm doing a pilot implementation for our project. When I can demonstrate
that Subversion works, well be able to dump VSS for most of our users. I
was estimating the disk & tape resources that we'd need. It's not a
large setup, initially 13 separate project directories, 4,700 files, 140
megs total, so the initial repository won't be that large. But, I was
reading chapter 5 (draft 9189 of the book) and am confused on the last
paragraph in Repository Backup. It states that the Subversion team backs
up the Subversion repository after every revision.

It's late, and I'm new to this, so I have to ask if revision == commit?
The usage has been pretty consistent, so I'm supposing so. Does that
really hurt performance of the server? Is the size of the backup
approximately the same size as the repository? Or, am I completely
reading that wrong, and they're just backing up the newly commited


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 14 05:39:49 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.