# Disaster Recovery - Non-Enterprise version **URL:** \ **Category:** Elasticsearch\ **Created:** [January 10, 2022, 2:08pm UTC](https://discuss.elastic.co/t/disaster-recovery-non-enterprise-version/293897 "2022-01-10T14:08:38Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![rajeev.j.khanna](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@rajeev.j.khanna](https://discuss.elastic.co/u/rajeev.j.khanna)\ **Post date:** [January 10, 2022, 2:08pm UTC](https://discuss.elastic.co/t/disaster-recovery-non-enterprise-version/293897/1 "2022-01-10T14:08:38Z")
Hi Team, We are using the open-source version of ELK. We want to implement a Disaster Recovery (DR) solution for our application. That means ELK LOGS has to be replicated. How can we do this? (Please do not share the paid licensed solution. I am looking for an open-source solution.) ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 10, 2022, 2:50pm UTC](https://discuss.elastic.co/t/disaster-recovery-non-enterprise-version/293897/2 "2022-01-10T14:50:06Z")
Welcome! You can snapshot your data somewhere and restore in the disaster recovery cluster every 30 minutes for example. Or if you want something more "real-time", without using the Cross Cluster Replication feature, you can send your documents to both clusters at the same time. Or may be safer, use a message broker like Kafka and read the queue from both clusters... ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 7, 2022, 2:50pm UTC](https://discuss.elastic.co/t/disaster-recovery-non-enterprise-version/293897/3 "2022-02-07T14:50:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.