[Bucardo-general] Replicate different Database on the same server using Bucardo

[akp geek]

Exactly,  the Sync is dieing because of the mismatch between the 2
databases. Now I remember, I have 2 syncs defined, one for push delta and
the other for fullcopy. DDL changes happend in tables related to both syncs
, as a result the whole replication process got effected.

Updates to the log file has been stopped at that time. that's when I thought
the replication process has been stopped with out me stopping bucardo_ctl

What I did was, I have fixed the DDL changes and re started bucardo_ctl with
onetimecopy=1 and tables being trunncated.

I will again need to the same setup , where DDL changes happen and see what
happens

Appreciate your help and followup

Regards

On Tue, Feb 23, 2010 at 12:28 PM, Joshua Tolley <josh at endpoint.com> wrote:

> I'm not sure bucardo_ctl would abort -- my first guess would be that only
> the
> sync handling that database would abort. I recommend you Try It And See, if
> you have time and resources to set up a simple test.
>
> --
> Josh Tolley  josh at endpoint.com  801-987-0252
> End Point Corporation
> http://www.endpoint.com
>
>  On Tue, Feb 23, 2010 at 10:46:37AM -0500, akp geek wrote:
> >    Thanks Joshua. I would like to follow the same concept as you
> mentioned
> >    which would be a very clean approach. However the problem that I might
> run
> >    into is , if there is any DDL change happens on Test , then chances
> are
> >    that the bucardo_ctl process would abort and it happend for us.
> >
> >    In that case the replication process for the other database where no
> >    changes have been made is also being effected.
> >
> >    That was root cause for posting  my question.  Appreciate your
> thoughts on
> >    the question
> >
> >    Regards
> >
> >
> >
> >    On Tue, Feb 23, 2010 at 10:25 AM, Joshua Tolley <josh at endpoint.com>
> wrote:
> >
> >      On Tue, Feb 23, 2010 at 09:24:30AM -0500, akp geek wrote:
> >      >      You'll also, of course, need the bucardo schema in each
> database
> >      >      you're replicating, and to specify distinct pidfile
> directories
> >      (and
> >      >      probably also distinct log file locations, too -- unless you
> want
> >      half
> >      >      your log traffic to be noise relative to what you're looking
> for
> >      at
> >      >      any one time) for each MCP you have running.  I'm having
> trouble
> >      >      remembering how to specify different log files offhand,
> though.
> >       Greg?
> >      >       Joshua?  Beuller?
> >
> >      I'd install bucardo twice, in two different directories, to make
> sure
> >      things
> >      stayed separate.
> >      >      All that said, I don't think you strictly need separate MCPs
> >      running
> >      >      to replicate multiple databases.  You should be able to
> >      coordinate all
> >      >      that with separate entries in the bucardo.db table, and
> distinct
> >      goats
> >      >      and herds appropriately associated with them.
> >      >
> >      >      What's the recommended practice for this kind of scenario?
> >
> >      Here's the key, I'd say. You don't need multiple instances of
> Bucardo
> >      just to
> >      replicate two separate databases. Simply add the new source and
> >      destination
> >      databases to your existing bucardo setup (e.g. bucardo_ctl add db
> ...),
> >      add
> >      the objects you want to replicate, and add another sync.
> >      --
> >      Josh Tolley  josh at endpoint.com  801-987-0252
> >      End Point Corporation
> >      http://www.endpoint.com
> >      -----BEGIN PGP SIGNATURE-----
> >      Version: GnuPG v1.4.9 (GNU/Linux)
> >
> >      iEYEARECAAYFAkuD81oACgkQRiRfCGf1UMNiAACgoizQ/nyCMGa6XkTuoJC9y4wp
> >      fagAnjpkjhLjMXfb1+k6mmTkfYOGePrd
> >      =lI6d
> >      -----END PGP SIGNATURE-----
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkuEEDkACgkQRiRfCGf1UMPbKQCcCDaH19rIxyAxIe8RuwtNA9v+
> sdEAn0ALj1q8e438UuzX98W6vZY7mO/b
> =MOvy
> -----END PGP SIGNATURE-----
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20100223/afb2830d/attachment-0001.html