# Unable to register secondary azure snapshot repo. Elasticsearch says client not found

**URL:** <https://discuss.elastic.co/t/unable-to-register-secondary-azure-snapshot-repo-elasticsearch-says-client-not-found/385806>\
**Category:** Elasticsearch\
**Created:** [April 7, 2026, 7:31pm UTC](https://discuss.elastic.co/t/unable-to-register-secondary-azure-snapshot-repo-elasticsearch-says-client-not-found/385806 "2026-04-07T19:31:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dfinn](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dfinn](https://discuss.elastic.co/u/dfinn)\
**Post date:** [April 7, 2026, 7:31pm UTC](https://discuss.elastic.co/t/unable-to-register-secondary-azure-snapshot-repo-elasticsearch-says-client-not-found/385806/1 "2026-04-07T19:31:38Z")

</div>

I’m trying to add a secondary snapshot repo repo to a cluster to migrate data. I’ve added the account info and key into the elasticsearch keystore, you can see them here:

`elasticsearch-keystore list`  
`azure.client.default.account`  
`azure.client.default.key`  
`azure.client.secondary.account`  
`azure.client.secondary.key`  
`bootstrap.password`  
`keystore.seed`

To be sure, I also ran this on the cluster:  
`POST _nodes/reload_secure_settings`

here is the settings for the repo:

```auto
  "secondary-repo": {

    "type": "azure",

"uuid": "Wj5LIrlvSXqnynrl-ZESZw",

"settings": {

"client": "secondary"

    }

  }

```

you can see client is set to “secondary” however when I do a verify on the snapshot repo, I get the following error:

```auto
        "caused_by": {

          "type": "settings_exception",

"reason": "Unable to find client with name [secondary]"

```

so what am I missing that it’s not finding this secondary client information? I think I have everything in place according to how the docs suggest.

---

<div class="post-metadata">

**Author:** ![dfinn](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dfinn](https://discuss.elastic.co/u/dfinn)\
**Post date:** [April 7, 2026, 7:44pm UTC](https://discuss.elastic.co/t/unable-to-register-secondary-azure-snapshot-repo-elasticsearch-says-client-not-found/385806/2 "2026-04-07T19:44:04Z")

</div>

I figured this out just after hitting submit on this. We have both master and data nodes and I had only added the account information to the keystore on the master nodes, the data nodes need it as well.