Hi Nick

Thanks a lot. That's clear to me.

Best regards
Paul

On Wed, 3 Jan 2024 at 21:29, Nick Vatamaniuc <[email protected]> wrote:

> Hi Paul,
>
> You can recreate your databases and then re-populate them from another
> source. As of CouchDB version 3.3.0, if a database is recreated it
> will reset the replication job id, so it will start a new replication
> job between the new recreated source and the target.
>
> > There are some duplicate database names in the two source systems and
> some
> different database systems.
>
> If source databases have duplicate names, but they are on different
> hosts (https://sdb.somehost1.net and https://sdb.somehost2.net)
> they'll end up as different replication job ids with different
> checkpoints. If they are on the same host but you set up different
> user ids for them (https://user1:[email protected] and
> https://user2:[email protected]) they'll also get different job
> ids and different checkpoints.
>
> Cheers,
> -Nick
>
>
> On Fri, Dec 29, 2023 at 9:59 AM Paul Milner <[email protected]> wrote:
> >
> > I have set up a clustered couchdb instance and I have initiated the
> > databases by replication from another source couch system.
> >
> > I now want to reset all those databases and populate them by replicating
> > databases from another different source system.
> >
> > There are some duplicate database names in the two source systems and
> some
> > different database systems.
> >
> > As checkpoints have been taken in the replication with the first source
> > system, I'm wondering how it will proceed.
> >
> > Can someone tell me what I should do so that I end up with the
> destination
> > system being a copy of the second source system please?
> >
> > If I delete all the databases in the destination system and start the
> > second replication, will all databases (even with duplicate names between
> > the 2 source systems) be fully created and populated.
> >
> > Replication from the first source system will be turned off.
> >
> > Thanks a lot for your help
> > Paul
>

Reply via email to