XDCR on Couchbase 6.0.0

[jreagan]

I am working to migrate Couchbase from GCP to AWS. I have gotten the servers installed and running but i am having issues getting XDCR working. I have opened all ports between the two but its not working still.

Ive read this post and it seem this may be my situation as well but i dont seem to have the couchbase-cli on 6.0.0.

Xdcr not replications with public ips

From your description of the problem, I am assuming that you used the public ip address of the ec2 instance when you added the XDCR remote cluster. If you look in the goxdcr.log (for example, /opt/couchbase/var/lib/couchbase/logs/goxdcr.log on Linux) on the source cluster, you’ll probably see WARN and ERRO messages for GOXDCR.RemClusterSvc saying that target nodes are not accessible, and you’ll probably see the private ip’s listed (even though you used the public ip when you added the XDCR rem…

Is there a way to set this alt ip\public ip on comminuty version 6.0.0?

[hyunjuV]

Alternate address support was added in Couchbase Server version 6.5, so that feature will not be in 6.0.0.

[jreagan]

So what do i need to do to get XDCR working between two data centers?

[hyunjuV]

Maybe this will help you – https://www.couchbase.com/forums/t/changing-server-node-name/3160

The other option might be to install 6.5.0 on the target cluster and use alternate addresses – should be able to XDCR from 6.0.0 to 6.5.0 (these are old versions, so I don’t know if there are any known issues with that) – but your main concern there would be whether your applications would be compatible with 6.5.0.

[jreagan]

Thanks for you advice @hyunjuV. This made me think of using a Site-to-Site VPN between GCP and AWS to complete this migration using XDCR. Setting up the VPN gave the servers the internal connectivity they needed to replicate.