html/en/elasticsearch/reference/current/add-repository.html

<!DOCTYPE html>
<html lang="en-us">
  <head>
    
<meta charset="UTF-8">
<meta name="keywords" content="hot-spotting, hotspot, hot-spot, hot spot, hotspots, hotspotting">
<title>Multiple deployments writing to the same snapshot repository | Elasticsearch Guide [8.10] | Elastic</title>
<meta class="elastic" name="content" content="Multiple deployments writing to the same snapshot repository | Elasticsearch Guide [8.10]">

<link rel="home" href="index.html" title="Elasticsearch Guide [8.10]"/>
<link rel="up" href="troubleshooting.html" title="Troubleshooting"/>
<link rel="prev" href="restore-from-snapshot.html" title="Restore from snapshot"/>
<link rel="next" href="repeated-snapshot-failures.html" title="Addressing repeated snapshot policy failures"/>
<meta class="elastic" name="product_version" content="8.10"/>
<meta class="elastic" name="product_name" content="Elasticsearch"/>
<meta class="elastic" name="website_area" content="documentation"/>
<meta name="DC.type" content="Learn/Docs/Elasticsearch/Reference/8.10"/>
<meta name="DC.subject" content="Elasticsearch"/>
<meta name="DC.identifier" content="8.10"/>

    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <script src="https://cdn.optimizely.com/js/18132920325.js"></script>
    <link rel="apple-touch-icon" sizes="57x57" href="/apple-icon-57x57.png">
    <link rel="apple-touch-icon" sizes="60x60" href="/apple-icon-60x60.png">
    <link rel="apple-touch-icon" sizes="72x72" href="/apple-icon-72x72.png">
    <link rel="apple-touch-icon" sizes="76x76" href="/apple-icon-76x76.png">
    <link rel="apple-touch-icon" sizes="114x114" href="/apple-icon-114x114.png">
    <link rel="apple-touch-icon" sizes="120x120" href="/apple-icon-120x120.png">
    <link rel="apple-touch-icon" sizes="144x144" href="/apple-icon-144x144.png">
    <link rel="apple-touch-icon" sizes="152x152" href="/apple-icon-152x152.png">
    <link rel="apple-touch-icon" sizes="180x180" href="/apple-icon-180x180.png">
    <link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32">
    <link rel="icon" type="image/png" href="/android-chrome-192x192.png" sizes="192x192">
    <link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96">
    <link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16">
    <link rel="manifest" href="/manifest.json">
    <meta name="apple-mobile-web-app-title" content="Elastic">
    <meta name="application-name" content="Elastic">
    <meta name="msapplication-TileColor" content="#ffffff">
    <meta name="msapplication-TileImage" content="/mstile-144x144.png">
    <meta name="theme-color" content="#ffffff">
    <meta name="naver-site-verification" content="936882c1853b701b3cef3721758d80535413dbfd" />
    <meta name="yandex-verification" content="d8a47e95d0972434" />
    <meta name="localized" content="true" />
    <meta name="st:robots" content="follow,index" />
    <meta property="og:image" content="https://static-www.elastic.co/v3/assets/bltefdd0b53724fa2ce/blt280217a63b82a734/6202d3378b1f312528798412/elastic-logo.svg" />
    <meta property="og:image:width" content="500" />
    <meta property="og:image:height" content="172" />
    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
    <link rel="icon" href="/favicon.ico" type="image/x-icon">
    <link rel="apple-touch-icon-precomposed" sizes="64x64" href="/favicon_64x64_16bit.png">
    <link rel="apple-touch-icon-precomposed" sizes="32x32" href="/favicon_32x32.png">
    <link rel="apple-touch-icon-precomposed" sizes="16x16" href="/favicon_16x16.png">
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
    <link rel="stylesheet" type="text/css" href="/guide/static/styles.css" />
  </head>

  <!--© 2015-2022 Elasticsearch B.V. -->
  <!-- All Elastic documentation is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. -->
  <!-- http://creativecommons.org/licenses/by-nc-nd/4.0/ -->

  <body>
    <!-- Google Tag Manager -->
    <script>dataLayer = [];</script><noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-58RLH5" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
    <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-58RLH5');</script>
    <!-- End Google Tag Manager -->

    <!-- Global site tag (gtag.js) - Google Analytics -->
    <script async src="https://www.googletagmanager.com/gtag/js?id=UA-12395217-16"></script>
    <script>
      window.dataLayer = window.dataLayer || [];
      function gtag(){dataLayer.push(arguments);}
      gtag('js', new Date());
      gtag('config', 'UA-12395217-16');
    </script>

    <!-- Google Tag Manager for GA4 -->
    <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer','GTM-KNJMG2M');</script>
    <noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-KNJMG2M" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
    <!-- End Google Tag Manager for GA4-->

    <div id='elastic-nav' style="display:none;"></div>
    <script src='https://www.elastic.co/elastic-nav.js'></script>

    <div class="main-container">
      <section id="content" >
        <div class="content-wrapper">

          <section id="guide" lang="en">
            <div class="container-fluid">
              <div class="row pb-3">
                <div class="col-12 order-2 col-md-4 order-md-1 col-lg-3 h-almost-full-md sticky-top-md" id="left_col">
                  <!-- The TOC is appended here -->
                </div>

                <div class="col-12 order-1 col-md-8 order-md-2 col-lg-7 order-lg-2 guide-section" id="middle_col">
                  <!-- start body -->
                  
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="/guide/">Elastic Docs</a></span>
<span class="chevron-right">›</span><span class="breadcrumb-link"><a href="index.html">Elasticsearch Guide [8.10]</a></span>
<span class="chevron-right">›</span><span class="breadcrumb-link"><a href="troubleshooting.html">Troubleshooting</a></span>
</div>
<div class="navheader">
<span class="prev">
<a href="restore-from-snapshot.html">« Restore from snapshot</a>
</span>
<span class="next">
<a href="repeated-snapshot-failures.html">Addressing repeated snapshot policy failures »</a>
</span>
</div>
<div class="chapter">
<div class="titlepage"><div><div>
<h2 class="title"><a id="add-repository"></a>Multiple deployments writing to the same snapshot repository<a class="edit_me" rel="nofollow" title="Edit this page on GitHub" href="https://github.com/elastic/elasticsearch/edit/8.10/docs/reference/troubleshooting/snapshot/add-repository.asciidoc">edit</a></h2>
</div></div></div>
<p>Multiple Elasticsearch deployments are writing to the same snapshot repository. Elasticsearch doesn&#8217;t
support this configuration and only one cluster is allowed to write to the same
repository. See <a class="xref" href="snapshot-restore.html#snapshot-repository-contents" title="Repository contents">Repository contents</a> for potential side-effects of
corruption of the repository contents, which may not be resolved by the following
guide.
To remedy the situation mark the repository as read-only or remove it from all the
other deployments, and re-add (recreate) the repository in the current deployment:</p>
<div class="tabs" data-tab-group="host">
  <div role="tablist" aria-label="Re-add repository">
    <button role="tab"
            aria-selected="true"
            aria-controls="cloud-tab-readd-repo"
            id="cloud-readd-repo">
      Elasticsearch Service
    </button>
    <button role="tab"
            aria-selected="false"
            aria-controls="self-managed-tab-readd-repo"
            id="self-managed-readd-repo"
            tabindex="-1">
      Self-managed
    </button>
  </div>
  <div tabindex="0"
       role="tabpanel"
       id="cloud-tab-readd-repo"
       aria-labelledby="cloud-readd-repo">
