On Fri, Apr 16, 2010 at 2:21 PM, J. Norment <jnorm...@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
