Hi Ryan,
Thanks for the response.
As far as I know svnsync can be used only on Subversion with the
version 1.4or newer.
But the version we are using is 1.3.2 only.
And we are trying to create a fail over repository which we can directly use
in case of any damage to the machine on which our repository is
hosted.Andit seems svnsync would only provide us "read-only"
repository, which we
don't want.
I need your suggestion over here.
Thanks,
Karthik.
On 9/6/07, Ryan Schmidt <subversion-2007b@ryandesign.com> wrote:
>
> On Sep 6, 2007, at 04:47, p karthik wrote:
>
> > We are in the process of replicating a Subversion repository on a
> > Sun Solaris Unix box.
> > The steps which we are following for this are:
> >
> > 1. Dump the delta revisons every one hour from the original
> > repository.
> > 2. Zip up those revisions and send it to other unix box.
> > 3. Get the zip file; unzip it and then load the dumped revisions in
> > to the replicated repository.
> >
> > Most of the times it works fine.
> > But at times, the last revision is not commited.
> >
> > The load log looks like this:
> >
> > <<< Started new transaction, based on original revision 24643
> >
> > * adding path : <path>
> >
> > * adding path : <path>
> >
> > * editing path : <path>
> >
> > * editing path : <path>
> >
> > ------- Committed revision 24643 >>>
> >
> > <<< Started new transaction, based on original revision 24644
> >
> > * editing path : <path>
> >
> > done.
> >
> > <At this point it is supposed to say that -----Committed revision
> > 24644, but it is not saying that way.>
> >
> > *** 06/09/2007.08:00:20 *** Deleting Sync File 24642_24644
> >
> > To confirm that I have looked the youngest revision in the
> > repository too. It is obviously saying that the youngest is 24643.
> >
> > Please let me know is it some thing wrong with what I am doing or
> > is it some thing to do with the svnadmin load binary.
>
> Is there a reason you're not using svnsync? Wouldn't that be simpler?
>
>
>
Received on Fri Sep 7 12:48:50 2007