<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Site decommission- how to find old data? in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Site-decommission-how-to-find-old-data/m-p/636247#M15850</link>
    <description>&lt;P&gt;thanks for the answer.&lt;/P&gt;&lt;P&gt;Setting RF 2:2 i get this error on splunkd.log&lt;/P&gt;&lt;P&gt;03-28-2023 12:47:53.255 +0700 ERROR ClusteringMgr - Failure to load cluster config (server.conf) Error = site_replication_factor={ origin:1, total:2 } is less than replication_factor=3.&lt;BR /&gt;03-28-2023 12:47:53.256 +0700 ERROR loader - clustering initialization failed; won't start splunkd&lt;/P&gt;&lt;P&gt;Kindly can suggest me how to verify if an originating event from one of the peer in the dismissed site has been migrated. Using SPL with a simple query like "index=blabla "*&amp;lt;old-peer-name&amp;gt;*" doesn't give result.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Tue, 28 Mar 2023 05:52:19 GMT</pubDate>
    <dc:creator>mgoldoni</dc:creator>
    <dc:date>2023-03-28T05:52:19Z</dc:date>
    <item>
      <title>Site decommission- how to find old data?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Site-decommission-how-to-find-old-data/m-p/636101#M15835</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;needs to remive a site in a three sites cluster. Following the instructions in&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.0/Indexer/Decommissionasite" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.0/Indexer/Decommissionasite&lt;/A&gt;, and resuming the commands as follow:&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;- Check if cluster is in complete state&lt;BR /&gt;- Move Manager away from the decommissioned site&lt;BR /&gt;- Remove the peers in decommissioned site as receivers for UF&lt;/P&gt;
&lt;P&gt;- Enter in maintenance mode&lt;/P&gt;
&lt;P&gt;- Modify server.conf (manager node )&lt;BR /&gt;&lt;STRONG&gt;from:&lt;/STRONG&gt; available_sites = site1, site2, site3&amp;nbsp; &lt;STRONG&gt;to:&lt;/STRONG&gt; available_sites = site1, site2&lt;BR /&gt;&lt;STRONG&gt;from:&lt;/STRONG&gt; site_replication_factor = origin:1,site1:1,site2:1,site3:1,total:3&amp;nbsp; &lt;STRONG&gt;to:&lt;/STRONG&gt; site_replication_factor = origin:2,total:3&lt;BR /&gt;&lt;STRONG&gt;from:&lt;/STRONG&gt; site_search_factor = origin:1, total:2&amp;nbsp; &lt;STRONG&gt;to:&lt;/STRONG&gt; site_search_factor = origin:1,total:2&lt;BR /&gt;&lt;STRONG&gt;add:&lt;/STRONG&gt; site_mappings = site3:site1&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;- Restart the manager&lt;BR /&gt;- Disable maintenance mode&lt;BR /&gt;- Stop splunk on each peer on the decommissioned site&lt;BR /&gt;- Waiting the cluster back in complete state&lt;/P&gt;
&lt;P&gt;- Remove peers&lt;/P&gt;
&lt;P&gt;How can i verify if all is gone as expected ?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;check buckets, query ...&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 14:19:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Site-decommission-how-to-find-old-data/m-p/636101#M15835</guid>
      <dc:creator>mgoldoni</dc:creator>
      <dc:date>2023-03-27T14:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: Site decommission- how to find old data?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Site-decommission-how-to-find-old-data/m-p/636233#M15847</link>
      <description>&lt;P&gt;Your plan seems sound, although I would change the site RF to 2:2.&amp;nbsp; Using 2:3 means Splunk will store two copies of your data on one site (not always&amp;nbsp; the same site) so you'll need additional storage.&amp;nbsp; RF of 2:2 keeps your current storage usage.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2023 00:06:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Site-decommission-how-to-find-old-data/m-p/636233#M15847</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-03-28T00:06:10Z</dc:date>
    </item>
    <item>
      <title>Re: Site decommission- how to find old data?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Site-decommission-how-to-find-old-data/m-p/636247#M15850</link>
      <description>&lt;P&gt;thanks for the answer.&lt;/P&gt;&lt;P&gt;Setting RF 2:2 i get this error on splunkd.log&lt;/P&gt;&lt;P&gt;03-28-2023 12:47:53.255 +0700 ERROR ClusteringMgr - Failure to load cluster config (server.conf) Error = site_replication_factor={ origin:1, total:2 } is less than replication_factor=3.&lt;BR /&gt;03-28-2023 12:47:53.256 +0700 ERROR loader - clustering initialization failed; won't start splunkd&lt;/P&gt;&lt;P&gt;Kindly can suggest me how to verify if an originating event from one of the peer in the dismissed site has been migrated. Using SPL with a simple query like "index=blabla "*&amp;lt;old-peer-name&amp;gt;*" doesn't give result.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2023 05:52:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Site-decommission-how-to-find-old-data/m-p/636247#M15850</guid>
      <dc:creator>mgoldoni</dc:creator>
      <dc:date>2023-03-28T05:52:19Z</dc:date>
    </item>
    <item>
      <title>Re: Site decommission- how to find old data?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Site-decommission-how-to-find-old-data/m-p/636307#M15858</link>
      <description>&lt;P&gt;To reduce the site RF you must also reduce replication_factor.&lt;/P&gt;&lt;P&gt;Data on the dismissed site will not be migrated because it's already copied on each of the other two sites.&amp;nbsp; That's a result of your site_replication_factor setting.&lt;/P&gt;&lt;P&gt;When the site is decommissioned, the Cluster Manager will ensure a primary bucket exists somewhere in the cluster.&amp;nbsp; Once the CM says the search and replication factors are met then you are done.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2023 12:24:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Site-decommission-how-to-find-old-data/m-p/636307#M15858</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-03-28T12:24:03Z</dc:date>
    </item>
  </channel>
</rss>

