"Henderson, Michael D" <michael.d.henderson@lmco.com> writes:
> 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
> transaction?
This doesn't really answer your question directly, but here's a script
might help you put together a Berkeley-based backup process that uses
a standard full/incremental strategy instead of 'svnadmin dump'. I
keep hoping to get time to turn it into something user-friendly enough
to put in tools/ or contrib/, but haven't yet (volunteers welcome :-) ).
It's at:
http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=9244
Note that the 'svnadmin create --bdb-log-keep' is important. This
strategy only works if your repository *doesn't* do automatic removal
of bdb logfiles.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 15 18:48:20 2004