Backup before ES operations

Issue

We are planning to add a dedicated worker for ElasticSearch
We are planning to update the configuration of ElasticSearch

Environment

Private SaaS Edition (PSE)

Resolution

The normal process to add a ES new worker is :

1 - Execute cluster elasticsearch-backup operation to backup all ES data

bees-pse prepare elasticsearch-backup
bees-pse apply

2 - Execute cluster worker-add operation with the new worker configuration

bees-pse prepare worker-add
# worker-add is staged - review worker-add.config and edit as needed
bees-pse apply

3 - Execute cluster worker-remove operation to remove the old worker

bees-pse prepare worker-remove
# worker-remove is staged - review worker-remove.config and edit as needed
bees-pse apply

4 - Execute cluster elasticsearch-restore operation to restore all ES data

bees-pse prepare elasticsearch-restore
bees-pse apply

The normal process to upgrade a ES configuration is :

1 - Execute cluster elasticsearch-backup operation to backup all ES data

bees-pse prepare elasticsearch-backup
bees-pse apply

2 - Execute cluster elasticsearch-update operation with the new worker configuration

bees-pse prepare elasticsearch-update
# elasticsearch-update is staged - review elasticsearch-update.config and edit as needed
bees-pse apply

3 - Execute cluster elasticsearch-restore operation to restore all ES data

bees-pse prepare elasticsearch-restore
bees-pse apply

If you do not do elasticsearch-backup operation you have some automatic old backup and you could use elasticsearch-restore operation to restore it, but you will have a gap in ES data.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.