# Cluster replication

**URL:** <https://discuss.elastic.co/t/cluster-replication/25288>\
**Category:** Elasticsearch\
**Created:** [July 10, 2015, 7:00am UTC](https://discuss.elastic.co/t/cluster-replication/25288 "2015-07-10T07:00:18Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![rabeetwaqar](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@rabeetwaqar](https://discuss.elastic.co/u/rabeetwaqar)\
**Post date:** [July 10, 2015, 7:00am UTC](https://discuss.elastic.co/t/cluster-replication/25288/1 "2015-07-10T07:00:18Z")

</div>

Hi,  
Is it possible to create the replica of whole cluster?  
Thanks

---

<div class="post-metadata">

**Author:** ![Joshua\_Rich](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshua_rich/32/44953_2.png) [@Joshua\_Rich](https://discuss.elastic.co/u/Joshua_Rich)\
**Post date:** [July 10, 2015, 7:02am UTC](https://discuss.elastic.co/t/cluster-replication/25288/2 "2015-07-10T07:02:50Z")

</div>

Hi @rabeetwaqar,

Can you describe what you are trying to solve by replicating your entire cluster? DR? Backups?

---

<div class="post-metadata">

**Author:** ![rabeetwaqar](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@rabeetwaqar](https://discuss.elastic.co/u/rabeetwaqar)\
**Post date:** [July 10, 2015, 7:05am UTC](https://discuss.elastic.co/t/cluster-replication/25288/3 "2015-07-10T07:05:33Z")

</div>

Yes backups. For any reason if my hardware fails i should have a backup of my whole cluster. Is it possible to create?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 10, 2015, 7:13am UTC](https://discuss.elastic.co/t/cluster-replication/25288/4 "2015-07-10T07:13:03Z")

</div>

What kind of hardware failure do you want to protect against? With a multi-node cluster with shard replicas you're pretty resilient to begin with.

Also, see this recent topic:

> [@What is the best backup strategy for ELK stack?](https://discuss.elastic.co/t/what-is-the-best-backup-strategy-for-elk-stack/25146):
>
> Hi Experts , Before moving things to the production I want to collect thoughts on ELK stack backup . Can you recommend or suggest some criteria's or methods best for backup . I have a question one way which comes to my mind is directly take directory backup and store it on tape or HD, but how I can take incremental backup with this approach ? Thanks Vikas

---

<div class="post-metadata">

**Author:** ![rabeetwaqar](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@rabeetwaqar](https://discuss.elastic.co/u/rabeetwaqar)\
**Post date:** [July 10, 2015, 7:26am UTC](https://discuss.elastic.co/t/cluster-replication/25288/5 "2015-07-10T07:26:04Z")

</div>

Thanks magnus for quick response  
Sure i will look into it.

---

<div class="post-metadata">

**Author:** ![rabeetwaqar](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@rabeetwaqar](https://discuss.elastic.co/u/rabeetwaqar)\
**Post date:** [July 10, 2015, 11:45am UTC](https://discuss.elastic.co/t/cluster-replication/25288/6 "2015-07-10T11:45:42Z")

</div>

Hello @magnusbaeck ,

I have created a repository and successfully managed to create a snapshot of my index but if we run a Cron job lets assume :

- Server A(SA)
- Server B(SB)

My cluster is created on SA and i replicate/backup it using snapshot to SB.

My question is if my cluster has more than 50,0000 data and i replicate it after every 2 minutes , the SB will not be able to manage it or bandwidth will be consumed or it will eventually get slow.  
What if my SA gets down , then the domain will be automatically changed but the data with in SB cluster must be the same as SA cluster was containing before crash.

1- Can we replicate SA cluster difference to SB. Note : Only the differences i.e indexes and shards maybe.  
2- And if yes what would be the exact procedure to do this?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 10, 2015, 11:52am UTC](https://discuss.elastic.co/t/cluster-replication/25288/7 "2015-07-10T11:52:10Z")

</div>

The snapshot/restore mechanism won't work well for real-time failover situations. But why not just have your two hosts join the same cluster? With one replica of each index it's okay if one node drops out.

---

<div class="post-metadata">

**Author:** ![rabeetwaqar](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@rabeetwaqar](https://discuss.elastic.co/u/rabeetwaqar)\
**Post date:** [July 10, 2015, 12:18pm UTC](https://discuss.elastic.co/t/cluster-replication/25288/8 "2015-07-10T12:18:08Z")

</div>

> [@magnusbaeck](#):
>
> The snapshot/restore mechanism won't work well for real-time failover situations. But why not just have your two hosts join the same cluster? With one replica of each index it's okay if one node drops out.

What if the server gets down which is containing the cluster? Then both dependencies will get down.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 10, 2015, 12:22pm UTC](https://discuss.elastic.co/t/cluster-replication/25288/9 "2015-07-10T12:22:26Z")

</div>

What do you mean? The whole point of an ES cluster is that no single node contains all state and that (given sufficient index replicas) any machine can drop out of the cluster without affecting its operations.

---

<div class="post-metadata">

**Author:** ![rabeetwaqar](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@rabeetwaqar](https://discuss.elastic.co/u/rabeetwaqar)\
**Post date:** [July 14, 2015, 6:53am UTC](https://discuss.elastic.co/t/cluster-replication/25288/10 "2015-07-14T06:53:00Z")

</div>

Hi,

How can i join two elasticsearch instances running on different servers to a single host?  
Should i update my .yml files?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 14, 2015, 7:05am UTC](https://discuss.elastic.co/t/cluster-replication/25288/11 "2015-07-14T07:05:15Z")

</div>

Do you have a two-node cluster that you want to turn into a one-node cluster? Or two separate clusters where you want to migrate all data from one to the other?

---

<div class="post-metadata">

**Author:** ![rabeetwaqar](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@rabeetwaqar](https://discuss.elastic.co/u/rabeetwaqar)\
**Post date:** [July 14, 2015, 7:10am UTC](https://discuss.elastic.co/t/cluster-replication/25288/12 "2015-07-14T07:10:33Z")

</div>

Thanks for prompt reply,

Yes the second case i'm looking for. I want to replicate cluster data running on different servers.

What steps should i follow?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 14, 2015, 7:17am UTC](https://discuss.elastic.co/t/cluster-replication/25288/13 "2015-07-14T07:17:09Z")

</div>

If it's a one time thing look into the snapshot/restore mechanism that you've already explored. If you're talking about continuous replication then we're discussing in circles and I'll refer you to what I've said previously in this thread.

---

<div class="post-metadata">

**Author:** ![rabeetwaqar](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@rabeetwaqar](https://discuss.elastic.co/u/rabeetwaqar)\
**Post date:** [July 14, 2015, 7:21am UTC](https://discuss.elastic.co/t/cluster-replication/25288/14 "2015-07-14T07:21:07Z")

</div>

Yes i'm looking for continuous replication.  
Okay thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 12:01am UTC](https://discuss.elastic.co/t/cluster-replication/25288/15 "2017-07-06T00:01:37Z")

</div>


