On Mon, Apr 19, 2010 at 11:46 AM, J. Norment <jnorment_at_q2software.com>wrote:
> Rob van Oostrum wrote:
>
> On Fri, Apr 16, 2010 at 2:21 PM, J. Norment <jnorment_at_q2software.com<mailto:
>> jnorment_at_q2software.com>> wrote:
>>
>>
>> Is anyone seeing this message that has any ideas how to fix this? (
>> This message is a repeat. ) It's now been about 3 weeks since
>> the last replication / backup.
>> The repo is large enough that doing a hot-backup on the production
>> server causes delays in day-to-day business.
>> ( This is one of the problems that I'm trying to solve. )
>>
>> But-- along the way to figuring out how to filter out specific
>> paths, I discovered that the repo wasn't replicating.
>> I need to get this operational again so that I can get backups
>> flowing again. ... even if it means sacrificing specific revisions.
>>
>> Here are the specifics:
>>
>>
>>
>> I had a replication repo start failing a few weeks ago with the
>> message:
>> syncing: "svnsync: Delta source ended unexpectedly"
>>
>> Ultimately, I ended up unintentionally removing the files for the
>> replication repo.
>>
>> So now I'm creating a new one.
>>
>>
>> The source repo is located on a server running svn, version 1.4.5
>> (r25188)
>>
>> .. which is being replicated to a new repo on a server running
>> svn, version 1.5.6 (r36142)
>>
>> ( I started replicating at revision 0. )
>>
>> I'm now getting:
>> svnsync: Path 'QA/Releases/Q2 2.6.3/Q2 Adaptors
>> 2.6.3.1617/ProgramBins/Sample/QuorumChangeOfAddress' not present
>>
>>
>> How is this possible, if nothing is being filtered from the repo,
>> and nothing can ever be deleted from an SVN repo?
>>
>> More to the point, how can this be fixed?
>>
>>
>> How exactly would hotcopy cause delays that would be prohibitive for your
>> day-to-day operation? Isn't the whole point of it to not do this?
>>
>> Have you run 'svnadmin verify' to make sure your source repository is
>> healthy and not corrupted somehow/somewhere?
>>
>> In my experience, seeding a mirror of a LARGE master repository using
>> svnsync is not the fastest way to get there at all. I would go the hotcopy
>> route and setup svnsync after the fact to start to bring over deltas. Should
>> be much, much faster that way.
>>
>>
>> -rob
>>
>
> I can't tell you how exactly. I can tell you that I was having users
> complain about error messages before I moved the backup process to a
> replicated repo.
>
> No, I haven't run svnadmin verify. I'll give that a shot today.
>
> It might help me figure out how to fix whatever is causing it not to
> replicate properly.
>
> Have you ever needed to split a repo? I'm going to need to do that once I
> can get a backup. It seems that you've worked with large repos, so maybe
> you've needed to do this.
>
>
>
>
Not exceptionally large, but in the ~10GB range, sure. Yes, I've had to
split a few. Straight forward svnadmin dump > svndumpfilter3 > svnadmin load
procedure for the most part.
Received on 2010-04-19 23:34:20 CEST