Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
*Location*: http://docs.couchbase.com/admin/admin/Tasks/xdcr-configure-replications.html
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.107 Safari/537.36
*Referrer*: http://docs.couchbase.com/admin/admin/Tasks/tasks-manage-xdcr.html
*Screen Resolution*: 1440 x 900
*Location*: http://docs.couchbase.com/admin/admin/Tasks/xdcr-configure-replications.html *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.107 Safari/537.36 *Referrer*: http://docs.couchbase.com/admin/admin/Tasks/tasks-manage-xdcr.html *Screen Resolution*: 1440 x 900
Description
There is a sentence on this page: "Ensure that all Couchbase Server versions and platforms match. For instance, if you want to replicate from a Linux-based cluster, you need to do so with another Linux-based cluster."
A customer was planning to migrate an on-premise Couchbase 2.2 cluster to another AWS Couchbase 3.0 cluster. In order to move data over network, they initially considered to use XDCR, but by seeing this explanation, they thought they can't do that.
Then, they decided to take backup and restore, plus some custom logics were needed to catch-up delta during this migration process.
Technically, if both cluster support the same XDCR protocol (currently we have two), the version of Couchbase Server and platform don't matter. Additionally, there are connectors which take advantages of this, such as Couchbase Server and Elasticsearch connector. XDCR can be used to replicate data even between different PRODUCTs.
XDCR can be used to migrate a cluster location as well as upgrading Couchbase version, and this feature is really powerful.