Snapshot with the same name already exists – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.4

Briefly, this error occurs when you try to create a new snapshot in Elasticsearch with a name that already exists in the repository. Elasticsearch doesn’t allow duplicate snapshot names within the same repository. To resolve this issue, you can either delete the existing snapshot before creating a new one with the same name, or simply use a different, unique name for the new snapshot. It’s also a good practice to implement a naming convention for snapshots to avoid such conflicts.

This guide will help you check for common problems that cause the log ” snapshot with the same name already exists ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot, repositories, blobstore.

Log Context

Log “snapshot with the same name already exists” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 try {
 final String snapshotName = snapshotId.getName();
 // check if the snapshot name already exists in the repository
 final RepositoryData repositoryData = getRepositoryData();
 if (repositoryData.getSnapshotIds().stream().anyMatch(s -> s.getName().equals(snapshotName))) {
 throw new InvalidSnapshotNameException(; snapshotId.getName(); "snapshot with the same name already exists");
 }  // Write Global MetaData
 globalMetaDataFormat.write(clusterMetaData; blobContainer(); snapshotId.getUUID());


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?