# Local gateway backup in EC2

**URL:** https://discuss.elastic.co/t/local-gateway-backup-in-ec2/9325
**Category:** Elasticsearch
**Created:** [October 11, 2012, 5:30pm UTC](https://discuss.elastic.co/t/local-gateway-backup-in-ec2/9325 "2012-10-11T17:30:23Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![igor](https://avatars.discourse-cdn.com/v4/letter/i/dec6dc/32.png) [@igor](https://discuss.elastic.co/u/igor)
#### Post date: [October 11, 2012, 5:30pm UTC](https://discuss.elastic.co/t/local-gateway-backup-in-ec2/9325/1 "2012-10-11T17:30:23Z")

</div>

I'm posting two separate messages on related subjects just to make each one focused and simpler to answer. ( Another one is about s3 gateway backup)

My questions are for the people who uses local gateway backup in EC2.

1. If I have a large cluster, lets say 20 nodes with multiple large indexes, 10-15 shards in each index, and 2 replicas, how do I decide which nodes I need to backup? I don't need to backup each and every node with 3 replicas and so many shards, do I ? It looks like a lot of wasted storage to me.

2. How do you deal with transient nature of nodes and their IP addresses in EC2 in restore? I guess, it's simple during backup, just backup a local node. But are there any issues with changing IPs with restore?

3. I understand, my backup will be a bunch of folders, one per original node. How do I restore a cluster from that? Do I create a new node per a backup folder and restore each of them manually?

---

<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, 3:09am UTC](https://discuss.elastic.co/t/local-gateway-backup-in-ec2/9325/2 "2017-07-06T03:09:16Z")

</div>


