# Recovery Strategy for Elastic **URL:** \ **Category:** Elasticsearch\ **Created:** [August 15, 2016, 3:41pm UTC](https://discuss.elastic.co/t/recovery-strategy-for-elastic/58036 "2016-08-15T15:41:59Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![newelasticuser](https://avatars.discourse-cdn.com/v4/letter/n/50afbb/32.png) [@newelasticuser](https://discuss.elastic.co/u/newelasticuser)\ **Post date:** [August 15, 2016, 3:41pm UTC](https://discuss.elastic.co/t/recovery-strategy-for-elastic/58036/1 "2016-08-15T15:41:59Z")
What is the recovery strategy for single data center built in VMware? Does Elastic support VMWare Site recovery Manager for any disaster or outage recovery? Currrently we have 3 node cluster on single data center(3 master/2 data nodes). Would like to know the best options for recovery/outage: 1. Do we need to have two data centers built ? 2. Incremental SNAPSHOT recovery is the way to go? 3. VMware Site recovery Manager ? ---
**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\ **Post date:** [August 15, 2016, 4:01pm UTC](https://discuss.elastic.co/t/recovery-strategy-for-elastic/58036/2 "2016-08-15T16:01:08Z")
I cannot comment on using VMWare Site recovery Manager since I don't know it. Regarding your other questions: - Snapshot/Restore might be enough if you can live with a little bit of downtime and have a read-only application or have a way to buffer documents that are written while the datacenter is out. How much time snapshot/restore needs depends on the size of your data you need to restore - ES currently doesn't support cluster replication between two datacenters. If you want to minimize downtime in case one cluster dies you can provide a second identical cluster in another datacenter you can switch to. However we currently don't provide a way of keeping those two clusters in sync, that needs to be adressed in your own application ---
**Author:** ![newelasticuser](https://avatars.discourse-cdn.com/v4/letter/n/50afbb/32.png) [@newelasticuser](https://discuss.elastic.co/u/newelasticuser)\ **Post date:** [August 22, 2016, 6:26pm UTC](https://discuss.elastic.co/t/recovery-strategy-for-elastic/58036/3 "2016-08-22T18:26:11Z")
We are currently loading realtime data into the index every 15 mins. What Snapshot strategy should be followed so we don't lose the data, if there is network failure and if we have to restore it from SNAPSHOT. Do we have to run the SNAPSHOT as well every 15 mins? ---
**Author:** ![Phani\_Nadiminti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phani_nadiminti/32/45381_2.png) [@Phani\_Nadiminti](https://discuss.elastic.co/u/Phani_Nadiminti)\ **Post date:** [August 23, 2016, 1:51pm UTC](https://discuss.elastic.co/t/recovery-strategy-for-elastic/58036/4 "2016-08-23T13:51:01Z")
HI, as christoph suggested we need to have other data center would be good idea !! where you can restore your snapshots to that new data center based on your requirement , we can take snapshot like you specified and restore to another DC perform scheduling operation for restroing snapshots to new DC. Thanks phani ---
**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, 10:25pm UTC](https://discuss.elastic.co/t/recovery-strategy-for-elastic/58036/5 "2017-07-05T22:25:53Z")