<p>Fixing the corrupted repository will entail making changes in multiple deployments
that write to the same snapshot repository.
Only one deployment must be writing to a repository. The deployment
that will keep writing to the repository will be called the "primary" deployment (the current cluster),
and the other one(s) where we&#8217;ll mark the repository read-only as the "secondary"
deployments.</p>
<p>First mark the repository as read-only on the secondary deployments:</p>
<p><span class="strong strong"><strong>Use Kibana</strong></span></p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
Log in to the <a href="https://cloud.elastic.co?page=docs&amp;placement=docs-body" class="ulink" target="_top">Elastic Cloud console</a>.
</li>
<li class="listitem">
<p>On the <span class="strong strong"><strong>Elasticsearch Service</strong></span> panel, click the name of your deployment.</p>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>If the name of your deployment is disabled your Kibana instances might be
unhealthy, in which case please contact <a href="https://support.elastic.co" class="ulink" target="_top">Elastic Support</a>.
If your deployment doesn&#8217;t include Kibana, all you need to do is
<a href="/guide/en/cloud/current/ec-access-kibana.html" class="ulink" target="_top">enable it first</a>.</p>
</div>
</div>
</li>
<li class="listitem">
<p>Open your deployment&#8217;s side navigation menu (placed under the Elastic logo in the upper left corner)
and go to <span class="strong strong"><strong>Stack Management &gt; Snapshot and Restore &gt; Repositories</strong></span>.</p>
<div class="imageblock text-center screenshot">
<div class="content">
<img src="images/repositories.png" alt="Kibana Console">
</div>
</div>
</li>
<li class="listitem">
The repositories table should now be visible. Click on the pencil icon at the
right side of the repository to be marked as read-only. On the Edit page that opened
scroll down and check "Read-only repository". Click "Save".
Alternatively if deleting the repository altogether is preferable, select the checkbox
at the left of the repository name in the repositories table and click the
"Remove repository" red button at the top left of the table.
</li>
</ol>
</div>
<p>At this point, it&#8217;s only the primary (current) deployment that has the repository marked
as writeable.
Elasticsearch sees it as corrupt, so the repository needs to be removed and added back so that
Elasticsearch can resume using it:</p>
<p>Note that we&#8217;re now configuring the primary (current) deployment.</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
<p>Open the primary deployment&#8217;s side navigation menu (placed under the Elastic logo in the upper left corner)
and go to <span class="strong strong"><strong>Stack Management &gt; Snapshot and Restore &gt; Repositories</strong></span>.</p>
<div class="imageblock text-center screenshot">
<div class="content">
<img src="images/repositories.png" alt="Kibana Console">
</div>
</div>
</li>
<li class="listitem">
Click on the pencil icon at the right side of the repository. On the Edit page that opened
scroll down and click "Save", without making any changes to the existing settings.
</li>
</ol>
</div>
  </div>
  <div tabindex="0"
       role="tabpanel"
       id="self-managed-tab-readd-repo"
       aria-labelledby="self-managed-readd-repo"
       hidden="">
