<?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: Splunk Rollback in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Rollback/m-p/523760#M18031</link>
    <description>You could found couple of cases how this can do on single instance by just googling with “splunk rollback update” those expects that there haven’t been any changes to indexes e.g. change of compression method etc.&lt;BR /&gt;r. Ismo</description>
    <pubDate>Thu, 08 Oct 2020 17:05:54 GMT</pubDate>
    <dc:creator>isoutamo</dc:creator>
    <dc:date>2020-10-08T17:05:54Z</dc:date>
    <item>
      <title>Splunk Rollback</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Rollback/m-p/523751#M18028</link>
      <description>&lt;P&gt;Is it possible to rollback changes if we face some issue upon Splunk enterprise version upgrade?&lt;/P&gt;</description>
      <pubDate>Thu, 08 Oct 2020 16:47:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Rollback/m-p/523751#M18028</guid>
      <dc:creator>sanjubaba</dc:creator>
      <dc:date>2020-10-08T16:47:03Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Rollback</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Rollback/m-p/523753#M18029</link>
      <description>&lt;P&gt;It depends what kind of environment you have and which kind of update you have done. Quite often the answer is no or use your backups to restore to the previous version. That also needs that you have stopped your input for update time, otherwise you lost those events when you do a restore from backups.&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Thu, 08 Oct 2020 16:51:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Rollback/m-p/523753#M18029</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-10-08T16:51:13Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Rollback</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Rollback/m-p/523754#M18030</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/214410"&gt;@isoutamo&lt;/a&gt;&amp;nbsp;Thank you for your reply.&lt;/P&gt;&lt;P&gt;Can you provide any document link or community discussion link regarding this topic?&lt;/P&gt;</description>
      <pubDate>Thu, 08 Oct 2020 16:54:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Rollback/m-p/523754#M18030</guid>
      <dc:creator>sanjubaba</dc:creator>
      <dc:date>2020-10-08T16:54:51Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Rollback</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Rollback/m-p/523760#M18031</link>
      <description>You could found couple of cases how this can do on single instance by just googling with “splunk rollback update” those expects that there haven’t been any changes to indexes e.g. change of compression method etc.&lt;BR /&gt;r. Ismo</description>
      <pubDate>Thu, 08 Oct 2020 17:05:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Rollback/m-p/523760#M18031</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-10-08T17:05:54Z</dc:date>
    </item>
  </channel>
</rss>

