possible large repository problems...

I've been running svn on a Debian (woody) system for a few months now.
I'm still using the 1.0.0 packages that Colin Watson released, since I
didn't want to risk destabilizing our production environment with any
non-essential upgrades. Which brings me to my first question:

1. Are there any critical fixes in 1.0.5? (Security is not a big
concern, this is for intranet use).

Also, we recently hit the 2GB strings-file limit, which breaks the
hotcopy functionality (as per #1819). From what I can see in the list
archives, the workaround are:

a) svnadmin dump (really slow)
b) lock out all of your users, cross your fingers, and copy the
repository manually.

Which raises my second question:

2. What is the best (current) practice for backing up large repositories?

And finally, a related question to the above:

3. Does the 2GB file limit affect any other areas of svn?

I ask because clients have suddenly started timing out on one of our
(large) repositories, using http:// or file://. Maybe it's something
else, but I thought I'd check before I start worrying about drive
failures and such.

Wisdom of the list will be much appreciated. :-)

Cheers,

-- 
Neil Gower
Brainbox Games
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org