RE: svnadmin hotcopy failing

I assume I would only execute step 3 in the event of a meltdown, correct?
Step 3 is not actually part of the backup process is it?

Thanks very much for the workaround!

Ryan

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Thursday, May 13, 2004 9:38 AM
To: Ryan Braswell
Cc: users@subversion.tigris.org
Subject: Re: svnadmin hotcopy failing

rbraswell@connected.com wrote:
> Hi,
> I am running SVN1.0.2 on RH9 with Apache 2.0.48
>
> [svn@svn reposdump]$ svnadmin hotcopy --clean-logs /home/svn/repos
> /reposdump/repos-5058-hotcopy
> svn: Can't copy '/home/svn/repos/db/strings' to
> '/reposdump/repos-5058-hotcopy/db/strings.tmp': File too large
>
> This is a very big problem. Any help is greatly appreciated.

While the developers argue about the best way to deal with APR's (lack
of) largefile support in certain scenarios, here's a workaround.

You can do the 'svnadmin hotcopy' manually in 3 steps. There's nothing
magical about this command; it's supposed to be just a convenience for
users. It's doing exactly these 3 things under the hood:

1. cp -R repos repos-backup
2. cp repos/db/log* repos-backup/db/
3. svnadmin recover repos-backup

You could even write a shell script to do this.

Various people are starting to get burned by the fact that APR's 'copy
file' API can't always copy a >2GB strings file, so perhaps we should
write up this workaround as a FAQ?
Received on Thu May 13 17:39:22 2004