<?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: Upgrading Distributed Environments Without Data Loss in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Upgrading-Distributed-Environments-Without-Data-Loss/m-p/541351#M18580</link>
    <description>&lt;P&gt;Thanks for the information,&amp;nbsp;&lt;SPAN&gt;Giuseppe.&amp;nbsp; We do not have clustered indexers but we do have one primary search head.&amp;nbsp; I've checked compatibility on the forwarders, so it appears one at a time, indexers then forwards is the way to go.&amp;nbsp; Thank you!&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Feb 2021 14:34:54 GMT</pubDate>
    <dc:creator>act_waltersj</dc:creator>
    <dc:date>2021-02-25T14:34:54Z</dc:date>
    <item>
      <title>Upgrading Distributed Environments Without Data Loss</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Upgrading-Distributed-Environments-Without-Data-Loss/m-p/541255#M18578</link>
      <description>&lt;P&gt;I'm taking over Splunk admin duties from a co-worker that has left the company.&amp;nbsp; We have a distributed environment setup of two heavy forwarders and four index servers all running&amp;nbsp; Splunk Enterprise 7.3.&amp;nbsp; I'm fleshing out our upgrade task list for moving to 8.1.2.&amp;nbsp; What is the best way to manage the upgrade across all servers, and do I need to take any special steps to prevent loss of logs?&amp;nbsp; I have the task for the install itself, I need a game plan for how to do it across the 6 servers.&amp;nbsp; Will upgrading each server - one at a time, have it back up and running before I move to the next server - prevent log/data loss, or is it better practice to do all 6 servers at once (take them all down, upgrade them all, the bring them all back online).&amp;nbsp; Looking at the compatibility matrix the I should be able to do all the indexers first and have the heavy forwarders still be compatible.&amp;nbsp; Any advice on how to manage this is greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 18:17:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Upgrading-Distributed-Environments-Without-Data-Loss/m-p/541255#M18578</guid>
      <dc:creator>act_waltersj</dc:creator>
      <dc:date>2021-02-24T18:17:00Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Distributed Environments Without Data Loss</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Upgrading-Distributed-Environments-Without-Data-Loss/m-p/541279#M18579</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231850"&gt;@act_waltersj&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;only two questions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;have you clustered or not clustered Indexers?&lt;/LI&gt;&lt;LI&gt;have you Search Heads?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Anyway, the upgrade order is the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Master Node (if clustered Indexers);&lt;/LI&gt;&lt;LI&gt;Search Heads;&lt;/LI&gt;&lt;LI&gt;Indexers;&lt;/LI&gt;&lt;LI&gt;Heavy Forwarders:&lt;/LI&gt;&lt;LI&gt;Universal Forwarders.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;If you have an Indexer Cluster, you can perform a rolling upgrade so you don't loose any data.&lt;/P&gt;&lt;P&gt;If you don't have an Indexer Cluster, you have to upgrade indexers only one a time.&lt;/P&gt;&lt;P&gt;You must put the same attention to Heavy Forwarders: upgrade only one a time.&lt;/P&gt;&lt;P&gt;Check the version of your Universal Forwarders to verify the compatibility with Indexers 8.1.2.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 21:56:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Upgrading-Distributed-Environments-Without-Data-Loss/m-p/541279#M18579</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2021-02-24T21:56:48Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Distributed Environments Without Data Loss</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Upgrading-Distributed-Environments-Without-Data-Loss/m-p/541351#M18580</link>
      <description>&lt;P&gt;Thanks for the information,&amp;nbsp;&lt;SPAN&gt;Giuseppe.&amp;nbsp; We do not have clustered indexers but we do have one primary search head.&amp;nbsp; I've checked compatibility on the forwarders, so it appears one at a time, indexers then forwards is the way to go.&amp;nbsp; Thank you!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Feb 2021 14:34:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Upgrading-Distributed-Environments-Without-Data-Loss/m-p/541351#M18580</guid>
      <dc:creator>act_waltersj</dc:creator>
      <dc:date>2021-02-25T14:34:54Z</dc:date>
    </item>
  </channel>
</rss>

