By using AWS re:Post, you agree to the Terms of Use

Disaster Recovery in Elasticseach

0

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.

Thanks in advance.

2 Answers
0

Hi,

If you still keep the source data somewhere then you can re-index the data to the new cluster.

For snapshot, note that the Amazon OpenSearch Service takes hourly automated snapshots and stores them in a preconfigured Amazon S3 bucket at no additional charge. To use this automated snapshots for disaster recovery you could raising a support ticket.

On the other hand, manual snapshot gives you more control so you can migrate data to a different domain by yourself. You could trigger Lambda function to create manual snapshot on a regular basis, but you may need to raise a support ticket to disable the hourly automated snapshot to avoid potential conflict as you can’t take a snapshot if one is currently in progress.

SUPPORT ENGINEER
answered 7 months ago
  • Jiaheng Thanks for your reply. But setting cross cluster replication won't be more cleaner and also the possibility of losing data would be less? What is the best approach that is being recommended for disaster recovery for Elasticsearch?

  • Hi,

    It will depend on your use cases and the architecture of the whole system. For example, if your applications can easily switch to a new OpenSearch cluster (assuming it is in a different region) and the latency is acceptable, then cross cluster is better as the downtime is less comparing to recovering from snapshot. In this case, you could also consider migrating the OpenSearch domain from N. California region to a region has 3 AZs so you don't need to worry about the one AZ down scenario.

0

Have you taken a look at this?

GitHub: aws-samples/aws-cross-region-elasticsearch-backup-restore

This project creates a State machine that does daily automated Backup Restore of OpenSearch indices from one domain to another in same or different region

profile picture
answered 7 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions