Am testing on a lab cluster
Repository name = "Snapshots"
Immediately after creating the snapshots, listing the snapshots returned
the snapshots and the indices they contained.
Now, am attempting to restore the snapshots to an empty cluster.
The new cluster looks good from the following:
curl -XGET localhost:9200/_cluster/health
From the master node on this new cluster, ran the following to list all
snapshots eligible to be restored. The node that's named is the local
node. Have verified the node has full access to the shared file system and
access to the snapshot repository.
curl -XGET localhost:9200/_snapshot/Snapshots/_all
nested: RepositoryMissingException[[Snapshots] missing]; ","status":404}
Am trying to think of reasons why ELASTICSEARCH-1 can't find the snapshot
repository. Maybe no other node can "find" the repository also, but the
command stops at this first node's failure.
Does the repository need to be registered using the steps to initialize an
empty repository before creating snapshots? If so, I assume the existing
repository data won't be wiped out (maybe the data should be moved,
repository created and then data moved back to the new registered
Maybe Snapshot/Restore has not actually been trialed in a migration
Note this lab exercise has similarities to another Forum post asking about
Cluster migration and his proposal to use Snapshot/Restore also.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/65f1f916-e413-4b59-abdd-55e98f64681f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.