<p>Fixing the corrupted repository will entail making changes in multiple clusters
that write to the same snapshot repository.
Only one cluster must be writing to a repository. Let&#8217;s call the cluster
we want to keep writing to the repository the "primary" cluster (the current cluster),
and the other one(s) where we&#8217;ll mark the repository as read-only the "secondary"
clusters.</p>
<p>Let&#8217;s first work on the secondary clusters:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
<p>Get the configuration of the repository:</p>
<div class="pre_wrapper lang-ruby alternative">
<pre class="programlisting prettyprint lang-ruby alternative">response = client.snapshot.get_repository(
  repository: 'my-repo'
)
puts response</pre>
</div>
<a id="b4d9d5017d42f27281e734e969949623"></a>
<div class="pre_wrapper lang-console default has-ruby">
<pre class="programlisting prettyprint lang-console default has-ruby">GET _snapshot/my-repo</pre>
</div>
<div class="console_widget has-ruby" data-snippet="snippets/2055.console"></div>
<p>The reponse will look like this:</p>
<a id="5321a214f7f8d01a114ab7ba81020a1c"></a>
<div class="pre_wrapper lang-console-result">
<pre class="programlisting prettyprint lang-console-result">{
  "my-repo": { <a id="CO679-1"></a><i class="conum" data-value="1"></i>
    "type": "s3",
    "settings": {
      "bucket": "repo-bucket",
      "client": "elastic-internal-71bcd3",
      "base_path": "myrepo"
    }
  }
}</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO679-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>Represents the current configuration for the repository.</p>
</td>
</tr>
</table>
</div>
</li>
<li class="listitem">
<p>Using the settings retrieved above, add the <code class="literal">readonly: true</code> option to mark
it as read-only:</p>
<a id="06c0db0f42223761e32fa418066b275f"></a>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">PUT _snapshot/my-repo
{
    "type": "s3",
    "settings": {
      "bucket": "repo-bucket",
      "client": "elastic-internal-71bcd3",
      "base_path": "myrepo",
      "readonly": true <a id="CO680-1"></a><i class="conum" data-value="1"></i>
    }
}</pre>
</div>
<div class="console_widget" data-snippet="snippets/2056.console"></div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO680-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>Marks the repository as read-only.</p>
</td>
</tr>
</table>
</div>
</li>
<li class="listitem">
<p>Alternatively, deleting the repository is an option using:</p>
<div class="pre_wrapper lang-ruby alternative">
<pre class="programlisting prettyprint lang-ruby alternative">response = client.snapshot.delete_repository(
  repository: 'my-repo'
)
puts response</pre>
</div>
<a id="4427517dcd8ec9997541150cdc11a0de"></a>
<div class="pre_wrapper lang-console default has-ruby">
<pre class="programlisting prettyprint lang-console default has-ruby">DELETE _snapshot/my-repo</pre>
</div>
<div class="console_widget has-ruby" data-snippet="snippets/2057.console"></div>
<p>The response will look like this:</p>
<a id="bc5fcc40c29087a0df7b5405bb70de5c"></a>
<div class="pre_wrapper lang-console-result">
<pre class="programlisting prettyprint lang-console-result">{
  "acknowledged": true
}</pre>
</div>
</li>
</ol>
</div>
<p>At this point, it&#8217;s only the primary (current) cluster that has the repository marked
as writeable.
Elasticsearch sees it as corrupt though so let&#8217;s recreate it so that Elasticsearch can resume using it.
Note that now we&#8217;re configuring the primary (current) cluster:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
<p>Get the configuration of the repository and save its configuration as we&#8217;ll use it
to recreate the repository:</p>
<div class="pre_wrapper lang-ruby alternative">
<pre class="programlisting prettyprint lang-ruby alternative">response = client.snapshot.get_repository(
  repository: 'my-repo'
)
puts response</pre>
</div>
<a id="b4d9d5017d42f27281e734e969949623"></a>
<div class="pre_wrapper lang-console default has-ruby">
<pre class="programlisting prettyprint lang-console default has-ruby">GET _snapshot/my-repo</pre>
</div>
<div class="console_widget has-ruby" data-snippet="snippets/2058.console"></div>
</li>
<li class="listitem">
<p>Using the configuration we obtained above, let&#8217;s recreate the repository:</p>
<a id="7fbebf0fc9b4a402917a4723ad547c6a"></a>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">PUT _snapshot/my-repo
{
  "type": "s3",
  "settings": {
    "bucket": "repo-bucket",
    "client": "elastic-internal-71bcd3",
    "base_path": "myrepo"
  }
}</pre>
</div>
<div class="console_widget" data-snippet="snippets/2059.console"></div>
<p>The response will look like this:</p>
<a id="bc5fcc40c29087a0df7b5405bb70de5c"></a>
<div class="pre_wrapper lang-console-result">
<pre class="programlisting prettyprint lang-console-result">{
  "acknowledged": true
}</pre>
</div>
</li>
</ol>
</div>
  </div>
