Disaster Recovery in Elasticseach

Question

Hi Everyone,

Last year, We moved one of our main reporting systems to Elasticseach 7.9 , its located in N. California region. In this region only 2 AZ is available, in our domain we have dedicated 3 master nodes. Now we are looking for some disaster recovery options.

I read https://docs.aws.amazon.com/opensearch-service/latest/developerguide/disaster-recovery-resiliency.html, and it looks with our current setup we have 50/50 downtime possibility.

so far I came up with two options 1- cross cluster replication(which will double our cost) 2- continuous snapshot backup.

Below are my questions 1- Is there any other possible option for disaster recovery that I haven't considered? 2- For snapshot backup, is there an easy way to schedule/manage the backups, so we can bring up the domin in shortest period of time and with less data loss.

Answer

Hi there, please find the answers inline

(1) Is there any other possible option for disaster recovery that I haven't considered?

Currently those are the best options available for disaster recovery i.e
1)  Cross cluster replication
2) Snapshot backup
3) Multi-AZ domains and replica shards 
4) Configuring a multi-AZ domain in Amazon OpenSearch Service.

(2) For snapshot backup, is there an easy way to schedule/manage the backups, so we can bring up the domin in shortest period of time and with less data loss.

Yes you can automate taking manual snapshots using ISM  (i) (ii), so that latest can be restored manually in to the new cluster.

Hope this helps!

References:

(i) https://opendistro.github.io/for-elasticsearch-docs/docs/im/ism/policies/#snapshot
(ii) https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html#managedomains-snapshot-ism

Disaster Recovery in Elasticseach

Relevant content