# Disaster recovery is supported by elastic operator **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [September 17, 2020, 9:41am UTC](https://discuss.elastic.co/t/disaster-recovery-is-supported-by-elastic-operator/248950 "2020-09-17T09:41:31Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![knagasri](https://avatars.discourse-cdn.com/v4/letter/k/47e85d/32.png) [@knagasri](https://discuss.elastic.co/u/knagasri)\ **Post date:** [September 17, 2020, 9:41am UTC](https://discuss.elastic.co/t/disaster-recovery-is-supported-by-elastic-operator/248950/1 "2020-09-17T09:41:31Z")
Did elastic operator :1.2.1 supports disaster recovery. If supports how to achieve it. ---
**Author:** ![dkow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dkow/32/47340_2.png) [@dkow](https://discuss.elastic.co/u/dkow)\ **Post date:** [September 21, 2020, 9:39am UTC](https://discuss.elastic.co/t/disaster-recovery-is-supported-by-elastic-operator/248950/2 "2020-09-21T09:39:54Z")
Hi @knagasri, thanks for your question. Can you expand about which disaster recovery context you are asking about? For ECK failures itself, ECK Pod will be restarted or rescheduled by Kubernetes. The operator is stateless and it's able to retrieve all information necessary to resume from Kubernetes APIs. To improve this even further, we are enabling leader election mechanism. See the [pull request](https://github.com/elastic/cloud-on-k8s/pull/3632) for more details. For failures of Elasticsearch deployed with ECK, it's no different than without ECK in the picture. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 19, 2020, 9:40am UTC](https://discuss.elastic.co/t/disaster-recovery-is-supported-by-elastic-operator/248950/3 "2020-10-19T09:40:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.