I do daily snapshot to S3 using the date format to make them unique
The backup has been running fine for the last 3 months it started failing for the past 2 weeks
I think I may have find the problem (will be able to tell for sure in couple of days). We have lots of indices and my script backup them up at the end of the day after they have rollover. These 3 indices that are failing are the only indices that do not rollover, documents get added to them day by day. I have a policy on my S3 backup to move indices from S3 to IA (Infrequent Access) and to Glacier after 60 days.
It seems like those indices were moved to Glacier.
I am in the process of restoring them to S3 and run the snapshot again.
Will keep you posted.
Thanks
Sorry to post question in your thread.
I have a doubt about this topic. If we create snapshots of elasticsearch cluster or node and store it in aws s3, how we can view the logs in kibana?
I mean for viewing logs in kibana, do we need to restore the snapshots back to elasticsearch.
I setup logserver in AWS EC2 and created a S3 bucket. Next I need to bind S3 with Elasticsearch ,but no idea of where to start.
Kibana reads what is indexed into elasticsearch.
So yes, you have to restore your data in elasticsearch if you want to be able to consume them into Kibana.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.