# Mysql vs Elasticsearch data replication? **URL:** \ **Category:** Elasticsearch\ **Created:** [July 22, 2015, 6:35am UTC](https://discuss.elastic.co/t/mysql-vs-elasticsearch-data-replication/26046 "2015-07-22T06:35:26Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![rabeetwaqar](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@rabeetwaqar](https://discuss.elastic.co/u/rabeetwaqar)\ **Post date:** [July 22, 2015, 6:35am UTC](https://discuss.elastic.co/t/mysql-vs-elasticsearch-data-replication/26046/1 "2015-07-22T06:35:26Z")
Since we have been using mysql, and the replication process of mysql database is very common and easy to perform. I am caught in this same issue with elasticsearch, performing CLUSTER REPLICATION, finding the best and appropriate way to do it. Although I have multiple nodes (node recovery), but in case of disaster recover i want a cluster backup in another data center, there by doing cluster replication, but I am not getting help from the elastic community on this. Can anyone suggest? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 23, 2015, 7:04am UTC](https://discuss.elastic.co/t/mysql-vs-elasticsearch-data-replication/26046/2 "2015-07-23T07:04:37Z")
> [@rabeetwaqar](#): > > but I am not getting help from the elastic community on this. This is a volunteer run forum, so we do our best to answer your questions when we have time away from our own jobs and lives 😄 Though I'm not sure why you don't think this has been answered, you did ask the same thing in [Cluster replication](https://discuss.elastic.co/t/cluster-replication/25288) and there are a number of response. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:59pm UTC](https://discuss.elastic.co/t/mysql-vs-elasticsearch-data-replication/26046/3 "2017-07-05T23:59:41Z")