Techiio-author
Started by Morrison OakOct 31, 2021

Open
Kibana not using existing .kibana index

0 VIEWES 0 LIKES 0 DISLIKES SHARE
0 LIKES 0 DISLIKES 0 VIEWES SHARE

I've 2 aws ec2 times. One for elasticsearch (es) and one for kibana. I am seeking to backup all the data from es to aws s3 after which repair it while creating a new instance.

The way I'm doing it's far this:

1. Terminate kibana example

2. Backup ES data with curator

3. Terminate ES example

4. Startup new ES instance and repair records with curator

5. Startup new kibana instance

The trouble is that even though the recovery works (I will see the indices restored in es which include a .Kibana_1 index that has an alias to .Kibana), when kibana begins up it doesn't use the existing .Kibana_1 index but creates a new one (e.G.: .Kibana_2)

0 Replies

You must be Logged in to reply
Trending Technologies
15
Software40
DevOps48
Frontend Development24
Backend Development20
Server Administration17
Linux Administration26
Data Center24
Sentry24
Terraform23
Ansible83
Docker70
Penetration Testing16
Kubernetes21
NGINX20
JenkinsX17
Recommended Blogs
1
Techiio-logo

Techiio is on the journey to build an ocean of technical knowledge, scouring the emerging stars in process and proffering them to the corporate world.

Follow us on:

Subscribe to get latest updates

You can unsubscribe anytime from getting updates from us
Developed and maintained by Wikiance
Developed and maintained by Wikiance