Note: Aiven for OpenSearch replaces Aiven for Elasticsearch after Elasticsearch version 7.10.2 due to licensing changes. In addition, OpenSearch Dashboards replaces Kibana. Starting from September 24th, 2021 until March 23rd, 2022, Aiven supports services running both OpenSearch and Elasticsearch 7.10.2. For more information on Aiven for OpenSearch, see our developer documentation.
Aiven for Elasticsearch databases are automatically backed up, encrypted, and stored securely in object storage.
Depending on the service plan, we offer single backups for disaster recovery or daily backups with different retention periods:
Hobbyist plans: single backup for disaster recovery
Startup plans: daily backups with a 2-day retention period
Business plans: daily backups with a 14-day retention period
Premium plans: daily backups with a 30-day retention period
How the backup functionality works
To allow returning to an earlier point in time, Aiven for Elasticsearch uses two kinds of backups - hourly and daily. Each type has its own backup frequency interval and retention period. Currently, you cannot configure these settings.
Aiven for Elasticsearch uses the database forking functionality to create a new Elasticsearch service that is cloned from the backup that you select. Depending on your service plan, you can restore backups from a specific day or hour.
Note: Currently, Aiven for Elasticsearch only supports restoring from daily backups or hourly backups from the previous day.
To restore a backup:
Log in to the Aiven web console and select your Elasticsearch service.
Click the Backups tab.
This opens the New Database Fork view where you can create the fork for the backup that you want to restore.
Fill in the required details, select the cloud provider, region, and service plan, then click Create fork.
Once the new service is running, change your application's connection settings to point to it.