Store snapshots of a deployment in a dedicated repository
editStore snapshots of a deployment in a dedicated repository
editAzure deployments of your organization in the same region currently may use the same Azure Blob storage container as shared repository to store their snapshots. To make sure that no other deployment can have access to this deployment’s snapshots, you can instead use a dedicated repository for this deployment.
This configuration is automatic for all newly created deployments, but must be triggered manually on any existing Azure deployments you have. If a deployment can be moved to a dedicated repository, a notification will show up in the deployments menu under Elasticsearch > Snapshots.
When enabling a dedicated repository for storing snapshots, a configuration change triggers for your deployment and:
-
Renames the existing
found-snapshotsrepository to\_clone_<clusterid>. In this repository, all existing snapshots and searchable snapshots can still be accessed. -
Adds a new (empty)
found-snapshotsrepository using a new container. -
Takes a full snapshot in this new
found-snapshotsrepository.
Restoring from a snapshot created before the migration
editThe snapshots are still available and can be restored just like snapshots in found-snapshots. You can find more information in Snapshot and restore.
Removing the old repository
editIf you no longer need the old snapshots, you can remove the repository. By doing this, you also prevent accessing snapshots of other deployments from this deployment:
- From your deployment menu, go to Elasticsearch > Snapshots.
- On the Snapshots page, Snapshot repositories of other deployments shows the old repository.
- With Remove Access, the snapshot repository will be removed.
If the repository is still in use (for example by mounted searchable snapshots), it can’t be removed. Please first remove any indices stored in this repository.