</div>
</div>
<div class="navfooter">
<span class="prev">
<a href="restore-from-snapshot.html">« Restore from snapshot</a>
</span>
<span class="next">
<a href="repeated-snapshot-failures.html">Addressing repeated snapshot policy failures »</a>
</span>
</div>
</div>

                  <!-- end body -->
                </div>

                <div class="col-12 order-3 col-lg-2 order-lg-3 h-almost-full-lg sticky-top-lg" id="right_col">
                  <div id="sticky_content">
                    <!-- The OTP is appended here -->
                    <div class="row">
                      <div class="col-0 col-md-4 col-lg-0" id="bottom_left_col"></div>
                      <div class="col-12 col-md-8 col-lg-12">
                        <div id="rtpcontainer">
                          <div class="mktg-promo" id="most-popular">
                            <p class="aside-heading">Most Popular</p>
                            <div class="pb-2">
                              <p class="media-type">Video</p>
                              <a href="https://www.elastic.co/webinars/getting-started-elasticsearch?page=docs&placement=top-video">
                                <p class="mb-0">Get Started with Elasticsearch</p>
                              </a>
                            </div>
                            <div class="pb-2">
                              <p class="media-type">Video</p>
                              <a href="https://www.elastic.co/webinars/getting-started-kibana?page=docs&placement=top-video">
                                <p class="mb-0">Intro to Kibana</p>
                              </a>
                            </div>
                            <div class="pb-2">
                              <p class="media-type">Video</p>
                              <a href="https://www.elastic.co/webinars/introduction-elk-stack?page=docs&placement=top-video">
                                <p class="mb-0">ELK for Logs & Metrics</p>
                              </a>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </section>

        </div>


<div id='elastic-footer'></div>
<script src='https://www.elastic.co/elastic-footer.js'></script>
<!-- Footer Section end-->

      </section>
    </div>

<script src="/guide/static/jquery.js"></script>
<script type="text/javascript" src="/guide/static/docs.js"></script>
<script type="text/javascript">
  window.initial_state = {"alternatives":{"console":{"php":{"hasAny":true},"python":{"hasAny":true},"ruby":{"hasAny":true},"go":{"hasAny":true},"js":{"hasAny":true}}}}</script>
  </body>
</html>